review cleanup

Author: shayoniseth

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

@@ -14,7 +14,7 @@ ms.date: 03/16/2021
 Virtual machines and other compute resources require an agent to collect monitoring data required to measure the performance and availability of their guest operating system and workloads. This article describes the agents used by Azure Monitor and helps you determine which you need to meet the requirements for your particular environment.
 
 > [!NOTE]
-> Azure Monitor recently launched a new agent, the [Azure Monitor agent](./azure-monitor-agent-overview.md), that provides all capabilities necessary to collect guest operating system monitoring data. **Use this new agent if you don't require the current limitations**, as it consolidates the features of all the legacy agents listed below and provides additional benefits. If you do require the limitations today, you may continue using the other legacy agents listed below until **August 2024**. [Learn more](./azure-monitor-agent-overview.md)
+> Azure Monitor recently launched a new agent, the [Azure Monitor agent](./azure-monitor-agent-overview.md), that provides all capabilities necessary to collect guest operating system monitoring data. **Use this new agent if you don't require [these current limitations](./azure-monitor-agent-overview.md#current-limitations)**, as it consolidates the features of all the legacy agents listed below and provides additional benefits. If you do require the limitations today, you may continue using the other legacy agents listed below until **August 2024**. [Learn more](./azure-monitor-agent-overview.md)
 
 ## Summary of agents
 

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

@@ -143,12 +143,7 @@ The Azure Monitor agent extensions for Windows and Linux can communicate either
 
     ![Flowchart to determine the values of settings and protectedSettings parameters when you enable the extension.](media/azure-monitor-agent-overview/proxy-flowchart.png)
 
-2. After the values for the *settings* and *protectedSettings* parameters are determined, provide these additional parameters when you deploy the Azure Monitor agent by using PowerShell commands. The following examples are for Azure virtual machines.
-
-    | Parameter | Value |
-    |:---|:---|
-    | settingsString | A JSON string value from the preceding flowchart. Skip if not applicable. |
-    | protectedSettingsHashtable | A JSON string value from the preceding flowchart. Skip if not applicable. |
+2. After the values for the *settings* and *protectedSettings* parameters are determined, **provide these additional parameters** when you deploy the Azure Monitor agent by using PowerShell commands. Refer the following examples.
 
 # [Windows VM](#tab/PowerShellWindows)
 

articles/azure-monitor/essentials/data-collection-endpoint-overview.md

@@ -13,7 +13,7 @@ Data Collection Endpoints (DCEs) allow you to uniquely configure ingestion setti
 ## Workflows that use DCEs
 The following workflows currently use DCEs:
 
-- [Azure Monitor agent](../agents/data-collection-rule-azure-monitor-agent.md))
+- [Azure Monitor agent](../agents/data-collection-rule-azure-monitor-agent.md)
 - [Custom logs](../logs/custom-logs-overview.md)
 
 ## Components of a data collection endpoint