Merge pull request #264185 from guywi-ms/ama-migration-update

Update azure-monitor-agent-migration.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -19,7 +19,7 @@ ms.custom:
 
 ## Benefits
 
-In addition to consolidating and improving on the legacy Log Analytics agents, Azure Monitor Agent provides [a variety of immediate benefits](./azure-monitor-agent-overview.md#benefits), including **cost savings, a simplified management experience, and enhanced security and performance.**
+In addition to consolidating and improving on the legacy Log Analytics agents, Azure Monitor Agent provides [various immediate benefits](./azure-monitor-agent-overview.md#benefits), including **cost savings, a simplified management experience, and enhanced security and performance.**
 
 ## Migration guidance
 
@@ -46,7 +46,7 @@ Before you begin migrating from the Log Analytics agent to Azure Monitor Agent,
 
 1. Use the [DCR generator](./azure-monitor-agent-migration-tools.md#installing-and-using-dcr-config-generator) to convert your legacy agent configuration into [data collection rules](./data-collection-rule-azure-monitor-agent.md#create-a-data-collection-rule) automatically.<sup>1</sup> 
 
-    Review the generated rules before you create them, to leverage benefits like [filtering](../essentials/data-collection-transformations.md), granular targeting (per machine), and other optimizations. There are special steps needed to[ migrate MMA custom logs to AMA custom logs](./azure-monitor-agent-custom-text-log-migration.md)
+    Review the generated rules before you create them and take advantage of advanced options, such as [filtering](../essentials/data-collection-transformations.md), granular targeting (per machine), and other optimizations. There are special steps needed to [migrate MMA custom logs to AMA custom logs](./azure-monitor-agent-custom-text-log-migration.md)
 
 1. Test the new agent and data collection rules on a few nonproduction machines: 
 
@@ -82,10 +82,10 @@ Before you begin migrating from the Log Analytics agent to Azure Monitor Agent,
 
     - If you've migrated to Azure Monitor Agent for all your requirements, [uninstall the Log Analytics agent](./agent-manage.md#uninstall-agent) from monitored resources. Clean up any configuration files, workspace keys, or certificates that were used previously by the Log Analytics agent. Continue using the legacy Log Analytics for features and solutions that Azure Monitor Agent doesn't support.
     
-        Use the [MMA removal tool](../agents/azure-monitor-agent-mma-removal-tool.md) to discovery and remove the Log Analytics agent extension from all machines within your tenant.     
+       Use the [MMA removal tool](../agents/azure-monitor-agent-mma-removal-tool.md) to discovery and remove the Log Analytics agent extension from all machines within your tenant.     
     - Don't uninstall the legacy agent if you need to use it to upload data to System Center Operations Manager.
 
-<sup>1</sup> The DCR generator only converts the configurations for Windows event logs, Linux syslog and performance counters. Support for more features and solutions will be available soon  
+<sup>1</sup> The DCR generator only converts the configurations for Windows event logs, Linux syslog and performance counters. Support for more features and solutions will be available soon.  
 <sup>2</sup> You might need to deploy [extensions required for specific solutions](#migrate-additional-services-and-features) in addition to the Azure Monitor Agent extension.  
 
 ## Migrate additional services and features
@@ -104,7 +104,7 @@ The following features and services now have an Azure Monitor Agent version (som
 |	Azure Stack HCI Insights	|	Migrate to Azure Monitor Agent 	| Generally Available|	[Monitor Azure Stack HCI with Insights](/azure-stack/hci/manage/monitor-hci-single)	|
 |	[Azure Virtual Desktop (AVD) Insights](../../virtual-desktop/insights.md) |	Migrate to Azure Monitor Agent	|Generally Available	| [Use Azure Virtual Desktop Insights to monitor your deployment](../../virtual-desktop/insights.md#session-host-data-settings)	|
 | [Container Monitoring Solution](../containers/containers.md) | Migrate to new service called Container Insights with Azure Monitor Agent | Generally Available | [Enable Container Insights](../containers/container-insights-transition-solution.md) |
-| [DNS Collector](../../sentinel/connect-dns-ama.md) | Use new Sentenil Connector | Generally Available | [Enable DNS Connnector](../../sentinel/connect-dns-ama.md)|
+| [DNS Collector](../../sentinel/connect-dns-ama.md) | Use new Sentinel Connector | Generally Available | [Enable DNS Connector](../../sentinel/connect-dns-ama.md)|
 
 > [!NOTE]
 > Features and services listed above in preview **may not be available in Azure Government and China clouds**. They will be available typically within a month *after* the features/services become generally available.