Fix egregious acrolinx issues

Author: cwatson-cat

articles/sentinel/data-connectors/1password.md

@@ -66,7 +66,7 @@ To integrate with 1Password (using Azure Functions) make sure you have:
 [Follow these instructions](https://support.1password.com/events-reporting/#appendix-issue-or-revoke-bearer-tokens) provided by 1Password to obtain an Events Reporting API Token. A 1Password Business account is required.
 
 
-**STEP 2 - Deploy the functionApp using DeployToAzure button to create the table, dcr and the associated Azure Function**
+**STEP 2 - Deploy the functionApp using DeployToAzure button to create the table, data collection rule, and the associated Azure Function**
 
 **IMPORTANT:** Before deploying the 1Password connector, a custom table needs to be created.
 
@@ -77,7 +77,7 @@ This method provides an automated deployment of the 1Password connector using an
 1. Click the **Deploy to Azure** button below. 
 
 	[![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-OnePassword-azuredeploy)
-2. Select the preferred **Subscription**, **Resource Group** and **Location**. 
+2. Select the preferred **Subscription**, **Resource Group**, and **Location**. 
 3. Enter the **Workspace Name**, **Workspace Name**, **1Password Events API Key**, and **URI**.
      - The default **Time Interval** is set to five (5) minutes. If you'd like to modify the interval, you can adjust the Function App Timer Trigger accordingly (in the function.json file, post deployment) to prevent overlapping data ingestion.
      - If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details. 

articles/sentinel/data-connectors/tenable-identity-exposure.md

@@ -11,7 +11,7 @@ ms.collection: sentinel-data-connector
 
 # Tenable Identity Exposure connector for Microsoft Sentinel
 
-Tenable Identity Exposure connector allows Indicators of Exposure, Indicators of Attack and trailflow logs to be ingested into Microsoft Sentinel.The different work books and data parsers allow you to more easily manipulate logs and monitor your Active Directory environment.  The analytic templates allow you to automate responses regarding different events, exposures and attacks.
+Tenable Identity Exposure connector allows Indicators of Exposure, Indicators of Attack and trailflow logs to be ingested into Microsoft Sentinel.The different work books and data parsers allow you to more easily manipulate logs and monitor your Active Directory environment.  The analytic templates allow you to automate responses regarding different events, exposures, and attacks.
 
 This is autogenerated content. For changes, contact the solution provider.
 
@@ -151,7 +151,7 @@ This data connector depends on [afad_parser](https://aka.ms/sentinel-TenableApp-
 
 2. Install and onboard the Microsoft agent for Linux
 
-   The OMS agent will receive the TenableIE syslog events and publish it in Microsoft Sentinel :
+   The OMS agent will receive the TenableIE syslog events and publish it in Microsoft Sentinel.
 
 
 3. Check agent logs on the Syslog server
@@ -183,7 +183,7 @@ Configure the agent to collect the logs.
 
 6. Enjoy!
 
-You should now be able to receive logs in the *Tenable_IE_CL* table, logs data can be parse using the **afad_parser()** function, used by all query samples, workbooks and analytic templates.
+You should now be able to receive logs in the *Tenable_IE_CL* table, logs data can be parse using the **afad_parser()** function, used by all query samples, workbooks, and analytic templates.
 
 
 

articles/sentinel/data-connectors/tenable-vulnerability-management.md

@@ -102,7 +102,7 @@ Use this method for automated deployment of the TenableVM Vulnerability Manageme
 1. Click the **Deploy to Azure** button below. 
 
 	[![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-TenableVM-azuredeploy)
-2. Select the preferred **Subscription**, **Resource Group** and **Location**. 
+2. Select the preferred **Subscription**, **Resource Group**, and **Location**. 
 3. Enter the **TenableAccessKey** and **TenableSecretKey** and deploy. 
 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 
 5. Click **Purchase** to deploy.

articles/sentinel/data-connectors/transmit-security-connector.md

@@ -11,7 +11,7 @@ ms.collection: sentinel-data-connector
 
 # Transmit Security Connector (using Azure Functions) connector for Microsoft Sentinel
 
-The [Transmit Security] data connector provides the capability to ingest common Transmit Security API events into Microsoft Sentinel through the REST API. [Refer to API documentation for more information](https://developer.transmitsecurity.com/). The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
+The Transmit Security data connector provides the capability to ingest common Transmit Security API events into Microsoft Sentinel through the REST API. [Refer to API documentation for more information](https://developer.transmitsecurity.com/). The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
 
 This is autogenerated content. For changes, contact the solution provider.
 
@@ -119,10 +119,10 @@ If you're already signed in, go to the next step.
 
 	e. **Select a runtime:** Choose Python 3.8.
 
-	f. Select a location for new resources. For better performance and lower costs choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
+	f. Select a location for new resources. For better performance and lower costs, choose the same [region](https://azure.microsoft.com/regions/) where Microsoft Sentinel is located.
 
 6. Deployment will begin. A notification is displayed after your function app is created and the deployment package is applied.
-7. Go to Azure Portal for the Function App configuration.
+7. Go to Azure portal for the Function App configuration.
 
 
 **2. Configure the Function App**