acrolinx

Author: bwren

articles/azure-monitor/logs/custom-logs-migrate.md

@@ -10,14 +10,14 @@ ms.date: 01/06/2022
 This article describes how to migrate from [Data Collector API](data-collector-api.md) or [custom fields](custom-fields.md) in Azure Monitor to [DCR-based custom logs](custom-logs-overview.md). It includes configuration required for tables in your Log Analytics workspace and applies to both [direct ingestion](custom-logs-overview.md) and [ingestion-time transformations](ingestion-time-transformations.md).
 
 > [!IMPORTANT]
-> You do not need to follow this article if you are defining your DCR-based custom logs using the Azure Portal. This article only applies if you are using resource manager templates and the custom logs API.
+> You do not need to follow this article if you are defining your DCR-based custom logs using the Azure Portal. This article only applies if you are using Resource Manager templates and the custom logs API.
 
 ## Background
 To use a table with the [direct ingestion](custom-logs-overview.md), and [ingestion-time transformations](ingestion-time-transformations.md), it must be configured to support these new features. When you complete the process described in this article, the following actions are taken:
 
 - The table will be reconfigured to enable all DCR-based custom logs features. This includes DCR and DCE support and management with the new Tables control plane.
 - Any previously defined custom fields will stop populating.
-- The Data Collector API will continue to work but will not create any new columns. Data will only populate into any columns that was created prior to migration.
+- The Data Collector API will continue to work but won't create any new columns. Data will only populate into any columns that was created prior to migration.
 - The schema and historic data is preserved and can be accessed the same way it was previously.
 
 ## Applicable scenarios
@@ -27,12 +27,12 @@ This article is only applicable if all of the following criteria apply:
 - The table in question was either created using the Data Collector API, or has custom fields defined in it  
 - You want to migrate using the custom logs API instead of the Azure portal.
 
-If all of these conditions are not true, then you can use DCR-based custom logs without following the procedure described here.
+If all of these conditions aren't true, then you can use DCR-based custom logs without following the procedure described here.
 
 ## Migration procedure
 If the table that you're targeting with DCR-based custom logs does indeed falls under the criteria described above, the following strategy is required for a graceful migration:
 
-1. Configure your data collection rule (DCR) following procedures at [Send custom logs to Azure Monitor Logs using resource manager templates (preview)](tutorial-custom-logs-api.md) or [Add ingestion-time transformation to Azure Monitor Logs using resource manager templates (preview)](tutorial-ingestion-time-transformations-api.md).
+1. Configure your data collection rule (DCR) following procedures at [Send custom logs to Azure Monitor Logs using Resource Manager templates (preview)](tutorial-custom-logs-api.md) or [Add ingestion-time transformation to Azure Monitor Logs using Resource Manager templates (preview)](tutorial-ingestion-time-transformations-api.md).
 
 1. If using the DCR-based API, also [configure the data collection endpoint (DCE)](tutorial-custom-logs-api.md#create-data-collection-endpoint) and the agent or component that will be sending data to the API.