Versioning fixes

content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md

@@ -19,6 +19,8 @@ shortTitle: Manage access to runners
 
 {% data reusables.actions.about-runner-groups %}
 
+{% ifversion ghec or ghes or ghae %}
+
 ## Creating a runner group for an organization
 
 {% data reusables.actions.creating-a-runner-group-for-an-organization %}
@@ -27,6 +29,8 @@ shortTitle: Manage access to runners
 
 {% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
 
+{% endif %}
+
 ## Changing the access policy of a runner group
 
 {% data reusables.actions.changing-the-access-policy-of-a-runner-group %}

data/reusables/actions/about-runner-groups.md

@@ -15,3 +15,5 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can create addit
 {% data reusables.actions.runner-group-enterprise-overview %}
 
 When new runners are created, they are automatically assigned to the default group. Runners can only be in one group at a time. You can move runners from the default group to another group. For more information, see "[Moving a runner to a group](#moving-a-runner-to-a-group)."
+
+{% endif %}

data/reusables/actions/creating-a-runner-group-for-an-enterprise.md

@@ -28,4 +28,3 @@ When creating a group, you must choose a policy that defines which organizations
 {% data reusables.actions.runner-group-assign-policy-workflow %}
 1. Click **Save group** to create the group and apply the policy.
 
-{% endif %}