edit pass: essentials-articles-batch-3

Author: paulth1

articles/azure-monitor/essentials/collect-custom-metrics-guestos-resource-manager-vm.md

@@ -1,5 +1,5 @@
 ---
-title: Collect Windows VM metrics in Azure Monitor with template
+title: Collect Windows VM metrics in Azure Monitor with a template
 description: Send guest OS metrics to the Azure Monitor metric database store by using a Resource Manager template for a Windows virtual machine.
 author: anirudhcavale
 services: azure-monitor
@@ -10,7 +10,7 @@ ms.author: bwren
 ---
 # Send guest OS metrics to the Azure Monitor metric store by using an ARM template for a Windows VM
 
-Performance data from the guest OS of Azure virtual machines (VMs) isn't collected automatically like other [platform metrics](./monitor-azure-resource.md#monitoring-data). Install the Azure Monitor [diagnostics extension](../agents/diagnostics-extension-overview.md) to collect guest OS metrics into the metrics database so that it can be used with all features of Azure Monitor Metrics. These features include near real time alerting, charting, routing, and access from a REST API. This article describes the process for sending guest OS performance metrics for a Windows VM to the metrics database by using an Azure Resource Manager template (ARM template).
+Performance data from the guest OS of Azure virtual machines (VMs) isn't collected automatically like other [platform metrics](./monitor-azure-resource.md#monitoring-data). Install the Azure Monitor [Diagnostics extension](../agents/diagnostics-extension-overview.md) to collect guest OS metrics into the metrics database so that it can be used with all features of Azure Monitor Metrics. These features include near real time alerting, charting, routing, and access from a REST API. This article describes the process for sending guest OS performance metrics for a Windows VM to the metrics database by using an Azure Resource Manager template (ARM template).
 
 > [!NOTE]
 > For details on configuring the diagnostics extension to collect guest OS metrics by using the Azure portal, see [Install and configure the Windows Azure Diagnostics (WAD) extension](../agents/diagnostics-extension-windows-install.md).
@@ -219,7 +219,7 @@ Download and save both files locally.
 ## Deploy the ARM template
 
 > [!NOTE]
-> You must be running the Azure Diagnostics extension version 1.5 or higher *and* have the `autoUpgradeMinorVersion:` property set to `true` in your ARM template. Azure then loads the proper extension when it starts the VM. If you don't have these settings in your template, change them and redeploy the template.
+> You must be running Azure Diagnostics extension version 1.5 or higher *and* have the `autoUpgradeMinorVersion:` property set to `true` in your ARM template. Azure then loads the proper extension when it starts the VM. If you don't have these settings in your template, change them and redeploy the template.
 
 To deploy the ARM template, we use Azure PowerShell.
 

articles/azure-monitor/essentials/data-collection-rule-structure.md

@@ -59,4 +59,4 @@ The definition indicates which streams should be sent to which destinations.
 
 ## Next steps
 
-[Overview of data collection rules including methods for creating them](data-collection-rule-overview.md)
+[Overview of data collection rules and methods for creating them](data-collection-rule-overview.md)

articles/azure-monitor/essentials/data-collection-transformations.md

@@ -8,14 +8,14 @@ ms.reviwer: nikeist
 ---
 
 # Data collection transformations in Azure Monitor
-With transformations in Azure Monitor, you can filter or modify incoming data before it's sent to a Log Analytics workspace. This article provides a basic description of transformations and how they're implemented. It provides links to other content for actually creating a transformation.
+With transformations in Azure Monitor, you can filter or modify incoming data before it's sent to a Log Analytics workspace. This article provides a basic description of transformations and how they're implemented. It provides links to other content for creating a transformation.
 
 ## Why to use transformations
 The following table describes the different goals that you can achieve by using transformations.
 
 | Category | Details |
 |:---|:---|
-| Remove sensitive data | You might have a data source that sends information you don't want stored for privacy or compliancy reasons.<br><br>**Filter sensitive information.** Filter out entire rows or particular columns that contain sensitive information.<br><br>**Obfuscate sensitive information.** Replace information such as digits in an IP address or telephone number with a common character.<br><br>**Send to alternate table.** Send sensitive records to an alternate table with different role-based access control configuration. |
+| Remove sensitive data | You might have a data source that sends information you don't want stored for privacy or compliancy reasons.<br><br>**Filter sensitive information.** Filter out entire rows or particular columns that contain sensitive information.<br><br>**Obfuscate sensitive information.** Replace information such as digits in an IP address or telephone number with a common character.<br><br>**Send to an alternate table.** Send sensitive records to an alternate table with different role-based access control configuration. |
 | Enrich data with more or calculated information | Use a transformation to add information to data that provides business context or simplifies querying the data later.<br><br>**Add a column with more information.** For example, you might add a column identifying whether an IP address in another column is internal or external.<br><br>**Add business-specific information.** For example, you might add a column indicating a company division based on location information in other columns. |
 | Reduce data costs | Because you're charged ingestion cost for any data sent to a Log Analytics workspace, you want to filter out any data that you don't require to reduce your costs.<br><br>**Remove entire rows.** For example, you might have a diagnostic setting to collect resource logs from a particular resource but not require all the log entries that it generates. Create a transformation that filters out records that match a certain criteria.<br><br>**Remove a column from each row.** For example, your data might include columns with data that's redundant or has minimal value. Create a transformation that filters out columns that aren't required.<br><br>**Parse important data from a column.** You might have a table with valuable data buried in a particular column. Use a transformation to parse the valuable data into a new column and remove the original.<br><br>**Send certain rows to basic logs.** Send rows in your data that require basic query capabilities to basic logs tables for a lower ingestion cost. |
 

articles/azure-monitor/essentials/metrics-store-custom-rest-api.md

@@ -1,6 +1,6 @@
 ---
 title: Send metrics to the Azure Monitor metric database by using a REST API
-description: Send custom metrics for an Azure resource to the Azure Monitor metric store by using a REST API.
+description: Send custom metrics for an Azure resource to the Azure Monitor metrics store by using a REST API.
 author: EdB-MSFT
 services: azure-monitor
 ms.reviewer: priyamishra
@@ -72,7 +72,7 @@ Save the access token from the response for use in the following HTTP requests.
 
 ## Send a metric via the REST API
 
-1. Paste the following JSON into a file. Save it as *custommetric.json* on your local computer. Update the time parameter so that it's within the last 20 minutes. You can't put a metric into the store that's more than 20 minutes old. The metric store is optimized for alerting and real-time charting.
+1. Paste the following JSON into a file. Save it as *custommetric.json* on your local computer. Update the time parameter so that it's within the last 20 minutes. You can't put a metric into the store that's more than 20 minutes old. The metrics store is optimized for alerting and real-time charting.
 
     ```JSON
     { 

articles/azure-monitor/essentials/tutorial-resource-logs.md

@@ -33,7 +33,7 @@ You can use any resource in your Azure subscription that supports diagnostic set
 ## Create a diagnostic setting
 [Diagnostic settings](../essentials/diagnostic-settings.md) define where to send resource logs for a particular resource. A single diagnostic setting can have multiple [destinations](../essentials/diagnostic-settings.md#destinations), but we only use a Log Analytics workspace in this tutorial.
 
-Under the **Monitoring** section of your resource's menu, select **Diagnostic settings** > **Add diagnostic setting**.
+Under the **Monitoring** section of your resource's menu, select **Diagnostic settings**. Then select **Add diagnostic setting**.
 
 > [!NOTE]
 > Some resources might require other selections. For example, a storage account requires you to select a resource before the **Add diagnostic setting** option is displayed. You might also notice a **Preview** label for some resources because their diagnostic settings are currently in preview.