Merge pull request #224789 from paulth1/agents-articles-batch-5

[AQ] edit pass: Agents articles batch 5

Author: ShawnJackson

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

@@ -129,5 +129,5 @@ If the query returns results, you need to determine if a particular data type is
     |Event ID |Source |Description |Resolution |
     |---------|-------|------------|-----------|
     |8000 |HealthService |This event will specify if a workflow related to performance, event, or other data type collected is unable to forward to the service for ingestion to the workspace. | Event ID 2136 from source HealthService is written together with this event and can indicate the agent is unable to communicate with the service. Possible reasons might be misconfiguration of the proxy and authentication settings, network outage, or the network firewall or proxy doesn't allow TCP traffic from the computer to the service.|
-    |10102 and 10103 |Health Service Modules |Workflow couldn't resolve the data source. |This issue can occur if the specified performance counter or instance doesn't exist on the computer or is incorrectly defined in the workspace data settings. If this is a user-specified [performance counter](data-sources-performance-counters.md#configuring-performance-counters), verify the information specified follows the correct format and exists on the target computers. |
+    |10102 and 10103 |Health Service Modules |Workflow couldn't resolve the data source. |This issue can occur if the specified performance counter or instance doesn't exist on the computer or is incorrectly defined in the workspace data settings. If this is a user-specified [performance counter](data-sources-performance-counters.md#configure-performance-counters), verify the information specified follows the correct format and exists on the target computers. |
     |26002 |Health Service Modules |Workflow couldn't resolve the data source. |This issue can occur if the specified Windows event log doesn't exist on the computer. This error can be safely ignored if the computer isn't expected to have this event log registered. Otherwise, if this is a user-specified [event log](data-sources-windows-events.md#configure-windows-event-logs), verify the information specified is correct. |

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

@@ -1,57 +1,57 @@
 ---
-title: Collect IIS logs with Log Analytics agent in Azure Monitor
-description: Internet Information Services (IIS) stores user activity in log files that can be collected by Azure Monitor.  This article describes how to configure collection of IIS logs and details of the records they create in Azure Monitor.
+title: Collect IIS logs with the Log Analytics agent in Azure Monitor
+description: This article describes how to configure collection of IIS log files that store user activity and the details of the records they create in Azure Monitor.
 ms.topic: conceptual
 ms.date: 03/31/2022
 ms.reviewer: JeffWo
 
 ---
 
-# Collect IIS logs with Log Analytics agent in Azure Monitor
+# Collect IIS logs with the Log Analytics agent in Azure Monitor
 Internet Information Services (IIS) stores user activity in log files that can be collected by the Log Analytics agent and stored in [Azure Monitor Logs](../data-platform.md).
 
-![IIS logs](media/data-sources-iis-logs/overview.png)
+![Diagram that shows IIS logs.](media/data-sources-iis-logs/overview.png)
 
 > [!IMPORTANT]
-> This article covers collecting IIS logs with the [Log Analytics agent](./log-analytics-agent.md), which **will be deprecated by August 2024**. Please be sure to [migrate to Azure Monitor agent](./azure-monitor-agent-manage.md) before August 2024 to continue ingesting data. See [Collect text logs with Azure Monitor agent (preview)](../agents/data-collection-text-log.md) for details on collecting IIS logs with [Azure Monitor agent](azure-monitor-agent-overview.md).
+> This article covers collecting IIS logs with the [Log Analytics agent](./log-analytics-agent.md), which **will be deprecated by August 2024**. Be sure to [migrate to Azure Monitor Agent](./azure-monitor-agent-manage.md) before August 2024 to continue ingesting data. See [Collect text logs with Azure Monitor Agent (preview)](../agents/data-collection-text-log.md) for details on collecting IIS logs with [Azure Monitor Agent](azure-monitor-agent-overview.md).
 
-
-## Configuring IIS logs
+## Configure IIS logs
 Azure Monitor collects entries from log files created by IIS, so you must [configure IIS for logging](/previous-versions/orphan-topics/ws.11/hh831775(v=ws.11)).
 
-Azure Monitor only supports IIS log files stored in W3C format and does not support custom fields or IIS Advanced Logging. It does not collect logs in NCSA or IIS native format.
-
-Configure IIS logs in Azure Monitor from the [Agent configuration menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics agent.  There is no configuration required other than selecting **Collect W3C format IIS log files**.
+Azure Monitor only supports IIS log files stored in W3C format and doesn't support custom fields or IIS Advanced Logging. It doesn't collect logs in NCSA or IIS native format.
 
+Configure IIS logs in Azure Monitor from the [Agent configuration menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics agent. No configuration is required other than selecting **Collect W3C format IIS log files**.
 
 ## Data collection
-Azure Monitor collects IIS log entries from each agent each time the log timestamp changes. The log is read every **5 minutes**. If for any reason IIS doesn't update the timestamp before the rollover time when a new file is created, entries will be collected following creation of the new file. The frequency of new file creation is controlled by the **Log File Rollover Schedule** setting for the IIS site, which is once a day by default. If the setting is **Hourly**, Azure Monitor collects the log each hour. If the setting is **Daily**, Azure Monitor collects the log every 24 hours.
+Azure Monitor collects IIS log entries from each agent each time the log timestamp changes. The log is read every 5 minutes. If for any reason IIS doesn't update the timestamp before the rollover time when a new file is created, entries will be collected following creation of the new file.
+
+The frequency of new file creation is controlled by the **Log File Rollover Schedule** setting for the IIS site. The setting is once a day by default. If the setting is **Hourly**, Azure Monitor collects the log each hour. If the setting is **Daily**, Azure Monitor collects the log every 24 hours.
 
 > [!IMPORTANT]
-> It is recommended to set the **Log File Rollover Schedule** to **Hourly**. If it's set to **Daily**, you may experience spikes in your data since it will only be collected once per day.
+> We recommend that you set **Log File Rollover Schedule** to **Hourly**. If it's set to **Daily**, you might experience spikes in your data because it will be collected only once per day.
 
 ## IIS log record properties
-IIS log records have a type of **W3CIISLog** and have the properties in the following table:
+IIS log records have a type of **W3CIISLog** and have the properties shown in the following table:
 
 | Property | Description |
 |:--- |:--- |
 | Computer |Name of the computer that the event was collected from. |
 | cIP |IP address of the client. |
-| csMethod |Method of the request such as GET or POST. |
+| csMethod |Method of the request, such as GET or POST. |
 | csReferer |Site that the user followed a link from to the current site. |
 | csUserAgent |Browser type of the client. |
 | csUserName |Name of the authenticated user that accessed the server. Anonymous users are indicated by a hyphen. |
-| csUriStem |Target of the request such as a web page. |
+| csUriStem |Target of the request, such as a webpage. |
 | csUriQuery |Query, if any, that the client was trying to perform. |
-| ManagementGroupName |Name of the management group for Operations Manager agents.  For other agents, this is AOI-\<workspace ID\> |
+| ManagementGroupName |Name of the management group for Operations Manager agents. For other agents, this name is AOI-\<workspace ID\>. |
 | RemoteIPCountry |Country/region of the IP address of the client. |
 | RemoteIPLatitude |Latitude of the client IP address. |
 | RemoteIPLongitude |Longitude of the client IP address. |
 | scStatus |HTTP status code. |
 | scSubStatus |Substatus error code. |
 | scWin32Status |Windows status code. |
 | sIP |IP address of the web server. |
-| SourceSystem |OpsMgr |
+| SourceSystem |OpsMgr. |
 | sPort |Port on the server the client connected to. |
 | sSiteName |Name of the IIS site. |
 | TimeGenerated |Date and time the entry was logged. |
@@ -60,7 +60,7 @@ IIS log records have a type of **W3CIISLog** and have the properties in the foll
 | csBytes | Number of bytes that the server received. |
 
 ## Log queries with IIS logs
-The following table provides different examples of log queries that retrieve IIS log records.
+Different examples of log queries that retrieve IIS log records are shown in the following table:
 
 | Query | Description |
 |:--- |:--- |