Acrolinx markups.

Author: Andy Churchard

articles/operator-service-manager/quickstart-containerized-network-function-create-site-network-service.md

@@ -39,7 +39,7 @@ ms.service: azure-operator-service-manager
     |User Assigned Identity | Select **identity-for-nginx**
 
 
-    :::image type="content" source="media/create-site-network-service-basic-containerized.png" alt-text="Screenshot showing the basics tab to input project, instance and identity details." lightbox="media/create-site-network-service-basic-containerized.png":::
+    :::image type="content" source="media/create-site-network-service-basic-containerized.png" alt-text="Screenshot showing the basics tab to input project, instance, and identity details." lightbox="media/create-site-network-service-basic-containerized.png":::
 
 1. Select **Next: Choose a Network Site Design >**.
 1. On this screen, select the **Publisher**, **Network Service Design Resource**, and the **Network Service Design Version** you published earlier.
@@ -78,7 +78,7 @@ ms.service: azure-operator-service-manager
 
 You have successfully created a Site Network Service for a Nginx Container as a CNF in Azure. You can now manage and monitor your CNF through the Azure portal.
 
-When you have finished, remember to delete the resources. You can do this by:
+When you have finished, remember to delete the resources. To do this:
 
-1. Deleting the Operator Resource Group.
-1. When the above is complete, deleting the Publisher Resource Group.
+1. Delete the Operator Resource Group.
+1. When step 1 is complete, delete the Publisher Resource Group.

articles/operator-service-manager/quickstart-containerized-network-function-operator.md

@@ -20,7 +20,7 @@ This quickstart contains the prerequisite tasks for Operator and Containerized N
 
 You need an Azure subscription with an existing Resource Group over which you have the _Contributor_ role and the _User Access Administrator_ role.
 
-Alternatively you need the _Contributor_ role over this subscription so that the AOSM CLI extension can create the Resource Group, but you will then need to add  to your user the _User Access Administrator_ role with scope of this newly created Resource Group.
+Alternatively the AOSM CLI extension can create the Resource Group for you, in which case you need the _Contributor_ role over this subscription. If you use this feature, you will need to add to your user the _User Access Administrator_ role with scope of this newly created Resource Group.
 
 You also need the _User Access Administrator_ role over the Network Function Definition Publisher Resource Group. The Network Function Definition Publisher Resource Group was used in [Quickstart: Publish Nginx container as Containerized Network Function (CNF)](quickstart-publish-containerized-network-function-definition.md). Check the input-cnf-nfd.jsonc file for the Resource Group name.
 
@@ -219,7 +219,7 @@ In prior steps, you created a Managed Identity labeled identity-for-nginx-sns in
 
 1. Choose **Add Role Assignment**.
 
-   :::image type="content" source="media/how-to-create-user-assigned-managed-identity-operator.png" alt-text="Screenshot showing identity for nginx sns add role assignment." lightbox="media/how-to-create-user-assigned-managed-identity-operator.png":::
+   :::image type="content" source="media/how-to-create-user-assigned-managed-identity-operator.png" alt-text="Screenshot showing identity for nginx SNS add role assignment." lightbox="media/how-to-create-user-assigned-managed-identity-operator.png":::
 
 1. Select the **Managed Identity Operator** role then proceed with **Next**.
 

articles/operator-service-manager/quickstart-virtualized-network-function-create-site-network-service.md

@@ -104,7 +104,7 @@ Wait for the deployment to reach the 'Succeeded' state. After completion, your V
 
 Congratulations! You have successfully created a Site Network Service for Ubuntu Virtual Machine (VM) as a Virtual Network Function (VNF) in Azure. You can now manage and monitor your Virtual Network Function (VNF) through the Azure portal.
 
-When you have finished, remember to delete the resources. You can do this by:
+When you have finished, remember to delete the resources. To do this:
 
-1. Deleting the Operator Resource Group.
-1. When the above is complete, deleting the Publisher Resource Group.
+1. Delete the Operator Resource Group.
+1. When step 1 is complete, delete the Publisher Resource Group.

articles/operator-service-manager/quickstart-virtualized-network-function-operator.md

@@ -148,7 +148,7 @@ In prior steps, you created a Managed Identity labeled identity-for-ubuntu-vm-sn
 
 1. Under the **Privileged administrator roles**, category pick *Contributor* then proceed with **Next**.
 
-    :::image type="content" source="media/privileged-admin-roles-contributor-ubuntu.png" alt-text="Screenshot showing the Add role assignment window and Contributor with description." lightbox="media/privileged-admin-roles-contributor-ubuntu.png":::
+    :::image type="content" source="media/privileged-admin-roles-contributor-ubuntu.png" alt-text="Screenshot showing the 'Add role assignment' window and Contributor with description." lightbox="media/privileged-admin-roles-contributor-ubuntu.png":::
 
 1. Select **Managed identity**.
 1. Choose **+ Select members** then find and choose the user-assigned managed identity **identity-for-ubuntu-vm-sns**.
@@ -174,7 +174,7 @@ In prior steps, you created a Managed Identity labeled identity-for-ubuntu-vm-sn
 1. Choose **+ Select members** then find and choose the user-assigned managed identity **identity-for-ubuntu-vm-sns**.
 1. Select **Review and assign**.
 
-    :::image type="content" source="media/managed-identity-resource-group-select-members-ubuntu.png" alt-text="Screenshot showing the add role assignment screen with review + assign highlighted." lightbox="media/managed-identity-resource-group-select-members-ubuntu.png":::
+    :::image type="content" source="media/managed-identity-resource-group-select-members-ubuntu.png" alt-text="Screenshot showing the 'Add role assignment' screen with review + assign highlighted." lightbox="media/managed-identity-resource-group-select-members-ubuntu.png":::
 
 ### Grant Managed Identity Operator role to itself
 
@@ -193,7 +193,7 @@ In prior steps, you created a Managed Identity labeled identity-for-ubuntu-vm-sn
 1. Select **Managed identity**.
 1. Select **+ Select members** and navigate to the user-assigned managed identity called *identity-for-ubuntu-vm-sns* and proceed with the assignment.
 
-    :::image type="content" source="media/managed-identity-user-assigned-ubuntu.png" alt-text="Screenshot showing the Add role assignment screen with Managed identity selected." lightbox="media/managed-identity-user-assigned-ubuntu.png":::
+    :::image type="content" source="media/managed-identity-user-assigned-ubuntu.png" alt-text="Screenshot showing the 'Add role assignment' screen with Managed identity selected." lightbox="media/managed-identity-user-assigned-ubuntu.png":::
 
 1. Select **Review and assign**.
 

articles/operator-service-manager/troubleshoot-cli-common-issues.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshooting Azure CLI Azure Operator Service Manager (AOSM) Extension Issues
-description: Learn how to resolve common issues and misconfigurations when using the Az CLI AOSM extension.
+description: Learn how to resolve common issues and misconfigurations when using the Azure CLI AOSM extension.
 author: pjw711
 ms.author: peterwhiting
 ms.service: azure-operator-service-manager
@@ -17,7 +17,7 @@ This document contains a list of common issues when using the Azure CLI AOSM ext
 
 ### Publisher already exists in the region
 
-Publisher names must be unique within an Azure region. If you see the following error, the publisher name you have chosen is already in use:
+Publisher names must be unique within an Azure region. If you see the following error, the publisher name you chose is already in use:
 
 `Message: A private publisher resource with the name 'nginx-publisher' already exists in the provided region.`
 
@@ -27,7 +27,7 @@ To resolve this error:
 
 The publisher is defined in your AOSM CLI extension configuration file. The `publisher_name` and `publisher_resource_group_name` fields must match those of the existing publisher, and it must be in the tenant you are using for this deployment.
 
-Change the `publisher_resource_group_name` in the config file so that it references the existing publisher, re-run the corresponding `build` command, then re-run the `publish` command.
+Change the `publisher_resource_group_name` in the config file so that it references the existing publisher, rerun the corresponding `build` command, then rerun the `publish` command.
 
 **You do not own the existing publisher:**
 
@@ -191,7 +191,7 @@ There are multiple solutions available.
 
 ### CGVs don't match CGS when parameter has null type
 
-Currently, AOSM doesn't support `null` as a default value in deployParameters schema, which means that the default value `null` isn't allowed in Configuration Group Schemas either. To work around this issue, the AOSM CLI sets the default value for parameters of type null to be the string `"null"`, which allows an nfdv to publish successfully.
+Currently, AOSM doesn't support `null` as a default value in deployParameters schema, which means that the default value `null` isn't allowed in Configuration Group Schemas either. To work around this issue, the AOSM CLI sets the default value for parameters of type null to be the string `"null"`, which allows an NFDV to publish successfully.
 
 When using the portal to create CGVs, your parameter autofills to have `"null"` as its value. If you don't change this value, the Portal shows an error message, saying: "New Configuration Group Value doesn't match the schema - please edit the values."