Apply suggestions from code review

Acro Correctness edits.

Author: v-stsavell

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

@@ -42,7 +42,7 @@ Node Selector is the most common and recommended option for placement of Windows
         "kubernetes.io/os": windows
 ```
 
-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:
+The above annotation finds *any* Windows node available and places 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:
@@ -91,7 +91,7 @@ At this point, AKS starts the process of terminating the existing pods and deplo
 ```console
 kubectl get pods -o wide
 ```
-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. 
+This command returns 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

articles/aks/use-windows-hpc.md

@@ -18,7 +18,7 @@ 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 containersdue to a limitation on the Windows operating system.Non-privileged Windows containers can't share a vNIC with the host IP namespace.
+* HostProcess pods can only contain HostProcess containers due 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.