fixes

Author: bwren

articles/azure-monitor/faq.md

@@ -192,7 +192,7 @@ See [Network firewall requirements](platform/log-analytics-agent.md#network-fire
 
 ## Visualizations
 
-### Why can't I can't see View Designer?
+### Why can't I see View Designer?
 
 View Designer is only available for users assigned with Contributor permissions or higher in the Log Analytics workspace.
 

articles/azure-monitor/insights/vminsights-log-search.md

@@ -204,7 +204,7 @@ Records with a type of *VMComputer* have inventory data for servers with the Dep
 |AzureCloudServiceRoleType | Cloud Service role type: *worker* or *web* |
 |AzureCloudServiceInstanceId | Cloud Service role instance ID |
 |AzureVmScaleSetName | The name of the virtual machine scale set |
-|AzureVmScaleSetDeployment | VM scale set deployment ID |
+|AzureVmScaleSetDeployment | Virtual machine scale set deployment ID |
 |AzureVmScaleSetResourceId | The unique identifier of the virtual machine scale set resource.|
 |AzureVmScaleSetInstanceId | The unique identifier of the virtual machine scale set |
 |AzureServiceFabricClusterId | The unique identifer of the Azure Service Fabric cluster | 

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

@@ -19,7 +19,7 @@ Azure Monitor for VMs relies on the following components to deliver its experien
 
 * A Log Analytics workspace, which stores monitoring data from VMs and other sources.
 * A collection of performance counters configured in the workspace. The collection updates the monitoring configuration on all VMs connected to the workspace.
-* `VMInsights` which is a monitoring solution configured in the workspace. This solution updates the monitoring configuration on all VMs connected to the workspace.
+* `VMInsights`, which is a monitoring solution configured in the workspace. This solution updates the monitoring configuration on all VMs connected to the workspace.
 * `MicrosoftMonitoringAgent` and `DependencyAgent`, which are Azure VM extensions. These extensions collect and send data to the workspace.
 
 As you prepare to disable monitoring of your VMs, keep these considerations in mind:

articles/azure-monitor/insights/vminsights-performance.md

@@ -118,7 +118,7 @@ Clicking on the pin icon at the upper right-hand corner of any one of the charts
 
 Performance metrics enabled as part of Azure Monitor for VMs do not include pre-configured alert rules. However, we may only collect and store a subset of the performance metrics you require in the Log Analytics workspace. If your monitoring strategy requires analysis or alerting that includes other performance metrics in order to effectively evaluate capacity or health of the virtual machine, or you need the flexibility to specify your own alerting criteria or logic, you can configure [collection of those performance counters](../platform/data-sources-performance-counters.md) in Log Analytics and define [log alerts](../platform/alerts-log.md). While Log Analytics allows you to perform complex analysis with other data types, and provide longer retention to support trend analysis, metrics on the other hand, are lightweight and capable of supporting near real-time scenarios. They are collected by the [Azure Diagnostic agent](../../virtual-machines/windows/monitor.md) and stored in the Azure Monitor metrics store, allowing you to create alerts with lower latency and at a lower cost.
 
-Review the overview of [collection of metrics and logs with Azure Monitor](../platform/data-platform.md) to further understand the fundamental differences and other clonsiderations before configuring collection of these additional metrics and alert rules.  
+Review the overview of [collection of metrics and logs with Azure Monitor](../platform/data-platform.md) to further understand the fundamental differences and other considerations before configuring collection of these additional metrics and alert rules.  
 
 ## Next steps