fixing validation error

Author: paulth1

articles/azure-monitor/agents/agent-linux-troubleshoot.md

@@ -189,7 +189,7 @@ Below the output plug-in, uncomment the following section by removing the `#` in
 ### Probable causes
 
 * The proxy specified during onboarding was incorrect.
-* The Azure Monitor and Azure Automation Service Endpoints aren't included in the approved list in your datacenter.
+* The Azure Monitor and Azure Automation service endpoints aren't included in the approved list in your datacenter.
 
 ### Resolution
 
@@ -233,7 +233,7 @@ Performance-related bugs don't happen all the time, and they're difficult to rep
 
 1. Callstack will be dumped in the omiagent_trace file. If you notice many curl and NSS function calls, follow these resolution steps.
 
-### Resolution (step by step)
+### Resolution
 
 1. Upgrade the nss-pem package to [v1.0.3-5.el7_6.1](https://centos.pkgs.org/7/centos-x86_64/nss-pem-1.0.3-7.el7.x86_64.rpm.html): <br/>
 `sudo yum upgrade nss-pem`
@@ -455,7 +455,7 @@ sudo sh ./onboard_agent.sh --purge
 
 You can continue to reonboard after you use the `--purge` option.
 
-## Log Analytics agent extension in the Azure portal is marked with a failed state: Provisioning failed
+## Issue: Log Analytics agent extension in the Azure portal is marked with a failed state: Provisioning failed
 
 ### Probable causes
 
@@ -490,7 +490,7 @@ The Log Analytics agent packages on the host are outdated.
 
 ### Probable causes
 
-There's a known issue where, if the VM's language isn't English, a check will fail when verifying which version of Python is being used. This issue leads to the agent always assuming Python2 is being used and failing if there's no Python2.
+For this known issue, if the VM's language isn't English, a check will fail when verifying which version of Python is being used. This issue leads to the agent always assuming Python2 is being used and failing if there's no Python2.
 
 ### Resolution
 

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

@@ -40,7 +40,7 @@ The following prerequisites must be met prior to installing the Azure Monitor ag
    | Any role that includes the action *Microsoft.Resources/deployments/** | <ul><li>Subscription and/or</li><li>Resource group and/or </li></ul> | To deploy Azure Resource Manager templates |  
 - **Non-Azure**: To install the agent on physical servers and virtual machines hosted *outside* of Azure (that is, on-premises) or in other clouds, you must [install the Azure Arc Connected Machine agent](../../azure-arc/servers/agent-overview.md) first, at no added cost.
 - **Authentication**: [Managed identity](../../active-directory/managed-identities-azure-resources/overview.md) must be enabled on Azure virtual machines. Both user-assigned and system-assigned managed identities are supported.
-  - **User-assigned**: This managed identity is recommended for large-scale deployments, configurable via [built-in Azure policies](#using-azure-policy). You can create a user-assigned managed identity once and share it across multiple VMs, which means it's more scalable than a system-assigned managed identity. If you use a user-assigned managed identity, you must pass the managed identity details to the Azure Monitor agent via extension settings:
+  - **User-assigned**: This managed identity is recommended for large-scale deployments, configurable via [built-in Azure policies](#use-azure-policy). You can create a user-assigned managed identity once and share it across multiple VMs, which means it's more scalable than a system-assigned managed identity. If you use a user-assigned managed identity, you must pass the managed identity details to the Azure Monitor agent via extension settings:
 
     ```json
     {