edit pass: azure-operator-service-manager-overview-how-to

Author: ShawnJackson

articles/operator-service-manager/azure-operator-service-manager-overview.md

@@ -19,17 +19,17 @@ Azure Operator Service Manager caters to large-scale operator environments. It a
 
 Managing a complex network service lifecycle efficiently and reliably can be a challenge. Azure Operator Service Manager offers a unique approach that introduces curated experiences for publishers, designers, and operators.
 
-The publisher role first onboards the network function to create a network function description (NFD). The designer role then onboards the network service to create a network service design (NSD) and configuration group schema (CGS). The operator role deploys a site network service to provide the site and runtime configuration group values (CGVs). These personas deploy a complete service stack that stretches across platforms, software, and configuration requirements, as illustrated in the following workflows.
+The publisher role first onboards the network function (NF) to create a network function description (NFD). The designer role then onboards the network service to create a network service design (NSD) and configuration group schema (CGS). The operator role deploys a site network service to provide configuration group values (CGVs) for the site and runtime. These personas deploy a complete service stack that stretches across platforms, software, and configuration requirements, as illustrated in the following workflows.
 
 :::image type="content" source="media/overview-deployment-workflows.png" alt-text="Diagram that shows Azure Operator Service Manager deployment workflows." lightbox="media/overview-deployment-workflows-lightbox.png":::
 
 ## Product features
 
 ### Orchestration of service platforms
 
-The deep integration of Azure Operator Service Manager with Azure Operator Nexus helps ensure comprehensive coverage of infrastructure operations required for any network function type.
+The deep integration of Azure Operator Service Manager with Azure Operator Nexus helps ensure comprehensive coverage of infrastructure operations that any NF type requires.
 
-For virtual network functions (VNFs), create L2/L3 isolation domains, network resources, the trunk, and content service network (CSN) resources. For container network functions (CNFs), create the initial Nexus Azure Kubernetes Service (NAKS) cluster, finalize the cluster, and then test the cluster for standards/security compliance.
+For virtual network functions (VNFs), create Layer 2 and Layer 3 isolation domains, network resources, the trunk, and content service network (CSN) resources. For container network functions (CNFs), create the initial Nexus Azure Kubernetes Service (NAKS) cluster, finalize the cluster, and then test the cluster for standards/security compliance.
 
 ### Flexible service composition
 
@@ -73,7 +73,7 @@ Services installed on the customer edge cluster undergo rigorous security testin
 
 ### Automation and AI
 
-Achieve continuous integration and delivery by combining Azure Operator Service Manager with Azure DevOps. Pull new software releases directly from the latest repository, deploy by using Azure safe practices, and scale from one site to thousands of sites.
+Achieve continuous integration and continuous delivery (CI/CD) by combining Azure Operator Service Manager with Azure DevOps. Pull new software releases directly from the latest repository, deploy by using Azure safe practices, and scale from one site to thousands of sites.
 
 Go further by influencing workflow decisions with data-driven insights and actions. Integrate with any Azure analytics or AI services, including Microsoft Fabric, Azure Data Explorer, Azure Logic Apps, and Microsoft Copilot.
 

articles/operator-service-manager/how-to-cancel-service-deployments.md

@@ -14,15 +14,15 @@ This article describes a method to interrupt a site network service (SNS) deploy
 
 ## Why interrupt a service deployment operation
 
-Azure Operator Service Manager deploys complex CNF workloads, which consist of many individual components (Helm charts). When you start an SNS deployment, each component is processed sequentially, in the order defined in the network function design (NFD). Depending on how many components are touched in a deployment, the SNS operation can take an extended time to finish.
+Azure Operator Service Manager deploys complex CNF workloads, which consist of many individual components (Helm charts). When you start an SNS deployment, each component is processed sequentially, in the order that the network function design (NFD) defines. Depending on how many components are touched in a deployment, the SNS operation can take an extended time to finish.
 
 As an example, consider a scenario where a CNF has 30 components. Each component takes 5 minutes to deploy. The total run time of this operation would exceed 2 hours. Now, consider operational issues with long-running deployment operations:
 
 * Users might want to test the deployment operation only up to a certain component.
 * Users might realize, after starting the operation, that an error exists in a component configuration.
 * The operation might create an unexpected negative impact on a customer-facing service.
 
-In such cases, an ability to interrupt the operation is desirable. Before the introduction of this interruption capability, the only option was to wait for the defective component to fail. With this interruption capability, you can proactively interrupt long-running deployments before they reach the defective component. This capability minimizes delays and improves operational agility.
+In such cases, an ability to interrupt the operation is desirable. Before the introduction of this interruption capability, the only option was to wait for the defective component to fail. With this interruption capability, you can proactively interrupt long-running deployments before they reach the defective component. This interruption minimizes delays and improves operational agility.
 
 ## Overview of service deployment operations
 

articles/operator-service-manager/manage-network-function-operator.md

@@ -55,7 +55,7 @@ az k8s-extension create --cluster-name
 
 `--cluster-type -t`
 
-* Specify Azure Arc clusters, Azure Kubernetes Service (AKS) managed clusters, Azure Arc appliances, or provisioned clusters.
+* Specify Azure Arc clusters, Azure Kubernetes Service (AKS) managed clusters, Azure Arc appliances, or `provisionedClusters`.
 * Accepted values: `connectedClusters`.
 
 `--extension-type`
@@ -108,7 +108,7 @@ az k8s-extension create --cluster-name
 `--config global.networkfunctionextension.webhook.pod.mutation.matchConditionExpression=`
 
 * This configuration is an optional parameter. It comes into play only when container network functions (CNFs) are installed in the corresponding release namespace.  
-* This configuration configures more granular control on top of rules and `namespaceSelectors`.
+* This configuration sets more granular control on top of rules and `namespaceSelectors`.
 * Default value:
 
   ```bash
@@ -118,7 +118,7 @@ az k8s-extension create --cluster-name
   The referenced match condition implies that the pods getting accepted in the `kube-system` namespace are mutated only if they have at least one of the following labels: `app == "commissioning"`, `app == "descheduler"`, or `name == "cert-exporter"`. Otherwise, they aren't mutated and continue to be pulled from the original source in accordance with the Helm chart of the CNF, component, or application.  
 * Accepted value: Any valid Common Expression Language (CEL) expression.
 * You can set or update this parameter during installation or update of the NFO extension.  
-* This condition comes into play only when the CNF, component, or application is being installed into the namespace in accordance with the rules and `namespaceSelectors`. If you create more pods in that namespace, this condition is applied.
+* This condition comes into play only when you're installing the CNF, component, or application into the namespace in accordance with the rules and `namespaceSelectors`. If you create more pods in that namespace, this condition is applied.
 
 #### Cluster registry
 
@@ -187,14 +187,14 @@ az k8s-extension create --cluster-name
 `--config global.networkfunctionextension.clusterRegistry.storageSize=`
 
 * You must provide this configuration when `global.networkfunctionextension.enableClusterRegistry=true`.
-* This configuration configures the size that we reserve for the cluster registry.
+* This configuration sets the size that we reserve for the cluster registry.
 * This configuration uses units as Gi and Ti for sizing.
 * Default value: `100Gi`
 
 `--config global.networkfunctionextension.clusterRegistry.clusterRegistryGCCadence=`
 
 * You must provide this configuration as a schedule in standard Unix Crontab format.
-* This configuration specified as an empty string disables the scheduled job, allowing customers to opt out of running garbage collection.
+* This configuration, specified as an empty string, disables the scheduled job so that you can opt out of running garbage collection.
 * Default value: `0 0 * * *`. Runs the job once every day.
 
 `--config global.networkfunctionextension.clusterRegistry.clusterRegistryGCThreshold=`