fixes

Author: bwren

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

@@ -27,7 +27,7 @@ Migration is a complex task. Start planning your migration to Azure Monitor Agen
 ## Benefits
 Using Azure Monitor agent, you get immediate benefits as shown below:
 
-:::image type="content" source="media/azure-monitor-agent-overview/azure-monitor-agent-benefits.png" lightbox="media/azure-monitor-agent-overview/azure-monitor-agent-benefits.png" alt-text="Snippet of the Azure Monitor Agent benefits at a glance. This is described in more details below.":::
+:::image type="content" source="media/azure-monitor-agent-overview/azure-monitor-agent-benefits.png" lightbox="media/azure-monitor-agent-overview/azure-monitor-agent-benefits.png" alt-text="Diagram of the Azure Monitor Agent benefits at a glance. This is described in more details below.":::
 
 - **Cost savings** by [using data collection rules](./azure-monitor-agent-data-collection.md):
   - Enables targeted and granular data collection for a machine or subset(s) of machines, as compared to the "all or nothing" approach of legacy agents.
@@ -65,7 +65,7 @@ The **Azure Monitor Agent Migration Helper** workbook is a workbook-based Azure
 
 ## Understand your agents
 
-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](../essentials/data-collection-rule-overview.md) automatically.<sup>1</sup> 
+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](../essentials/data-collection-rule-overview.md) automatically.<sup>1</sup> 
 To help understand your agents, review the following questions:
 
 |**Question**|**Actions**|

articles/azure-monitor/agents/azure-monitor-agent-network-configuration.md

@@ -3,7 +3,7 @@ title: Azure Monitor network configuration
 description: Define network settings and enable network isolation for Azure Monitor Agent.
 ms.topic: conceptual
 ms.date: 07/10/2024
-ms.custom: references_region
+ms.custom: references_regions
 ms.reviewer: shseth
 
 ---

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

@@ -37,7 +37,7 @@ A single DCR can contain multiple data sources of different types. Depending on
 
 The DCR is applied to a particular agent by creating a [data collection rule association (DCRA)](../essentials/data-collection-rule-overview.md#data-collection-rule-associations-dcra) between the DCR and the agent. One DCR can be associated with multiple agents, and each agent can be associated with multiple DCRs. When an agent is installed, it connects to Azure Monitor to retrieve any DCRs that are associated with it. The agent periodically checks back with Azure Monitor to determine if there are any changes to existing DCRs or associations with new ones.
 
-:::image type="content" source="media/azure-monitor-agent-data-collection/data-collection-rule-associations.png" alt-text="Diagram showing data collection rule associations connecting each VM to a single DCR." lightbox="media/azure-monitor-agent-data-collection/data-collection-rule-associations.png" border="false":::
+:::image type="content" source="media/azure-monitor-agent-overview/data-collection-rule-associations.png" alt-text="Diagram showing data collection rule associations connecting each VM to a single DCR." lightbox="media/azure-monitor-agent-overview/data-collection-rule-associations.png" border="false":::
 
 ## Costs
 

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

@@ -53,7 +53,7 @@ You should use `mi_res_id` as the `identifier-name`. The following sample comman
 > System-assigned managed identity is the only supported authentication For Azure Arc-enabled servers and is enabled automatically as soon as you install the Azure Arc agent. 
 
 
-## Disk Space
+## Disk space
  Required disk space can vary significantly depending on how an agent is configured or if the agent is unable to communicate with the destinations and must cache data. By default the agent requires 10Gb of disk space to run. The following table provides guidance for capacity planning:
 
 | Purpose | Environment | Path | Suggested Space |

articles/azure-monitor/agents/azure-monitor-agent-send-data-to-event-hubs-and-storage.md

@@ -739,4 +739,4 @@ WAD and LAD will only be getting security/patches going forward. Most engineerin
 
 ## See also
 
-- For more information on creating a data collection rule, see [Collect data from virtual machines wusing Azure Monitor Agent](./azure-monitor-agent-data-collection.md).
+- For more information on creating a data collection rule, see [Collect data from virtual machines using Azure Monitor Agent](./azure-monitor-agent-data-collection.md).

articles/azure-monitor/agents/azure-monitor-agent-supported-operating-systems.md

@@ -93,7 +93,7 @@ This article lists the operating systems supported by [Azure Monitor Agent](./az
 > [!NOTE]
 > CBL-Mariner 2.0's disk size is by default about 1GB to provide storage savings, compared to other Azure VMs that are about 30GB. The Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. See [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
 
-## Hardening Standards
+## Hardening standards
 Azure Monitoring Agent supports most industry-standard hardening standards and is continuously tested and certified against these standards every release. All Azure Monitor Agent scenarios are designed from the ground up with security in mind.
 
 ### Windows hardening

articles/azure-monitor/agents/data-collection-log-text.md

@@ -271,6 +271,6 @@ Go through the following steps if you aren't collecting data from the text log t
 
 Learn more about: 
 
-- [Azure Monitor Agent](azure-monitor-agent-overview.md).
-- [Data collection rules](../essentials/data-collection-rule-overview.md).
-- [Best practices for cost management in Azure Monitor](../best-practices-cost.md).
+- [Azure Monitor Agent](azure-monitor-agent-overview.md)
+- [Data collection rules](../essentials/data-collection-rule-overview.md)
+- [Best practices for cost management in Azure Monitor](../best-practices-cost.md)

articles/azure-monitor/agents/data-collection-performance.md

@@ -1,6 +1,6 @@
 ---
 title: Collect performance counters with Azure Monitor Agent
-description: Describes how to erformance counters from virtual machines, Virtual Machine Scale Sets, and Arc-enabled on-premises servers using Azure Monitor Agent.
+description: Describes how to collect performance counters from virtual machines, Virtual Machine Scale Sets, and Arc-enabled on-premises servers using Azure Monitor Agent.
 ms.topic: conceptual
 ms.date: 07/12/2024
 author: guywild

articles/azure-monitor/agents/data-collection-syslog.md

@@ -26,8 +26,8 @@ Syslog is an event logging protocol that's common to Linux. You can use the Sysl
 In the **Collect and deliver** step of the DCR, select **Linux Syslog** from the **Data source type** dropdown. 
 
 The following facilities are supported with the Syslog collector:
-| Pri index 	| Pri Name 	|
-|---		|---		|
+| Pri index | Pri Name 	|
+|:---|:---|
 | 0	   	| None		|
 | 1		| Kern		|
 | 2		| user		|
@@ -181,7 +181,7 @@ If you edit the Syslog configuration, you must restart the Syslog daemon for the
 
 The following facilities are supported with the Syslog collector:
 | Pri index 	| Pri Name 	|
-|---		|---		|
+|:---|:---|
 | 0	   	| None		|
 | 1		| Kern		|
 | 2		| user		|