update outputs

Author: tamram

articles/aks/learn/quick-windows-container-deploy-cli.md

@@ -183,13 +183,13 @@ You use [kubectl][kubectl], the Kubernetes command-line client, to manage your K
 
     ```output
     NAME                                STATUS   ROLES   AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION      CONTAINER-RUNTIME
-    aks-nodepool1-90538373-vmss000000   Ready    agent   54m   v1.25.6   10.224.0.33   <none>        Ubuntu 22.04.2 LTS               5.15.0-1035-azure   containerd://1.6.18+azure-1
-    aks-nodepool1-90538373-vmss000001   Ready    agent   55m   v1.25.6   10.224.0.4    <none>        Ubuntu 22.04.2 LTS               5.15.0-1035-azure   containerd://1.6.18+azure-1
-    aksnpwin000000                      Ready    agent   40m   v1.25.6   10.224.0.62   <none>        Windows Server 2022 Datacenter   10.0.20348.1668     containerd://1.6.14+azure
-    ```
+    aks-nodepool1-20786768-vmss000000   Ready    agent   22h   v1.27.7   10.224.0.4    <none>        Ubuntu 22.04.3 LTS               5.15.0-1052-azure   containerd://1.7.5-1
+    aks-nodepool1-20786768-vmss000001   Ready    agent   22h   v1.27.7   10.224.0.33   <none>        Ubuntu 22.04.3 LTS               5.15.0-1052-azure   containerd://1.7.5-1
+    aksnpwin000000                      Ready    agent   20h   v1.27.7   10.224.0.62   <none>        Windows Server 2022 Datacenter   10.0.20348.2159     containerd://1.6.21+azure
+        ```
 
     > [!NOTE]
-    > The container runtime for each node pool is shown under *CONTAINER-RUNTIME*. Notice *aksnpwin987654* begins with `docker://`, which means it uses Docker for the container runtime. Notice *aksnpwcd123456* begins with `containerd://`, which means it uses `containerd` for the container runtime.
+    > The container runtime for each node pool is shown under *CONTAINER-RUNTIME*. The container runtime values begin with `containerd://`, which means that they each use `containerd` for the container runtime.
 
 ## Deploy the application
 
@@ -244,6 +244,8 @@ The ASP.NET sample application is provided as part of the [.NET Framework Sample
 
     For a breakdown of YAML manifest files, see [Deployments and YAML manifests](../concepts-clusters-workloads.md#deployments-and-yaml-manifests).
 
+    If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the **Upload/Download files** button and selecting the file from your local file system.
+
 1. Deploy the application using the [kubectl apply][kubectl-apply] command and specify the name of your YAML manifest.
 
     ```console

articles/aks/learn/quick-windows-container-deploy-portal.md

@@ -112,8 +112,11 @@ You use [kubectl][kubectl], the Kubernetes command-line client, to manage your K
 
     ```output
     NAME                                STATUS   ROLES   AGE     VERSION
-    aks-nodepool1-12345678-vmssfedcba   Ready    agent   13m     v1.16.7
-    aksnpwin987654                      Ready    agent   108s    v1.16.7
+    aks-agentpool-41946322-vmss000001   Ready    agent   7m51s   v1.27.7
+    aks-agentpool-41946322-vmss000002   Ready    agent   7m5s    v1.27.7
+    aks-npwin-41946322-vmss000000       Ready    agent   7m43s   v1.27.7
+    aks-userpool-41946322-vmss000001    Ready    agent   7m47s   v1.27.7
+    aks-userpool-41946322-vmss000002    Ready    agent   6m57s   v1.27.7
     ```
 
 ---
@@ -171,7 +174,8 @@ The ASP.NET sample application is provided as part of the [.NET Framework Sample
 
     For a breakdown of YAML manifest files, see [Deployments and YAML manifests](../concepts-clusters-workloads.md#deployments-and-yaml-manifests).
 
-1. If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the **Upload/Download files** button and selecting the file from your local file system.
+    If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the **Upload/Download files** button and selecting the file from your local file system.
+
 1. Deploy the application using the [`kubectl apply`][kubectl-apply] command and specify the name of your YAML manifest.
 
     ```console

articles/aks/learn/quick-windows-container-deploy-powershell.md

@@ -170,9 +170,10 @@ You use [kubectl][kubectl], the Kubernetes command-line client, to manage your K
     The following sample output shows all the nodes in the cluster. Make sure the status of all nodes is **Ready**:
 
     ```output
-    NAME                                STATUS   ROLES   AGE    VERSION
-    aks-nodepool1-12345678-vmssfedcba   Ready    agent   13m    v1.16.7
-    aksnpwin987654                      Ready    agent   108s   v1.16.7
+    NAME                                STATUS   ROLES   AGE   VERSION
+    aks-nodepool1-20786768-vmss000000   Ready    agent   22h   v1.27.7
+    aks-nodepool1-20786768-vmss000001   Ready    agent   22h   v1.27.7
+    aksnpwin000000                      Ready    agent   21h   v1.27.7
     ```
 
 ## Deploy the application
@@ -228,6 +229,8 @@ The ASP.NET sample application is provided as part of the [.NET Framework Sample
 
     For a breakdown of YAML manifest files, see [Deployments and YAML manifests](../concepts-clusters-workloads.md#deployments-and-yaml-manifests).
 
+    If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the **Upload/Download files** button and selecting the file from your local file system.
+
 2. Deploy the application using the [kubectl apply][kubectl-apply] command and specify the name of your YAML manifest.
 
     ```azurepowershell