Update troubleshoot-custom-log-table-creation.md

Edit review per CI 6620

Author: przlplx

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md

@@ -7,40 +7,33 @@ ms.service: azure-monitor
 ms.custom: Configure and Manage Log analytics tables
 ---
 
-# Troubleshoot Custom Log Table Creation in Azure
+# Troubleshoot custom log table creation in Azure
 
-When attempting to create a custom log table using a JSON file in Azure, users may encounter an error stating "Cannot read properties of undefined (reading length)". This issue typically arises during the final step of table creation, despite the JSON being valid. Understanding the root cause and following the correct steps can help resolve this problem.
+Users might receive an error message that states "Cannot read properties of undefined (reading length)" when they try to create a custom log table by using a JSON file in Microsoft Azure. This issue typically occurs during the final step of table creation even though the JSON file is valid. If you understand the root cause of the issue and follow the correct steps, you can resolve this issue efficiently.
 
-## Common Issues and Solutions
+## Common issues and solutions
 
-- **Error: Cannot read properties of undefined (reading length)**
-  - This error often indicates a problem with the JSON structure or the DCR configuration. Double-check both for accuracy.
+- Error: Cannot read properties of undefined (reading length): This error often indicates an issue that affects the JSON structure or the DCR configuration. Doublecheck both for accuracy.
 
-- **No Data Ingestion**
-  - Verify that the data source is correctly set up to collect log files. The data source type should be **Custom (Log files)**, and the stream declaration should follow the format `Custom-<TableName>`.
+- No Data Ingestion: Verify that the data source is correctly set up to collect log files. The data source type should be **Custom (Log files)**, and the stream declaration should follow the format `Custom-<TableName>`.
 
-### Step-by-Step Instructions to Resolve the Issue
+### Instructions to resolve the issue
 
-1. **Verify JSON Validity**
-   - Ensure that the JSON file being used is correctly formatted and valid. Use a JSON validator tool to confirm this.
+1. Make sure that the JSON file that's used is correctly formatted and valid. Use a JSON validator tool to verify this.
 
-2. **Create a New Data Collection Rule (DCR)**
-   - Navigate to the Azure portal and access the **Log Analytics Workspace**.
-   - Create a new DCR specifically for the custom log table. Avoid using an existing DCR that collects other types of data, as this can lead to configuration conflicts.
+2. Create a new data collection rule (DCR):
+   1. Navigate to the Azure portal > **Log Analytics Workspace**.
+   1. Create a DCR specifically for the custom log table. Avoid using an existing DCR that collects other types of data because this action can cause configuration conflicts.
 
-3. **Use PowerShell Script for Table Creation**
-   - Follow the steps outlined in the [Azure documentation](https://learn.microsoft.com/azure/azure-monitor/vm/data-collection-log-json#create-custom-table) to create the custom table using a PowerShell script.
-   - This method allows you to specify the file pattern and verify the DCR configuration after creation.
+3. Follow the steps that are outlined in the [Azure documentation](https://learn.microsoft.com/azure/azure-monitor/vm/data-collection-log-json#create-custom-table) to create the custom table by using a PowerShell script. This method allows you to specify the file pattern and verify the DCR configuration after the creation is finished.
 
-4. **Check Contributor Role**
-   - Ensure that you have at least the Contributor role in the relevant Azure Workspace to perform these actions.
+4. To be able to perform these actions, make sure that you have at least the Contributor role in the relevant Azure Workspace.
 
-5. **Refresh the Portal**
-   - If issues persist, try refreshing the Azure portal to ensure all settings are updated.
+5. If the issue persists, try to refresh the Azure portal to make sure that all settings are updated.
 
 ## Reference
 
 - [Create Custom Table in Azure](https://learn.microsoft.com/azure/azure-monitor/vm/data-collection-log-json#create-custom-table)
 - [Data Collection Rule Best Practices](https://learn.microsoft.com/azure/azure-monitor/data-collection/data-collection-rule-best-practices)
 
-If the issue persists after following the solution steps, please open a support case for further assistance.
+If the issue persists after you follow these steps, please open a support case for further assistance.