Fix Acrolinx issues

Author: ecfan

articles/connectors/apis-list.md

@@ -41,7 +41,7 @@ A trigger also passes along any inputs and other required data into your workflo
 
 ### Actions
 
-An *action* is an operation that follows the trigger and performs some kind of task in your workflow. You can use multiple actions in your workflow. For example, you might start the workflow with a SQL trigger that detects new customer data in an SQL database. Following the trigger, your workflow can have a SQL action that gets the customer data. Following the SQL action, your workflow can have another action, not necessarily SQL, that processes the data.
+An *action* is an operation that follows the trigger and performs some kind of task in your workflow. You can use multiple actions in your workflow. For example, you might start the workflow with a SQL trigger that detects new customer data in an SQL database. Following the trigger, your workflow can have a SQL action that gets the customer data. Following the SQL action, your workflow can have a different action that processes the data.
 
 ## Connector categories
 
@@ -112,7 +112,7 @@ For more information, review the following documentation:
 
 ### Recurrence for connection-based triggers
 
-In recurring connection-based triggers, such as Office 365 Outlook, the schedule isn't the only driver that controls execution. The time zone only determines the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior, for example:
+For recurring connection-based triggers, such as Office 365 Outlook, the schedule isn't the only driver that controls execution. The time zone only determines the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior, for example:
 
 * Whether the trigger accesses a server that has more data, which the trigger immediately tries to fetch.
 * Any failures or retries that the trigger incurs.

articles/connectors/built-in.md

@@ -45,7 +45,7 @@ In Standard logic app workflows, a built-in connector that has the following att
 
 * Runs in the same process as the redesigned Azure Logic Apps runtime.
 
-These service provider-based built-in connectors are available alongside their [managed connector versions](managed.md).
+Service provider-based built-in connectors are available alongside their [managed connector versions](managed.md).
 
 In contrast, a built-in connector that's *not a service provider* has the following attributes: