Clarify `.github` repository visibility requirement for starter workflows (#50421)

Co-authored-by: Thomas Cole <51364971+thomasjohncole@users.noreply.github.com>

content/actions/using-workflows/creating-starter-workflows-for-your-organization.md

@@ -24,9 +24,12 @@ topics:
 
 {% data reusables.actions.starter-workflow-categories %}
 
+> [!NOTE]
+> Because starter workflows require a public `.github` repository, they are not available for {% data variables.product.prodname_emus %}.
+
 ## Creating a starter workflow
 
-Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+Starter workflows can be created by users with write access to the organization's _public_ `.github` repository. These can then be used by organization members who have permission to create workflows.
 
 {% ifversion fpt %}
 Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-workflows/creating-starter-workflows-for-your-organization).
@@ -40,7 +43,7 @@ Starter workflows created by users can only be used to create workflows in publi
 
 This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
 
-1. If it doesn't already exist, create a new public repository named `.github` in your organization.
+1. If it doesn't already exist, create a new _public_ repository named `.github` in your organization.
 1. Create a directory named `workflow-templates`.
 1. Create your new workflow file inside the `workflow-templates` directory.