Fix Acrolinx issues

Author: ecfan

articles/logic-apps/quickstart-create-example-consumption-workflow.md

@@ -40,7 +40,7 @@ The connectors in this example are only two connectors among [1000+ connectors](
 
 As you progress through this quickstart, you'll learn the following basic high-level steps:
 
-* Create a Consumption logic app resource that's hosted in multitenant Azure Logic Apps.
+* Create a Consumption logic app resource that is hosted in multitenant Azure Logic Apps.
 * Add a trigger that specifies when to run the workflow.
 * Add an action that performs a task after the trigger fires.
 * Run your workflow.
@@ -67,7 +67,7 @@ To create and manage a Consumption logic app workflow using other tools, see the
   > [create a Google client app to use for authentication with your Gmail connector](/connectors/gmail/#authentication-and-bring-your-own-application). For more information, see 
   > [Data security and privacy policies for Google connectors in Azure Logic Apps](../connectors/connectors-google-data-security-privacy-policy.md).
 
-* If you have a firewall that limits traffic to specific IP addresses, make sure that you set up your firewall to allow access for both the [inbound](logic-apps-limits-and-config.md#inbound) and [outbound](logic-apps-limits-and-config.md#outbound) IP addresses used by Azure Logic Apps in the Azure region where you create your logic app workflow.
+* If you have a firewall that limits traffic to specific IP addresses, make sure that you set up your firewall to allow access for both the [inbound](logic-apps-limits-and-config.md#inbound) and [outbound](logic-apps-limits-and-config.md#outbound) IP addresses that Azure Logic Apps uses in the Azure region where you create your logic app workflow.
 
   This example uses the **RSS** and **Office 365 Outlook** connectors, which [run in global multitenant Azure and are managed by Microsoft](../connectors/managed.md). These connectors require that you set up your firewall to allow access for all the [managed connector outbound IP addresses](/connectors/common/outbound-ip-addresses) in the Azure region for your logic app resource.
 
@@ -231,13 +231,13 @@ This example uses an Office 365 Outlook action that sends an email each time tha
 
 ## Test your workflow
 
-To check that the workflow runs correctly, you can either wait for the trigger to fire after checking the RSS feed based on your specified schedule, or you can manually run the workflow.
+To check that the workflow runs correctly, you can either wait for the trigger to fire based on your specifed schedule, or you can manually run the workflow.
 
 * On the designer toolbar, from the **Run** menu, select **Run**.
 
 If the RSS feed has new items, your workflow sends an email for each new item. Otherwise, your workflow waits until the next interval to check the RSS feed again.
 
-The following screenshot shows a sample email that's sent by the example workflow. The email includes the details from each trigger output that you selected plus the descriptive text that you included for each item.
+The following screenshot shows a sample email that the example workflow sends. The email includes the details from each trigger output that you selected plus the descriptive text that you included for each item.
 
 :::image type="content" source="media/quickstart-create-example-consumption-workflow/monitor-rss-feed-email.png" alt-text="Screenshot shows Outlook and sample email received for new RSS feed item, along with item title, date published, and link." lightbox="media/quickstart-create-example-consumption-workflow/monitor-rss-feed-email.png":::
 
@@ -247,7 +247,7 @@ If you don't receive emails from the workflow as expected:
 
 * Check your email account's junk or spam folder, in case the message was incorrectly filtered.
 
-* Make sure the RSS feed you're using has published items since the last scheduled or manual check.
+* Make sure the RSS feed you're using published items since the last scheduled or manual check.
 
 ## Clean up resources