[Doc-a-thon] Code block updated

Author: msaenzbosupport

articles/aks/availability-zones.md

@@ -94,13 +94,13 @@ az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
 
 Next, use the [kubectl describe][kubectl-describe] command to list the nodes in the cluster and filter on the `topology.kubernetes.io/zone` value. The following example is for a Bash shell.
 
-```bash
+```azurecli-interactive
 kubectl describe nodes | grep -e "Name:" -e "topology.kubernetes.io/zone"
 ```
 
 The following example output shows the three nodes distributed across the specified region and availability zones, such as *eastus2-1* for the first availability zone and *eastus2-2* for the second availability zone:
 
-```console
+```output
 Name:       aks-nodepool1-28993262-vmss000000
             topology.kubernetes.io/zone=eastus2-1
 Name:       aks-nodepool1-28993262-vmss000001
@@ -113,13 +113,13 @@ As you add more nodes to an agent pool, the Azure platform automatically distrib
 
 With Kubernetes versions 1.17.0 and later, AKS uses the newer label `topology.kubernetes.io/zone` and the deprecated `failure-domain.beta.kubernetes.io/zone`. You can get the same result from running the `kubelet describe nodes` command in the previous step, by running the following script:
 
- ```console
+ ```azurecli-interactive
 kubectl get nodes -o custom-columns=NAME:'{.metadata.name}',REGION:'{.metadata.labels.topology\.kubernetes\.io/region}',ZONE:'{metadata.labels.topology\.kubernetes\.io/zone}'
 ```
 
 The following example resembles the output with more verbose details:
 
-```console
+```output
 NAME                                REGION   ZONE
 aks-nodepool1-34917322-vmss000000   eastus   eastus-1
 aks-nodepool1-34917322-vmss000001   eastus   eastus-2
@@ -139,7 +139,7 @@ az aks scale \
 
 When the scale operation completes after a few minutes, run the command `kubectl describe nodes | grep -e "Name:" -e "topology.kubernetes.io/zone"` in a Bash shell. The following output resembles the results:
 
-```console
+```output
 Name:       aks-nodepool1-28993262-vmss000000
             topology.kubernetes.io/zone=eastus2-1
 Name:       aks-nodepool1-28993262-vmss000001
@@ -154,14 +154,14 @@ Name:       aks-nodepool1-28993262-vmss000004
 
 You now have two more nodes in zones 1 and 2. You can deploy an application consisting of three replicas. The following example uses NGINX:
 
-```bash
+```azurecli-interactive
 kubectl create deployment nginx --image=mcr.microsoft.com/oss/nginx/nginx:1.15.5-alpine
 kubectl scale deployment nginx --replicas=3
 ```
 
 By viewing nodes where your pods are running, you see pods are running on the nodes corresponding to three different availability zones. For example, with the command `kubectl describe pod | grep -e "^Name:" -e "^Node:"` in a Bash shell, you see the following example output:
 
-```console
+```output
 Name:         nginx-6db489d4b7-ktdwg
 Node:         aks-nodepool1-28993262-vmss000000/10.240.0.4
 Name:         nginx-6db489d4b7-v7zvj