update to improve readability

Author: MGoedtel

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

@@ -93,17 +93,17 @@ The following list is the cluster inventory data collected by default:
 
 The estimation below is based on an Azure Kubernetes Service (AKS) cluster with the following sizing example. Also, the estimate applies only for metrics and inventory data collected. For container logs (stdout, stderr, and environmental variables), it varies based on the log sizes generated by the workload, and they are excluded from our estimation.
 
-If you enabled monitoring of an AKS cluster configured as follows:
+If you enabled monitoring of an AKS cluster configured as follows,
 
 - Three nodes
 - Two disks per node
 - One network interface per node
-- 20 pods (1 container in each pod = 20 containers in total)
+- 20 pods (one container in each pod = 20 containers in total)
 - Two Kubernetes namespaces
 - Five Kubernetes services (includes kube-system pods, services, and namespace)
 - Collection frequency = 60 secs (default)
 
-You can see the tables and volume of data generated per hour in the assigned Log Analytics workspace. For additional information about each of these tables, see [Container records](container-insights-log-search.md#container-records).
+you can see the tables and volume of data generated per hour in the assigned Log Analytics workspace. For more information about each of these tables, see [Container records](container-insights-log-search.md#container-records).
 
 |Table | Size estimate (MB/hour) |
 |------|---------------|
@@ -116,7 +116,7 @@ You can see the tables and volume of data generated per hour in the assigned Log
 |KubeHealth | 0.1 |
 |KubeMonAgentEvents |0.005 |
 
-Total = 31 MB/Hour = 23.1 GB/month (1 month = 31 days)
+Total = 31 MB/Hour = 23.1 GB/month (one month = 31 days)
 
 Using the default pricing for Log Analytics, which is a Pay-As-You-Go model ($2.30 per GB), the monthly Azure Monitor cost would be $52.90 per month. After including a capacity reservation, the price could range from $47.82 to $54.20 per month depending on the reservation selected.
 
@@ -148,7 +148,7 @@ The following are examples of what changes you can apply to your cluster by modi
           enabled = false
     ```
 
-2. Disable collecting stderr logs from your development namespace (e.g. **dev-test**), and continue collecting stderr logs from other namespaces (e.g. **prod** and **default**) by modifying the following in the ConfigMap file:
+2. Disable collecting stderr logs from your development namespace (for example, **dev-test**), and continue collecting stderr logs from other namespaces (for example, **prod** and **default**) by modifying the following in the ConfigMap file:
 
     >[!NOTE]
     >Note: kube-system log collection is disabled by default. The default setting is retained, adding **dev-test** namespace to the list of exclusion namespaces is applied to stderr log collection.
@@ -166,7 +166,7 @@ The following are examples of what changes you can apply to your cluster by modi
         enabled = false
     ```
 
-4. To clean up completed jobs, specify the clean up policy in the job definition by modifying the following in the ConfigMap file:
+4. To clean up completed jobs, specify the cleanup policy in the job definition by modifying the following in the ConfigMap file:
 
     ```
     apiVersion: batch/v1
@@ -185,9 +185,9 @@ If you are utilizing [Prometheus metric scraping](container-insights-prometheus-
 
 - Ensure scraping frequency is set optimally (the default is 60 seconds). While you can increase the frequency to 15 seconds, you need to ensure that the metrics you are scraping are published at that frequency. Otherwise there will be many duplicate metrics scraped and sent to your Log Analytics workspace at intervals adding to data ingestion and retention costs, but are of less value. 
 
-- Azure Monitor for containers supports exclusion & inclusion lists by metric name. For example, if you are scraping **kubedns** metrics in your cluster, there might be hundreds of them that gets scraped by default, but you are most likely only interested in a subset. Confirm you specified a list of metrics to scrape, or exclude others except a few to save on data ingestion volume. It is very easy to enable scraping and not use many of those metrics, which will only add additional charges to your Log Analytics bill.
+- Azure Monitor for containers supports exclusion & inclusion lists by metric name. For example, if you are scraping **kubedns** metrics in your cluster, there might be hundreds of them that gets scraped by default, but you are most likely only interested in a subset. Confirm you specified a list of metrics to scrape, or exclude others except a few to save on data ingestion volume. It is easy to enable scraping and not use many of those metrics, which will only add additional charges to your Log Analytics bill.
 
-- When scraping through pod annotations, ensure you filter by namespace so that you exclude scraping of pod metrics from namespaces that you don't use (e.g. **dev-test** namespace).
+- When scraping through pod annotations, ensure you filter by namespace so that you exclude scraping of pod metrics from namespaces that you don't use (for example, **dev-test** namespace).
 
 ## Next steps