Additional changes.

Author: TimShererWithAquent

articles/azure-monitor/insights/container-insights-enable-existing-clusters.md

@@ -77,7 +77,7 @@ If you would rather integrate with an existing workspace, perform the following
 
     The output will resemble the following:
 
-    ```azurecli
+    ```output
     provisioningState       : Succeeded
     ```
 
@@ -268,7 +268,7 @@ If you choose to use the Azure CLI, you first need to install and use the CLI lo
 
        The configuration change can take a few minutes to complete. When it's completed, a message is displayed that's similar to the following and includes the result:
 
-       ```powershell
+       ```output
        provisioningState       : Succeeded
        ```
 
@@ -302,7 +302,7 @@ kubectl get ds omsagent --namespace=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:
 
-```
+```output
 User@aksuser:~$ kubectl get ds omsagent --namespace=kube-system
 NAME       DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
 omsagent   2         2         2         2            2           beta.kubernetes.io/os=linux   1d
@@ -316,7 +316,7 @@ kubectl get deployment omsagent-rs -n=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:
 
-```
+```output
 User@aksuser:~$ kubectl get deployment omsagent-rs -n=kube-system
 NAME       DESIRED   CURRENT   UP-TO-DATE   AVAILABLE    AGE
 omsagent   1         1         1            1            3h
@@ -332,7 +332,7 @@ kubectl get ds omsagent --namespace=kube-system
 
 The output should resemble the following, which indicates that it was deployed properly:  
 
-```
+```output
 User@aksuser:~$ kubectl get ds omsagent --namespace=kube-system
 NAME       DESIRED   CURRENT   READY     UP-TO-DATE   AVAILABLE   NODE SELECTOR                 AGE
 omsagent   2         2         2         2            2           beta.kubernetes.io/os=linux   1d

articles/azure-monitor/insights/container-insights-optout-openshift.md

@@ -118,7 +118,7 @@ New-AzResourceGroupDeployment -Name opt-out -ResourceGroupName <ResourceGroupNam
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```powershell
+```output
 ProvisioningState       : Succeeded
 ```
 

articles/azure-monitor/insights/container-insights-optout.md

@@ -153,7 +153,7 @@ New-AzResourceGroupDeployment -Name opt-out -ResourceGroupName <ResourceGroupNam
 
 The configuration change can take a few minutes to complete. When it's completed, a message similar to the following that includes the result is returned:
 
-```powershell
+```output
 ProvisioningState       : Succeeded
 ```
 

articles/container-registry/container-registry-faq.md

@@ -147,13 +147,13 @@ docker push myregistry.azurecr.io/1gb:latest
 
 You should be able to see that the storage usage has increased in the Azure portal, or you can query usage using the CLI.
 
-```bash
+```azurecli
 az acr show-usage -n myregistry
 ```
 
 Delete the image using the Azure CLI or portal and check the updated usage in a few minutes.
 
-```bash
+```azurecli
 az acr repository delete -n myregistry --image 1gb
 ```
 
@@ -217,7 +217,7 @@ ACR supports [custom roles](container-registry-roles.md) that provide different
 
   Or, assign the role to a service principle identified by its application ID:
 
-  ```
+  ```azurecli
   az role assignment create --scope resource_id --role AcrPull --assignee 00000000-0000-0000-0000-000000000000
   ```