Resource group wording (#2106)

* clarify wording for rg admin

* use full word

* add also

* add admin capabilities

Author: Muhammadsaeed707

docs/hub/security-resource-groups.md

@@ -18,9 +18,9 @@ Members are assigned a role in each Resource Group that determines their permiss
 - `read`: Grants read access to repositories within the Resource Group.
 - `contributor`: Provides extra write rights to the subset of the Organization's repositories created by the user (i.e., users can create repos and then modify only those repos). Similar to the 'Write' role, but limited to repos created by the user.
 - `write`: Offers write access to all repositories in the Resource Group. Users can create, delete, or rename any repository in the Resource Group.
-- `admin`: In addition to write permissions on repositories, admin members can administer the Resource Group — add, remove, and alter the roles of other members. They can also transfer repositories in and out of the Resource Group.
+- `admin`: In addition to write permissions on repositories, admin members can administer the Resource Group — add, remove, and alter the roles of other members. They can also manage already existing repositories in a Resource Group.
 
-In addition, Organization admins can manage all resource groups inside the organization.
+In addition, Organization admins can manage all resource groups inside the organization. This includes moving repositories in and out of any Resource Group.
 
 Resource Groups also affect the visibility of private repositories inside the organization. A private repository that is part of a Resource Group will only be visible to members of that Resource Group. Public repositories, on the other hand, are visible to anyone, inside and outside the organization.