build warning fixes

Author: chcomley

docs/includes/prerequisites-project-collection-valid-users-group.md

@@ -2,10 +2,10 @@
 ms.topic: include
 ---
 
-**Permissions**: Be a member of the **Project Collection Valid Users** group. Users who are project members are automatically members of this group.
+**Permissions**: Be a member of the **Project Collection Valid Users** group. Project members are automatically members of this group.
 
 ::: moniker range="azure-devops"  
 > [!NOTE]  
-> Users added to the **Project-scoped users** group can't access **Organization settings** other than the **Overview** section if the [**Limit user visibility and collaboration to specific projects** preview feature is enabled](../../user-guide/manage-organization-collection.md#project-scoped-user-group) for the organization.
+> Users added to the **Project-scoped users** group can't access **Organization settings** other than the **Overview** section if the [**Limit user visibility and collaboration to specific projects** preview feature is enabled](../user-guide/manage-organization-collection.md#project-scoped-user-group) for the organization.
 
 ::: moniker-end  

docs/organizations/security/change-access-levels.md

@@ -27,26 +27,20 @@ For a simplified overview of the permissions that are assigned to the most commo
 
 ## Prerequisites
 
-- **Permissions**: Be a member of the [**Project Administrators** group](../organizations/security/change-project-level-permissions.md). 
+- **Permissions**: Be a member of the [**Project Administrators** group](change-project-level-permissions.md). 
 * **Group membership**: To manage access for a large group of users, create either a [Windows group, a group in Active Directory, or Azure DevOps security group](/azure/devops/server/admin/setup-ad-groups), and then add users to those groups.
 * **Project access**: Ensure users are [added to the project](add-users-team-project.md).
 
 ## Open access levels
 
 You can manage access levels for the collections defined on the application tier. The default access level affects all the projects in all the collections. When you add users or groups to teams, projects, or collections, they get the default access level. To give a different access level to a certain user or group, you need to add them to a non-default access level.
 
-::: moniker range=">= azure-devops-2019"
-
 - From the web portal home page for a project collection (for example, `http://MyServer:8080/tfs/DefaultCollection/`), open **Access levels**. If you're at a project level, choose the :::image type="icon" source="../../media/icons/project-icon.png" border="false"::: Azure DevOps logo and then choose **Access levels**.
 
    ![Screenshot of web portal, Open Access levels dialog.](media/change-access-levels/open-access-levels-2019.png)
 
 	If you don't see **Access levels**, you aren't an administrator and need to [get permission](/azure/devops/server/admin/add-administrator).
 
-::: moniker-end
-
-
-
 ## Add a user or group to an access level 
 
 Changes you make to the access level settings take effect immediately.

docs/organizations/security/restrict-invitations.md

@@ -30,7 +30,7 @@ can add users who are already in the organization to their team       |
 ## Prerequisites
 
 - **Permissions**: Be a member of the [**Project Collection Administrators** group](../security/look-up-project-collection-administrators.md). Organization owners are automatically members of this group.
-- **Access levels:** Be a member in the destination Microsoft Entra ID. For more information, see how to [convert a Microsoft Entra guest into a member](faq-azure-access.yml).
+- **Access levels:** Be a member in the destination Microsoft Entra ID. For more information, see [Convert a Microsoft Entra guest into a member](../accounts/faq-azure-access.yml).
 
 ## Turn off policy
 

docs/organizations/security/view-permissions.md

@@ -27,7 +27,7 @@ For more information, see [Get started with permissions, access, and security gr
 
 ## Prerequisites
 
-* **Project membership**: Be a member of a [project](../organizations/projects/create-project.md). 
+* **Project membership**: Be a [member of a project](../organizations/projects/create-project.md). 
 * **Permissions:** Be a member of the **Project Valid Users** group or **Project Collection Valid Users** group.
 
 ## View project-level permissions