updated based on symantics and syntax check tool report

Author: NarineM

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

@@ -73,7 +73,7 @@ Azure Monitor Agent uses [data collection rules](../essentials/data-collection-r
     |:---|:---|:---|
     | Performance | Azure Monitor Metrics (Public preview)<sup>1</sup> - Insights.virtualmachine namespace<br>Log Analytics workspace - [Perf](/azure/azure-monitor/reference/tables/perf) table | Numerical values measuring performance of different aspects of operating system and workloads |
     | Windows event logs (including sysmon events) | Log Analytics workspace - [Event](/azure/azure-monitor/reference/tables/Event) table | Information sent to the Windows event logging system |
-    | Syslog | Log Analytics workspace - [Syslog](/azure/azure-monitor/reference/tables/syslog)<sup>2</sup> table | Information sent to the Linux event logging system. [Colllect syslog with Azure Monitor Agent](data-collection-syslog.md) |
+    | Syslog | Log Analytics workspace - [Syslog](/azure/azure-monitor/reference/tables/syslog)<sup>2</sup> table | Information sent to the Linux event logging system. [Collect syslog with Azure Monitor Agent](data-collection-syslog.md) |
     |	Text logs and Windows IIS logs	|	Log Analytics workspace - custom table(s) created manually |	[Collect text logs with Azure Monitor Agent](data-collection-text-log.md)	|
 
 

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

@@ -19,7 +19,7 @@ Here's how AMA collects syslog events:
 	> [!NOTE]
 	> AMA uses local persistency by default, all events received from `rsyslog` / `syslog-ng` are queued in `/var/opt/microsoft/azuremonitoragent/events` if they fail to be uploaded.
 
-## Rsyslog data not uploaded due to Full Disk space issue on AMA Linux Agent
+## Rsyslog data not uploaded due to full disk space issue on Azure Monitor Linux Agent
 
 ### Symptom
 **Syslog data is not uploading**: When inspecting the error logs at `/var/opt/microsoft/azuremonitoragent/log/mdsd.err`, you'll see entries about *Error while inserting item to Local persistent store…No space left on device* similar to the following snippet:
@@ -31,7 +31,7 @@ Here's how AMA collects syslog events:
 ### Cause
 Linux AMA buffers events to `/var/opt/microsoft/azuremonitoragent/events` prior to ingestion. On a default Linux AMA install, this directory will take ~650MB of disk space at idle. The size on disk will increase when under sustained logging load. It will get cleaned up about every 60 seconds and will reduce back to ~650 MB when the load returns to idle.
 
-### Confirming the issue of Full Disk
+### Confirming the issue of full disk
 The `df` command shows almost no space available on `/dev/sda1`, as shown below:
 
 ```
@@ -85,7 +85,7 @@ If you're sending a high log volume through rsyslog, consider modifying the defa
 	```
 2. `sudo systemctl restart rsyslog`
 
-## Issue: AMA Event Buffer is Filling Disk
+## Issue: Azure Monitor Linux Agent Event Buffer is Filling Disk
 If you observe the `/var/opt/microsoft/azuremonitor/events` directory growing unbounded (10 GB or higher) and not reducing in size, [file a ticket](#file-a-ticket) with **Summary** as 'AMA Event Buffer is filling disk' and **Problem type** as 'I need help configuring data collection from a VM'.
 
 [!INCLUDE [azure-monitor-agent-file-a-ticket](../../../includes/azure-monitor-agent/azure-monitor-agent-file-a-ticket.md)]

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

@@ -14,7 +14,7 @@ Syslog is an event logging protocol that's common to Linux. You can use the Sysl
 
 ![Diagram that shows Syslog collection.](media/data-sources-syslog/overview.png)
 
-![Diagram that shows Syslog daemon and Azure Monitor Agent communication.](media/azure-monitor-agent/linux_agent_syslog_communication.png)
+![Diagram that shows Syslog daemon and Azure Monitor Agent communication.](media/azure-monitor-agent/linux-agent-syslog-communication.png)
 
 The following facilities are supported with the Syslog collector:
 * auth
@@ -71,7 +71,7 @@ A data collection rule is an Azure resource that allows you to define the way  d
 
 1. Select **Add data source**.
 1. For **Data source type**, select **Linux syslog**.
-   :::image type="content" source="../../sentinel/media/forward-syslog-monitor-agent/create-rule-data-source.png" alt-text="Screenshot of page to select data source type and minimum log level":::
+   :::image type="content" source="../../sentinel/media/forward-syslog-monitor-agent/create-rule-data-source.png" alt-text="Screenshot of page to select data source type and minimum log level.":::
 1. For **Minimum log level**, leave the default values **LOG_DEBUG**.
 1. Select **Next: Destination**.