formatting update

Author: amsliu

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/understanding-and-mitigating-high-data-consumption.md

@@ -13,40 +13,40 @@ ms.custom: Configure and Manage Log analytics tables
 
 This article addresses the issue of high data consumption in Log Analytics workspaces, specifically focusing on tables like `AzureDiagnostics`. It provides insights into understanding the costs associated with data usage and offers steps to optimize and reduce these costs.
 
-## Step-by-Step Instructions to Resolve High Data Usage
+## Common Issues and Solutions
 
-### 1. Identify High Data Tables
+- **Data Retention**: Ensure that data retention settings are configured appropriately to avoid unnecessary storage costs.
+- **Data Filtering**: Implement data filtering to only collect necessary data, reducing the volume of data ingested.
 
-- Use the `AzureDiagnostics` table to determine which Reference are sending large amounts of data.
-- Run the following query in your Log Analytics workspace:
+### Step-by-Step Instructions to Resolve High Data Usage
 
-    ```plaintext
-    AzureDiagnostics | distinct _ResourceId
-    ```
+1. **Identify High Data Tables:**
 
-- This will help you identify the Reference contributing to high data usage.
+    - Use the `AzureDiagnostics` table to determine which Reference are sending large amounts of data.
+    - Run the following query in your Log Analytics workspace:
 
-### 2. Review Diagnostic Settings
+        ```plaintext
+        AzureDiagnostics | distinct _ResourceId
+        ```
 
-- Navigate to the diagnostic settings of the identified Reference.
-- Remove unnecessary diagnostic settings if the data is not needed. This will stop the data from being sent to the AzureDiagnostics table.
+    - This will help you identify the Reference contributing to high data usage.
 
-### 3. Understand Cost Implications
+2. **Review Diagnostic Settings:**
 
-Review the following Reference to understand the costs associated with your Log Analytics workspace:
+    - Navigate to the diagnostic settings of the identified Reference.
+    - Remove unnecessary diagnostic settings if the data is not needed. This will stop the data from being sent to the AzureDiagnostics table.
 
-- [Understand Log Analytics Workspace Billing](https://learn.microsoft.com/azure/azure-monitor/log-analytics/billing/understand-log-analytics-workspace-bill)
-- [Best Practices for Cost Management](https://learn.microsoft.com/azure/azure-monitor/fundamentals/best-practices-cost)
-- [Cost Management for Logs](https://learn.microsoft.com/azure/azure-monitor/logs/cost-logs)
+3. **Understand Cost Implications:**
 
-### 4. Implement Cost Optimization Strategies
+    Review the following Reference to understand the costs associated with your Log Analytics workspace:
 
-- Follow the best practices outlined in the Reference to optimize data usage and reduce costs.
+    - [Understand Log Analytics Workspace Billing](https://learn.microsoft.com/azure/azure-monitor/log-analytics/billing/understand-log-analytics-workspace-bill)
+    - [Best Practices for Cost Management](https://learn.microsoft.com/azure/azure-monitor/fundamentals/best-practices-cost)
+    - [Cost Management for Logs](https://learn.microsoft.com/azure/azure-monitor/logs/cost-logs)
 
-## Common Issues and Solutions
+4. **Implement Cost Optimization Strategies**:
 
-- **Data Retention**: Ensure that data retention settings are configured appropriately to avoid unnecessary storage costs.
-- **Data Filtering**: Implement data filtering to only collect necessary data, reducing the volume of data ingested.
+    - Follow the best practices outlined in the Reference to optimize data usage and reduce costs.
 
 ## Reference