Fix Acrolinx issues

Author: ecfan

articles/connectors/built-in.md

@@ -601,7 +601,7 @@ For more information, review the following documentation:
 [scope-doc]: ../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md "Organize actions into groups, which get their own status after the actions in group finish running"
 [sftp-doc]: /azure/logic-apps/connectors/built-in/reference/sftp/ "Connect to your SFTP account by using SSH. Upload, get, delete files, and more"
 [smtp-doc]: /azure/logic-apps/connectors/built-in/reference/smtp/ "Connect to your SMTP server so you can send email"
-[sql-server-doc]: /azure/logic-apps/connectors/built-in/reference/sql/ "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in an SQL database table"
+[sql-server-doc]: /azure/logic-apps/connectors/built-in/reference/sql/ "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in a SQL database table"
 [switch-doc]: ../logic-apps/logic-apps-control-flow-switch-statement.md "Organize actions into cases, which are assigned unique values. Run only the case whose value matches the result from an expression, object, or token. If no matches exist, run the default case"
 [swift-doc]: https://techcommunity.microsoft.com/t5/azure-integration-services-blog/announcement-public-preview-of-swift-message-processing-using/ba-p/3670014 "Encode and decode SWIFT transactions in flat-file XML format"
 [terminate-doc]: ../logic-apps/logic-apps-workflow-actions-triggers.md#terminate-action "Stop or cancel an actively running workflow for your logic app workflow"

articles/connectors/connectors-create-api-cosmos-db.md

@@ -68,7 +68,7 @@ To add an Azure Cosmos DB built-in trigger to a Standard workflow, follow these
    | **Database Id** | Yes | <*database-name*> | The name of the database with the container to monitor. This database should also have the lease container. If you don't have a lease container, the connector creates one for you in a later step. |
    | **Monitored Container Id** | Yes | <*container-name*> | The name of the container to monitor. This container should exist in the specified database. |
    | **Lease Container Id** |  Yes | <*lease-container-name*> | The name of either an existing container or a new container to create. The trigger automatically populates with **`leases`** as the default name. |
-   | **Create Lease Container** | No | **No** or **Yes** | If the lease container exists in the specified database, select **No**. To create this container, select **Yes**. If you select **Yes** and are using manual throughput dedicated for each container, make sure to open the **Advanced parameters** list to select the **Lease Container Throughput** parameter. Enter the number of [request units (RUs)](/azure/cosmos-db/request-units) to provision for this container. |
+   | **Create Lease Container** | No | **No** or **Yes** | If the lease container exists in the specified database, select **No**. To create this container, select **Yes**. If you select **Yes** and are using manual throughput dedicated for each container, make sure to open the **Advanced parameters** list to select the **Lease Container Throughput** parameter. Enter the number of [request units (RUs)](/azure/cosmos-db/request-units) to deploy for this container. |
 
    > [!NOTE]
    >
@@ -101,7 +101,7 @@ To add an Azure Cosmos DB action to a Consumption workflow, follow these steps:
 
 1. If the workflow is blank, add any trigger that you want.
 
-   This example starts with the [**When a HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger).
+   This example starts with the [**When an HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger).
 
 1. Under the trigger or action where you want to add the Azure Cosmos DB action, follow [these general steps to add the **Azure Cosmos DB** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action?tabs=consumption#add-action).
 
@@ -138,9 +138,9 @@ To add an Azure Cosmos DB built-in action to a Standard workflow, follow these s
 
 1. If the workflow is blank, add any trigger that you want.
 
-   This example starts with the [**When a HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger), which uses a basic schema definition to represent the item that you want to create:
+   This example starts with the [**When an HTTP request is received** trigger](connectors-native-reqres.md#add-request-trigger), which uses a basic schema definition to represent the item that you want to create:
 
-   :::image type="content" source="./media/connectors-create-api-cosmos-db/http-trigger-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and trigger named When a HTTP request is received.":::
+   :::image type="content" source="./media/connectors-create-api-cosmos-db/http-trigger-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and trigger named When an HTTP request is received.":::
 
 1. Under the trigger or action where you want to add the Azure Cosmos DB action, follow [these general steps to add the **Azure Cosmos DB** action that you want](/azure/logic-apps/create-workflow-with-trigger-or-action?tabs=standard#add-action).
 
@@ -161,7 +161,7 @@ To add an Azure Cosmos DB built-in action to a Standard workflow, follow these s
    | **Container Id** | Yes | <*container-ID*> | The container to query. |
    | **Item** | Yes | <*JSON-document*> | The JSON document to create. This example uses the **id** output from the Request trigger. <br><br>**Note**: If you use the **body** trigger output, make sure that the body content is well-formed JSON, and at a minimum, contains the **`id`** attribute and the **`partitionKey`** attribute for your document. If a document with these attributes exists, the document is updated. Otherwise, a new document is created. |
 
-   The following example shows the action named **Create or update item**, which includes the **Item** and **Partition Key** parameter values from the output for the trigger named **When a HTTP request is received**:
+   The following example shows the action named **Create or update item**, which includes the **Item** and **Partition Key** parameter values from the output for the trigger named **When an HTTP request is received**:
 
    :::image type="content" source="media/connectors-create-api-cosmos-db/create-action-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard workflow, and Azure Cosmos DB built-in action named Create or update item.":::
 
@@ -217,7 +217,7 @@ For a Standard workflow, an Azure Cosmos DB connection (built-in) requires the f
 
 ### Get iterable results from the Query items action
 
-The **Query items** built-in action in a Standard workflow has many dynamic content outputs available for use in subsequent actions. To get the query result items or item metadata as an iterable object, follow these steps:
+In a Standard workflow, the **Query items** built-in action produces many dynamic content output items for use in subsequent actions. To get the query result items or item metadata as an iterable object, follow these steps:
 
 1. In the [Azure portal](https://portal.azure.com), open your Standard workflow in the designer.
 

articles/connectors/introduction.md

@@ -37,7 +37,7 @@ In Azure Logic Apps, connectors are either *built in* or *managed*. Some connect
 
 * [Managed connectors](managed.md) are deployed, hosted, and managed in Azure by Microsoft. Managed connectors mostly provide a proxy or a wrapper around an API that the underlying service or system uses to communicate with Azure Logic Apps.
 
-  In the designer, all managed connectors appear in the connector gallery within the **Shared** group. They are billed at either the **Standard** or **Enterprise** level.
+  In the designer, all managed connectors appear in the connector gallery within the **Shared** group. They're billed at either the **Standard** or **Enterprise** level.
 
 For more information, see the following documentation:
 
@@ -66,7 +66,7 @@ When the trigger fires, the trigger usually passes along event outputs for subse
 
 ## Actions
 
-An action specifies a task to perform and always appears as a subsequent step in the workflow. You can use multiple actions in your workflow. For example, you might start the workflow with a [SQL Server trigger](/connectors/sql/#triggers) that checks for new customer data in an SQL database. Following the trigger, your workflow can have a [SQL Server action](/connectors/sql/#actions) that gets the customer data. Following this SQL Server action, your workflow can use a different action that processes the data, for example, a [Data Operations action](../logic-apps/logic-apps-perform-data-operations.md) that creates a CSV table.
+An action specifies a task to perform and always appears as a subsequent step in the workflow. You can use multiple actions in your workflow. For example, you might start the workflow with a [SQL Server trigger](/connectors/sql/#triggers) that checks for new customer data in a SQL database. Following the trigger, your workflow can have a [SQL Server action](/connectors/sql/#actions) that gets the customer data. Following this SQL Server action, your workflow can use a different action that processes the data, for example, a [Data Operations action](../logic-apps/logic-apps-perform-data-operations.md) that creates a CSV table.
 
 <a name="connection-configuration"></a>
 

articles/connectors/managed.md

@@ -383,7 +383,7 @@ For more information, review the following documentation:
 [slack-doc]: ./connectors-create-api-slack.md "Connect to Slack and post messages to Slack channels"
 [smtp-doc]: ./connectors-create-api-smtp.md "Connect to an SMTP server and send email with attachments"
 [sparkpost-doc]: ./connectors-create-api-sparkpost.md "Connects to SparkPost for communication"
-[sql-server-doc]: ./connectors-create-api-sqlazure.md "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in an SQL database table"
+[sql-server-doc]: ./connectors-create-api-sqlazure.md "Connect to Azure SQL Database or SQL Server. Create, update, get, and delete entries in a SQL database table"
 [teradata-doc]: /connectors/teradata/ "Connect to your Teradata database to read data from tables"
 [twilio-doc]: ./connectors-create-api-twilio.md "Connect to Twilio. Send and get messages, get available numbers, manage incoming phone numbers, and more"
 [youtube-doc]: ./connectors-create-api-youtube.md "Connect to YouTube. Manage your videos and channels"

articles/connectors/media/connectors-create-api-cosmos-db/action-consumption.png

@@ -200,7 +200,7 @@ As your vector databases continue to ingest data, make sure the data is easily s
 
 The following pattern is only one example that shows how a chat workflow might look:
 
-:::image type="content" source="media/azure-ai/chat-workflow.png" alt-text="Screenshot that the shows Azure portal, Standard workflow designer, and workflow operations that implement a chat interaction.":::
+:::image type="content" source="media/azure-ai/chat-workflow.png" alt-text="Screenshot that shows the Azure portal, Standard workflow designer, and workflow operations that implement a chat interaction.":::
 
 | Step | Task | Underlying operation | Description |
 |------|------|----------------------|-------------|

articles/connectors/media/connectors-create-api-cosmos-db/create-action-standard.png

@@ -39,7 +39,7 @@ When the workflow receives an HTTPS request for a specified file through the **R
 > You can use the **Code Interpreter (Python Container Apps session)** operations outside an agent loop 
 > action or in non-agentic workflows in a Standard logic app. However, you must provide your own Python 
 > code for the **Execute Python code** action. In these cases, the **Code Interpreter** operations 
-> don't have access to agentic capabilities provided by the agent loop-linked AI model, which include 
+> don't have access to agentic capabilities provided by the agent loop-linked AI model, which includes 
 > natural language interactions and model-generated code.
 
 Your agentic workflow can process files that contain diverse or fragmented data and have formats such as CSV, Excel, or JSON, which can include thousands to millions of rows. However, raw data often needs extra work before you can extract useful information and insights, for example: