change headers

Author: bwren

articles/azure-monitor/essentials/data-collection-rule-create-edit.md

@@ -75,8 +75,6 @@ az rest --method put --url $ResourceId"?api-version=2022-06-01" --body @$FilePat
 
 ### [ARM](#tab/arm)
 
-### DCR
-
 See the follow references for defining DCRs and associations in a template.
 - [Data collection rules](/azure/templates/microsoft.insights/datacollectionrules)
 - [Data collection rule associations](/azure/templates/microsoft.insights/datacollectionruleassociations)
@@ -116,9 +114,10 @@ Use the following template to create a DCR using information from [Structure of
 
 ```
 
-### DCR Association -Azure VM
+#### DCR Association -Azure VM
+The following sample creates an association between an Azure virtual machine and a data collection rule.
 
-#### Bicep
+**Bicep template file**
 
 ```bicep
 @description('The name of the virtual machine.')
@@ -144,7 +143,7 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
 }
 ```
 
-#### ARM
+**ARM template file**
 
 ```json
 {
@@ -185,7 +184,7 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
 }
 ```
 
-#### Parameter file
+**Parameter file**
 
 ```json
 {
@@ -205,8 +204,9 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
 }
 ```
 ### DCR Association -Arc-enabled server
+The following sample creates an association between an Azure Arc-enabled server and a data collection rule.
 
-#### Bicep
+**Bicep template file**
 
 ```bicep
 @description('The name of the virtual machine.')
@@ -232,7 +232,7 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
 }
 ```
 
-#### ARM
+**ARM template file**
 
 ```json
 {
@@ -273,7 +273,7 @@ resource association 'Microsoft.Insights/dataCollectionRuleAssociations@2021-09-
 }
 ```
 
-#### Parameter file
+**Parameter file**
 
 ```json
 {

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

@@ -9,7 +9,7 @@ ms.date: 03/31/2023
 
 # Tutorial: Replace custom fields in Log Analytics workspace with KQL-based custom columns
 
-Custom fields is a feature of Azure Monitor that allows you to extract into a separate column data from a different text column of the same table. Creation of new custom fields will be disabled starting March 31st, 2023. Custom fields functionality will be deprecated and existing custom fields will stop functioning on March 31st, 2026.
+Custom fields is a feature of Azure Monitor that allows you to extract into a separate column data from a different text column of the same table. Creation of new custom fields will be disabled starting March 31, 2023. Custom fields functionality will be deprecated and existing custom fields will stop functioning on March 31, 2026.
 
 There are several advantages to using DCR-based [ingestion-time transformations](../essentials/data-collection-transformations.md) to accomplish the same result:
 
@@ -64,8 +64,8 @@ Since there is no way to examine the custom field definition directly, you need
 
 1. Locate the columns noted in the previous step and examine their content.
     - If the column *is not empty* and *there are DCRs* associated with the table, then custom field logic has been already implemented with transformation. No action is required
-    - If the column *is empty* (or not present in query results) and *there are DCRs* associated with the table, the custom field logic was not implemented with the DCR. Add a transformation to the dataflow in the existing DCR.
-    - If the column *is not empty* and *there are no DCRs* associated with the table, the custom field logic needs to implemented as a transformation in the [workspace DCR](../essentials/data-collection-transformations-workspace.md).
+    - If the column *is empty* (or not present in query results) and *there are DCRs* associated with the table, the custom field logic wasn't implemented with the DCR. Add a transformation to the dataflow in the existing DCR.
+    - If the column *isn't empty* and *there are no DCRs* associated with the table, the custom field logic needs to implemented as a transformation in the [workspace DCR](../essentials/data-collection-transformations-workspace.md).
 
 1. Examine the content of the custom field and determine the logic how it's being calculated. Custom fields usually calculate substrings of other columns in the same table. Determine which column the data comes from and the portion of the string it extracts.
 
@@ -76,7 +76,7 @@ You're now ready to create the required KQL snippet and add it to a DCR. This lo
 
     - Use [parse](/azure/data-explorer/kusto/query/parseoperator) operator for pattern-based search of a substring within a string.
     - Use [extract()](/azure/data-explorer/kusto/query/extractfunction) function for regex-based substring search.
-    - String functions as [split()](/azure/data-explorer/kusto/query/splitfunction), [substring()](/azure/data-explorer/kusto/query/substringfunction) and [many others](/azure/data-explorer/kusto/query/scalarfunctions#string-functions) may also be useful.
+    - String functions as [split()](/azure/data-explorer/kusto/query/splitfunction), [substring()](/azure/data-explorer/kusto/query/substringfunction), and [many others](/azure/data-explorer/kusto/query/scalarfunctions#string-functions) may also be useful.
 
     :::image type="content" source="media/custom-fields-migrate/log-analytics-transformation-query.png" alt-text="Screenshot of Log Analytics with query returning data using transformation query" lightbox="media/custom-fields-migrate/log-analytics-transformation-query.png":::
 
@@ -91,15 +91,15 @@ You're now ready to create the required KQL snippet and add it to a DCR. This lo
 
 ### How do I migrate  custom fields for a text log collected with legacy Log Analytics agent (MMA)?
 
-Consider migrating to Azure Monitor Agent (AMA). Log Analytics agent is approaching its end of support, and you should migrate to Azure Monitor Agent (AMA). [Text logs collected with AMA](../agents/data-collection-text-log.md) use log parsing logic defined in form of KQL transformations from the start. Custom fields are not required and not supported in text logs collected by Azure Monitor Agent.
+Consider migrating to Azure Monitor Agent (AMA). Log Analytics agent is approaching its end of support, and you should migrate to Azure Monitor Agent (AMA). [Text logs collected with AMA](../agents/data-collection-text-log.md) use log parsing logic defined in form of KQL transformations from the start. Custom fields aren't required and not supported in text logs collected by Azure Monitor Agent.
 
 ### Is migration of custom fields to KQL mandatory?
 
-No. You need to migrate your custom fields only if you still want your custom columns populated. If you don't migrate your custom fields, corresponding columns will stop being populated when support of custom fields is ended. Data that has been already processed and stored in the table will not be affected and will remain usable.
+No, you need to migrate your custom fields only if you still want your custom columns populated. If you don't migrate your custom fields, corresponding columns will stop being populated when support of custom fields is ended. Data that has been already processed and stored in the table won't be affected and will remain usable.
 
 ### Will I lose my existing data in corresponding columns if I don't migrate my custom fields in time?
 
-No. Custom fields are calculated at the time of data ingestion. Deleting the field definition or not migrating them in time will not affect any data previously ingested.
+No, custom fields are calculated at the time of data ingestion. Deleting the field definition or not migrating them in time won't affect any data previously ingested.
 
 ## Next steps