Merge pull request #236604 from msaenzbosupport/patch-11

[Doc-A-thon] Updating code block

Author: prmerger-automator[bot]

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

@@ -58,7 +58,7 @@ Once you update the nodeSelector on the YAML file, you should also update the co
 
 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
+```bash
 kubectl get nodes -o wide
 ```
 This command shows all nodes on your AKS cluster with extra details on the output:
@@ -76,7 +76,7 @@ akswspool000002                     Ready    agent   5h37m   v1.23.8   10.240.0.
 
 With the Windows Server 2022 node pool deployed and the YAML file configured, you can now deploy the new version of the YAML:
 
-```console
+```bash
 kubectl apply -f <filename>
 ```
 
@@ -88,7 +88,7 @@ service/sample unchanged
 ```
 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
+```bash
 kubectl get pods -o wide
 ```
 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. 
@@ -104,4 +104,4 @@ sample-7794bfcc4c-sh78c   1/1     Running   0          2m49s   10.240.0.228   ak
 
 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).
+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).