Merge pull request #42625 from ohadschn/patch-4

Typos

Author: ktoliver

articles/azure-monitor/platform/autoscale-common-metrics.md

@@ -30,7 +30,7 @@ The following host-level metrics are emitted by default for Azure VM and VMSS in
 - [Host metrics for Resource Manager-based Windows and Linux VMs](../../azure-monitor/platform/metrics-supported.md#microsoftcomputevirtualmachines)
 - [Host metrics for Resource Manager-based Windows and Linux VM Scale Sets](../../azure-monitor/platform/metrics-supported.md#microsoftcomputevirtualmachinescalesets)
 
-### Guest OS metrics Resource Manager-based Windows VMs
+### Guest OS metrics for Resource Manager-based Windows VMs
 When you create a VM in Azure, diagnostics is enabled by using the Diagnostics extension. The diagnostics extension emits a set of metrics taken from inside of the VM. This means you can autoscale off of metrics that are not emitted by default.
 
 You can generate a list of the metrics by using the following command in PowerShell.
@@ -123,8 +123,8 @@ Get-AzMetricDefinition -ResourceId <resource_id> | Format-Table -Property Name,U
 | \NetworkInterface\TotalTxErrors |Count |
 | \NetworkInterface\TotalCollisions |Count |
 
-## Commonly used Web (Server Farm) metrics
-You can also perform autoscale based on common web server metrics such as the Http queue length. It's metric name is **HttpQueueLength**.  The following section lists available server farm (Web Apps) metrics.
+## Commonly used App Service (Server Farm) metrics
+You can also perform autoscale based on common web server metrics such as the Http queue length. Its metric name is **HttpQueueLength**.  The following section lists available server farm (App Service) metrics.
 
 ### Web Apps metrics
 You can generate a list of the Web Apps metrics by using the following command in PowerShell.
@@ -153,8 +153,8 @@ For example, with a Classic Storage Account the autoscale setting metricTrigger
 
 ```
 "metricName": "ApproximateMessageCount",
- "metricNamespace": "",
- "metricResourceUri": "/subscriptions/SUBSCRIPTION_ID/resourceGroups/RES_GROUP_NAME/providers/Microsoft.ClassicStorage/storageAccounts/STORAGE_ACCOUNT_NAME/services/queue/queues/QUEUE_NAME"
+"metricNamespace": "",
+"metricResourceUri": "/subscriptions/SUBSCRIPTION_ID/resourceGroups/RES_GROUP_NAME/providers/Microsoft.ClassicStorage/storageAccounts/STORAGE_ACCOUNT_NAME/services/queue/queues/QUEUE_NAME"
  ```
 
 For a (non-classic) storage account, the metricTrigger would include:
@@ -171,7 +171,7 @@ You can scale by Service Bus queue length, which is the number of messages in th
 For VM scale sets, you can update the Autoscale setting in the Resource Manager template to use *metricName* as *ApproximateMessageCount* and pass the ID of the storage queue as *metricResourceUri*.
 
 ```
-"metricName": "MessageCount",
+"metricName": "ApproximateMessageCount",
  "metricNamespace": "",
 "metricResourceUri": "/subscriptions/SUBSCRIPTION_ID/resourceGroups/RES_GROUP_NAME/providers/Microsoft.ServiceBus/namespaces/SB_NAMESPACE/queues/QUEUE_NAME"
 ```