etherscan-io
diff --git a/‎articles/azure-monitor/insights/container-insights-optout.md
+1-1 b/‎articles/azure-monitor/insights/container-insights-optout.md
+1-1
diff --git a/‎articles/azure-monitor/insights/container-insights-overview.md
+1-1 b/‎articles/azure-monitor/insights/container-insights-overview.md
+1-1
diff --git a/‎articles/azure-monitor/insights/container-insights-troubleshoot.md
+1-1 b/‎articles/azure-monitor/insights/container-insights-troubleshoot.md
+1-1
diff --git a/‎articles/azure-monitor/insights/containers.md
+31-46 b/‎articles/azure-monitor/insights/containers.md
+31-46
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-dash01.png
17.7 KB b/‎articles/azure-monitor/insights/media/containers/containers-dash01.png
17.7 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-dash02.png
53.7 KB b/‎articles/azure-monitor/insights/media/containers/containers-dash02.png
53.7 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-failed04.png
37.2 KB b/‎articles/azure-monitor/insights/media/containers/containers-failed04.png
37.2 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-log-search.png
13.8 KB b/‎articles/azure-monitor/insights/media/containers/containers-log-search.png
13.8 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-queries.png
-4.9 KB b/‎articles/azure-monitor/insights/media/containers/containers-queries.png
-4.9 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-state-failed-select.png
31.7 KB b/‎articles/azure-monitor/insights/media/containers/containers-state-failed-select.png
31.7 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-state-failed.png
28 KB b/‎articles/azure-monitor/insights/media/containers/containers-state-failed.png
28 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-status.png
7.22 KB b/‎articles/azure-monitor/insights/media/containers/containers-status.png
7.22 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/containers-title.png
3.88 KB b/‎articles/azure-monitor/insights/media/containers/containers-title.png
3.88 KB
diff --git a/‎articles/azure-monitor/insights/media/containers/search-ubuntu.png
70.5 KB b/‎articles/azure-monitor/insights/media/containers/search-ubuntu.png
70.5 KB
@@ -22,7 +22,7 @@ After you enable monitoring of your AKS cluster, you can stop monitoring the clu
 
 
 ## Azure CLI
-Use the [az aks disable-addons](https://docs.microsoft.com/cli/azure/aks?view=azure-cli-latest#az-aks-disable-addons) command to disable Azure Monitor for containers. The command removes the agent from the cluster nodes, it does not remove the solution or the data already collected and stored in your Log Analytics resource.  
+Use the [az aks disable-addons](https://docs.microsoft.com/cli/azure/aks?view=azure-cli-latest#az-aks-disable-addons) command to disable Azure Monitor for containers. The command removes the agent from the cluster nodes, it does not remove the solution or the data already collected and stored in your Azure Monitor resource.  
 
 ```azurecli
 az aks disable-addons -a monitoring -n MyExistingManagedCluster -g MyExistingManagedClusterRG
 
@@ -19,7 +19,7 @@ ms.author: magoedte
 
 Azure Monitor for containers is a feature designed to monitor the performance of container workloads deployed to either Azure Container Instances or managed Kubernetes clusters hosted on Azure Kubernetes Service (AKS). Monitoring your containers is critical, especially when you're running a production cluster, at scale, with multiple applications.
 
-Azure Monitor for containers gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. Container logs are also collected.  After you enable monitoring from Kubernetes clusters, these metrics and logs are automatically collected for you through a containerized version of the Log Analytics agent for Linux and stored in your [Log Analytics](../../azure-monitor/log-query/log-query-overview.md) workspace. 
+Azure Monitor for containers gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. Container logs are also collected.  After you enable monitoring from Kubernetes clusters, these metrics and logs are automatically collected for you through a containerized version of the Log Analytics agent for Linux and stored in your [Log Analytics](../log-query/log-query-overview.md) workspace. 
 
 ## What does Azure Monitor for containers provide?
 
 
@@ -20,7 +20,7 @@ ms.author: magoedte
 When you configure monitoring of your Azure Kubernetes Service (AKS) cluster with Azure Monitor for containers, you may encounter an issue preventing data collection or reporting status. This article details some common issues and troubleshooting steps.
 
 ## Azure Monitor for containers is enabled but not reporting any information
-If Azure Monitor for containers is successfully enabled and configured, but you cannot view status information or no results are returned from a Log Analytics log query, you diagnose the problem by following these steps: 
+If Azure Monitor for containers is successfully enabled and configured, but you cannot view status information or no results are returned from a log query, you diagnose the problem by following these steps: 
 
 1. Check the status of the agent by running the command: