fix blocking items

Author: chcomley

docs/artifacts/quickstarts/github-actions.md

@@ -32,7 +32,7 @@ You can authenticate by using either a managed identity or a [Personal Access To
 - Permission to assign a managed identity to the **Contributor** group in Azure DevOps. **Project Administrators** and **Collection Administrators** both have this permission. 
 
 > [!NOTE]
-> An alternative approach is to use an Microsoft Entra application with a service principal and federated authentication credential to connect Azure DevOps and GitHub Actions. To learn more about this approach, see [Configure an app to trust an external identity provider](/entra/workload-id/workload-identity-federation-create-trust). 
+> An alternative approach is to use a Microsoft Entra application with a service principal and federated authentication credential to connect Azure DevOps and GitHub Actions. To learn more about this approach, see [Configure an app to trust an external identity provider](/entra/workload-id/workload-identity-federation-create-trust). 
 
 ## Assign permissions to your managed identity in Azure DevOps 
 

docs/artifacts/universal-packages/project-setup-universal-packages.md

@@ -49,7 +49,7 @@ Ensure that you have Azure CLI installed, then follow the steps below to install
 
     ### [Windows](#tab/windows/)
 
-    1. Run the following command to log into the Azure CLI:
+    1. Run the following command to sign in to the Azure CLI:
 
         ```azurecli
         az login

docs/organizations/security/security-overview.md

@@ -50,7 +50,7 @@ Zero Trust helps protect against lateral movement within the network, ensuring t
 
 Ensure your Azure DevOps environment complies with industry standards and regulations that protect your environment and maintain trust with your users.
 
-- **Ensure compliance with industry standards:** Azure DevOps complies with various industry standards and regulations, such as ISO/IEC 27001, SOC 1/2/3, and GDPR. Ensure your environment adheres to these standards.
+- **Ensure compliance with industry standards:** Azure DevOps complies with various industry standards and regulations, such as ISO/IEC 27001, SOC 1/2/3, and more. Ensure your environment adheres to these standards.
 - **Enforce compliance policies:** Implement [branch policies](../../repos/git/branch-policies.md) and [compliance policies for your pipelines](/azure/governance/policy/tutorials/policy-devops-pipelines).
 - **Onboard to Component Governance for CI/CDs**, which offers the following benefits:
   - Security vulnerability detection: Alerts you to known vulnerabilities in open-source components.

docs/pipelines/agents/service-principal-agent-registration.md

@@ -60,7 +60,7 @@ For more information about using Service Principal with Azure DevOps, see [Use s
 >
 > `ClientSecretCredential authentication failed: AADSTS90002: Tenant 'xxxxxxxxxxxxxx' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant.`
 >
-> To resolve this error, set the login URL to Azure Public Cloud login by setting the environment variable `$AZURE_AUTHORITY_HOST` to 
+> To resolve this error, set the sign-in URL to Azure Public Cloud sign-in by setting the environment variable `$AZURE_AUTHORITY_HOST` to 
 `https://login.microsoftonline.com`, then run the agent config.cmd.
 > 
 > For more information, see [Azure in China developer guide](/azure/china/resources-developer-guide), 

docs/pipelines/security/overview.md

@@ -113,7 +113,7 @@ Learn how to secure containers through configuration changes, scanning, and poli
 - **Mark volumes as read only**: Containers include system-provided volume mounts for tasks, tools, and external components required to work with the host agent. Set `externals`, `tasks`, and `tools` to read only for added security. 
 - **Set container-specific resource limits**: Set limits on CPU and memory to prevent containers from consuming excessive resources, which can lead to denial of service or security vulnerabilities.
 - **Use trusted images**: Use official and verified images from reputable sources such as Azure Container Registry or Docker Hub. Always specify a specific version or tag to maintain consistency and reliability, rather than relying on the `latest` tag. Regularly update base images to include the latest security patches and bug fixes.
-- **Scan containers for vulnerabilities and enforce runtime threat protection**: Use tools such as [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-containers-introduction) to monitor and detect security risks. Additionally, Azure Container Registry offers integrated [vulnerability scanning](/azure/container-registry/scan-images-defender) to help ensure container images are secure before deployment. You can also integrate third-party scanning tools through Azure DevOps extensions for added security checks.
+- **Scan containers for vulnerabilities and enforce runtime threat protection**: Use tools such as [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-containers-introduction) to monitor and detect security risks. Additionally, Azure Container Registry offers integrated [vulnerability scanning](/azure/container-registry/scan-images-defender) to help ensure container images are secure before deployment. You can also integrate non-Microsoft scanning tools through Azure DevOps extensions for added security checks.
 - **Implement security policies to prevent privilege escalation and ensure containers run with the least amount of privileges necessary**: For example, Azure [Kubernetes Service (AKS)](/azure/aks/operator-best-practices-cluster-security), [role-based access control](/azure/aks/manage-azure-rbac), and [Pod Security Admission](/azure/aks/use-psa) let you enforce policies that restrict container privileges, ensure non-root execution, and limit access to critical resources. 
 - **Utilize Network Policies**: [Network Policies](/azure/virtual-network/kubernetes-network-policies) can be used to restrict communication between containers, ensuring that only authorized containers can access sensitive resources within your network. In addition, [Azure Policy for AKS](/azure/governance/policy/concepts/policy-for-kubernetes) can be applied to enforce container security best practices, such as ensuring only trusted container images are deployed.