diff --git a/data/reusables/actions/about-runner-groups.md b/data/reusables/actions/about-runner-groups.md
index 5fc01d3039..6de21ebb50 100644
--- a/data/reusables/actions/about-runner-groups.md
+++ b/data/reusables/actions/about-runner-groups.md
@@ -4,7 +4,7 @@ Runner groups are used to collect sets of runners and create a security boundary
 
 {%- ifversion ghec or ghes or ghae %} Enterprise administrators can configure access policies that control which organizations {% ifversion restrict-groups-to-workflows %}and workflows {% endif %}in an enterprise have access to the runner group.{% else %} Organization owners can configure access policies that control which repositories in an organization have access to the runner group.{% endif %}
 
-When you grant access access to a runner group, you can see the runner group listed in the organization's runner settings. Optionally, you can assign additional granular repository{% ifversion restrict-groups-to-workflows %} and workflow{% endif %} access policies to the runner group.
+When you grant access to a runner group, you can see the runner group listed in the organization's runner settings. Optionally, you can assign additional granular repository{% ifversion restrict-groups-to-workflows %} and workflow{% endif %} access policies to the runner group.
 
 When new runners are created, they are automatically assigned to the default group unless otherwise specified. Runners can only be in one group at a time. You can move runners from one runner group to another. For more information, see "[Moving a runner to a group](#moving-a-runner-to-a-group)."