Acrolinx improvements

Author: allyford

articles/aks/upgrade-windows-2019-2022.md

@@ -9,14 +9,14 @@ ms.author: viniap
 
 # Upgrade Kubernetes workloads from Windows Server 2019 to 2022
 
-Upgrading the OS version of a running Windows workload on Azure Kubernetes Service (AKS) requires you to deploy a new node pool as Windows versions must match on each node pool. This article describes the steps to upgrade the OS version for Windows workloads as well as other important aspects.
+Upgrading the OS version of a running Windows workload on Azure Kubernetes Service (AKS) requires you to deploy a new node pool as Windows versions must match on each node pool. This article describes the steps to upgrade the OS version for Windows workloads and other important aspects.
 
 > [!NOTE]
 > Windows Server 2019 is being retired after Kubernetes version 1.32 reaches end of life (EOL) and won't be supported in future releases. For more information about this retirement, see the [AKS release notes][aks-release-notes].
 
 ## Limitations
 
-Windows Server 2019 and Windows Server 2022 cannot co-exist on the same node pool on AKS. A new node pool must be created to host the new OS version. It's important that you match the permissions and access of the previous node pool to the new one.
+Windows Server 2019 and Windows Server 2022 can't co-exist on the same node pool on AKS. A new node pool must be created to host the new OS version. It's important that you match the permissions and access of the previous node pool to the new one.
 
 ## Before you begin
 
@@ -30,7 +30,7 @@ Windows Server 2019 and Windows Server 2022 cannot co-exist on the same node poo
 
 ## Add a Windows Server 2022 node pool to the existing cluster
 
-Windows Server 2019 and 2022 cannot co-exist on the same node pool on AKS. To upgrade your application, you need a separate node pool for Windows Server 2022.
+Windows Server 2019 and 2022 can't co-exist on the same node pool on AKS. To upgrade your application, you need a separate node pool for Windows Server 2022.
 For more information on how to add a new Windows Server 2022 node pool to an existing AKS cluster, see [Add a Windows Server 2022 node pool](./learn/quick-windows-container-deploy-cli.md).
 
 ## Update your YAML file
@@ -42,7 +42,7 @@ Node Selector is the most common and recommended option for placement of Windows
         "kubernetes.io/os": windows
 ```
 
-The above annotation will find *any* Windows node available and place the pod on that node (of course, following all other scheduling rules). When upgrading from Windows Server 2019 to Windows Server 2022, you need to enforce not only the placement on a Windows node, but also on a node that is running the latest OS version. To accomplish this, one option is to use a different annotation:
+The above annotation finds *any* Windows node available and place the pod on that node (following all other scheduling rules). When upgrading from Windows Server 2019 to Windows Server 2022, you need to enforce not only the placement on a Windows node, but also on a node that is running the latest OS version. To accomplish this, one option is to use a different annotation:
 
 ```yaml
       nodeSelector:
@@ -52,16 +52,16 @@ The above annotation will find *any* Windows node available and place the pod on
 Once you update the nodeSelector on the YAML file, you should also update the container image to be used. You can get this information from the previous step on which you created a new version of the containerized application by changing the FROM statement on your dockerfile.
 
 > [!NOTE]
-> You should leverage the same YAML file you used to deploy the application in the first place - this will ensure no other configuration is changed, only the nodeSelector and the image to be used.
+> You should leverage the same YAML file you used to deploy the application in the first place - this ensures no other configuration is changed, only the nodeSelector and the image to be used.
 
 ## Apply the new YAML file to the existing workload
 
-If you have an application deployed already, ensure you follow the steps recommended above to deploy a new node pool with Windows Server 2022 nodes. Once deployed, your environment will show Windows Server 2019 and 2022 nodes, with the workloads running on the 2019 nodes:
+If you have an application deployed already, follow the recommended steps to deploy a new node pool with Windows Server 2022 nodes. Once deployed, your environment will show Windows Server 2019 and 2022 nodes, with the workloads running on the 2019 nodes:
 
 ```console
 kubectl get nodes -o wide
 ```
-The command above will show all nodes on your AKS cluster with additional details on the output:
+This command shows all nodes on your AKS cluster with extra details on the output:
 
 ```output
 NAME                                STATUS   ROLES   AGE     VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION     CONTAINER-RUNTIME
@@ -80,18 +80,18 @@ With the Windows Server 2022 node pool deployed and the YAML file configured, yo
 kubectl apply -f <filename>
 ```
 
-The command above should return a "configured" status for the deployment:
+This command should return a "configured" status for the deployment:
 
 ```output
 deployment.apps/sample configured
 service/sample unchanged
 ```
-At this point, AKS will start the process of terminating the existing pods and deploying new pods to the Windows Server 2022 nodes. You can check the status of your deployment by running:
+At this point, AKS starts the process of terminating the existing pods and deploying new pods to the Windows Server 2022 nodes. You can check the status of your deployment by running:
 
 ```console
 kubectl get pods -o wide
 ```
-The command above return the status of the pods on the default namespace. You might need to change the command above to list the pods on specific namespaces. 
+This command return the status of the pods on the default namespace. You might need to change the command above to list the pods on specific namespaces. 
 
 ```output
 NAME                      READY   STATUS    RESTARTS   AGE     IP             NODE              NOMINATED NODE   READINESS GATES
@@ -102,6 +102,6 @@ sample-7794bfcc4c-sh78c   1/1     Running   0          2m49s   10.240.0.228   ak
 
 ## Active Directory, gMSA and Managed Identity implications
 
-If you are leveraging Group Managed Service Accounts (gMSA) you will need to update the Managed Identity configuration for the new node pool. gMSA uses a secret (user account and password) so the node on which the Windows pod is running can authenticate the container against Active Directory. To access that secret on Azure Key Vault, the node uses a Managed Identity that allows the node to access the resource. Since Managed Identities are configured per node pool, and the pod now resides on a new node pool, you need to update that configuration. Check out [Enable Group Managed Service Accounts (GMSA) for your Windows Server nodes on your Azure Kubernetes Service (AKS) cluster](./use-group-managed-service-accounts.md) for more information.
+If you're using Group Managed Service Accounts (gMSA), update the Managed Identity configuration for the new node pool. gMSA uses a secret (user account and password) so the node on which the Windows pod is running can authenticate the container against Active Directory. To access that secret on Azure Key Vault, the node uses a Managed Identity that allows the node to access the resource. Since Managed Identities are configured per node pool, and the pod now resides on a new node pool, you need to update that configuration. Check out [Enable Group Managed Service Accounts (GMSA) for your Windows Server nodes on your Azure Kubernetes Service (AKS) cluster](./use-group-managed-service-accounts.md) for more information.
 
 The same principle applies to Managed Identities used for any other pod/node pool when accessing other Azure resources. Any access provided via Managed Identity needs to be updated to reflect the new node pool. To view update and sign-in activities, see [How to view Managed Identity activity](../active-directory/managed-identities-azure-resources/how-to-view-managed-identity-activity.md).

articles/aks/use-windows-hpc.md

@@ -18,13 +18,13 @@ A privileged DaemonSet can carry out changes or monitor a Linux host on Kubernet
 
 * HostProcess containers require Kubernetes 1.23 or greater.
 * HostProcess containers require `containerd` 1.6 or higher container runtime.
-* HostProcess pods can only contain HostProcess containers. This is a current limitation of the Windows operating system. Non-privileged Windows containers can't share a vNIC with the host IP namespace.
+* HostProcess pods can only contain HostProcess containersdue to a limitation on the Windows operating system.Non-privileged Windows containers can't share a vNIC with the host IP namespace.
 * HostProcess containers run as a process on the host. The only isolation those containers have from the host is the resource constraints imposed on the HostProcess user account.
 * Filesystem isolation and Hyper-V isolation aren't supported for HostProcess containers.
 * Volume mounts are supported and are mounted under the container volume. See Volume Mounts.
 * A limited set of host user accounts are available for Host Process containers by default. See Choosing a User Account.
 * Resource limits such as disk, memory, and cpu count, work the same way as fashion as processes on the host.
-* Named pipe mounts and Unix domain sockets are not directly supported, but can be accessed on their host path, for example `\\.\pipe\*`.
+* Named pipe mounts and Unix domain sockets aren't directly supported, but can be accessed on their host path, for example `\\.\pipe\*`.
 
 
 ## Run a HostProcess workload
@@ -44,7 +44,7 @@ To use HostProcess features with your deployment, set *hostProcess: true* and *h
       ...
 ```
 
-To run an example workload that uses HostProcess features on an existing AKS cluster with Windows nodes, create `hostprocess.yaml` with the following:
+To run an example workload that uses HostProcess features on an existing AKS cluster with Windows nodes, create `hostprocess.yaml` with the following contents:
 
 ```yaml
 apiVersion: apps/v1
@@ -96,7 +96,7 @@ $ kubectl apply -f hostprocess.yaml
 daemonset.apps/privileged-daemonset created
 ```
 
-You can verify your workload use the features of HostProcess by view the pod's logs.
+Verify that your workload uses the features of HostProcess containers by viewing the pod's logs.
 
 Use `kubectl` to find the name of the pod in the `kube-system` namespace.
 
@@ -118,7 +118,7 @@ Process has admin rights:
 
 ## Next steps
 
-For more details on HostProcess containers and Microsoft's contribution to Kubernetes upstream, see the [Alpha in v1.22: Windows HostProcess Containers][blog-post].
+For more information on HostProcess containers and Microsoft's contribution to Kubernetes upstream, see the [Alpha in v1.22: Windows HostProcess Containers][blog-post].
 
 
 <!-- LINKS - External -->