fix

Author: bwren

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

@@ -7,7 +7,7 @@ ms.date: 04/08/2022
 ---
 
 # Collect text and IIS logs with Azure Monitor agent (preview)
-This articles describes how to configure the collection of file-based text logs, including logs generated by IIS on Windows computers, with the [Azure Monitor agent](azure-monitor-agent-overview.md).  This feature uses a [data collection rule](../essentials/data-collection-rule-overview.md) that you can use to define the structure of the log file and its target table. 
+This article describes how to configure the collection of file-based text logs, including logs generated by IIS on Windows computers, with the [Azure Monitor agent](azure-monitor-agent-overview.md). Many applications log information to text files instead of standard logging services such as Windows Event log or Syslog. 
 
 > [!NOTE]
 > This feature is currently in public preview and isn't completely implemented in the Azure portal. This tutorial uses Azure Resource Manager templates for steps that can't yet be performed with the portal.
@@ -26,12 +26,11 @@ The log file must meet the following criteria to be collected by this feature:
 - Each entry in the log file must be delineated with an [ISO 8601 formatted](https://www.iso.org/standard/40874.html) time stamp or an end of line.
 - The log file must not allow circular logging, log rotation where the file is overwritten with new entries, or the file is renamed and the same file name is reused for continued logging.
 
-## 
 
 ## Steps to collect text logs
 The steps to configure log collection are as follows. The detailed steps for each are provided in the sections below:
 
-1. Create a new table in your workspace to receive the collected data.
+1. Create a new table in your workspace to receive the collected data. (not required for IIS logs)
 2. Create a data collection endpoint for the Azure Monitor agent to connect.
 3. Create a data collection rule to define the structure of the log file and destination of the collected data.
 4. Create association between the data collection rule and the agent collecting the log file.
@@ -170,13 +169,11 @@ The [data collection rule (DCR)](../essentials/data-collection-rule-overview.md)
 
     :::image type="content" source="../logs/media/tutorial-ingestion-time-transformations-api/build-custom-template.png" lightbox="../logs/media/tutorial-ingestion-time-transformations-api/build-custom-template.png" alt-text="Screenshot that shows portal blade to build template in the editor.":::
 
-3. Paste on of the Resource Manager templates below into the editor and then change the following values:
-
-    You may choose to modify the following details in the DCR defined in this template:
+3. Paste one of the Resource Manager templates below into the editor and then change the following values:
 
     - `streamDeclarations`: Defines the columns of the incoming data. This must match the structure of the log file.
     - `filePatterns`: Specifies the location and file pattern of the log files to collect. This defines a separate pattern for Windows and Linux agents.
-    - `transformKql`: Specifies a [transformation](../logs/../essentials/data-collection-rule-transformations.md) to apply to the incoming data before it's sent to the workspace. Since data collection rules for Azure Monitor agent don't yet support transformations, this value will always be `source`.
+    - `transformKql`: Specifies a [transformation](../logs/../essentials/data-collection-rule-transformations.md) to apply to the incoming data before it's sent to the workspace. Data collection rules for Azure Monitor agent don't yet support transformations, so this value should currently be `source`.
 
 
 4. Click **Save**.