Fix Acrolinx issues

Author: ecfan

articles/logic-apps/logic-apps-enterprise-integration-create-integration-account.md

@@ -144,7 +144,7 @@ For this task, you can use the Azure portal, [Azure CLI](/cli/azure/resource#az-
        --name integration_account_01 --location westus --sku name=Standard
    ```
 
-   Your integration account name can contain only letters, numbers, hyphens (-), underscores (_), parentheses ((, )), and periods (.).
+   Your integration account name can contain only letters, numbers, hyphens (-), underscores (_), parentheses (()), and periods (.).
 
    To view a specific integration account, use the [az logic integration-account show](/cli/azure/logic/integration-account#az-logic-integration-account-show) command:
 

articles/logic-apps/logic-apps-enterprise-integration-flatfile.md

@@ -20,7 +20,7 @@ Before you send XML content to a business partner in a business-to-business (B2B
 >
 > In Standard logic app workflows, the **Flat File** actions are currently in preview.
 
-While no **Flat File** triggers are available, you can use any trigger or action to feed the source XML content into your workflow for encoding or decoding. For example, you can use a built-in connector trigger, a managed or Azure-hosted connector trigger available for Azure Logic Apps, or even another app.
+While no **Flat File** triggers are available, you can use any trigger or action to feed the source XML content into your workflow. For example, you can use a built-in connector trigger, a managed or Azure-hosted connector trigger available for Azure Logic Apps, or even another app.
 
 This article shows how to add the **Flat File** encoding and decoding actions to your workflow.
 
@@ -59,7 +59,7 @@ For more information, review the following documentation:
 
   * If you're working on a Consumption logic app workflow, your logic app resource requires a [link to your integration account](logic-apps-enterprise-integration-create-integration-account.md?tabs=consumption#link-account).
 
-  * If you're working on a Standard logic app workflow, you can link your your logic app resource to your integration account, upload schemas directly to your logic app resource, or both, based on the following scenarios:
+  * If you're working on a Standard logic app workflow, you can link your logic app resource to your integration account, upload schemas directly to your logic app resource, or both, based on the following scenarios:
 
     * If you already have an integration account with the artifacts that you need or want to use, you can link your integration account to multiple Standard logic app resources where you want to use the artifacts. That way, you don't have to upload schemas to each individual logic app. For more information, review [Link your logic app resource to your integration account](logic-apps-enterprise-integration-create-integration-account.md?tabs=standard#link-account).
 

articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md

@@ -14,7 +14,7 @@ ms.date: 08/15/2022
 
 When you want to perform basic JSON transformations in your logic app workflows, you can use built-in data operations, such as the **Compose** action or **Parse JSON** action. However, some scenarios might require advanced and complex transformations that include elements such as iterations, control flows, and variables. For transformations between JSON to JSON, JSON to text, XML to JSON, or XML to text, you can create a template that describes the required mapping or transformation using the Liquid open-source template language. You can select this template when you add a **Liquid** built-in action to your workflow. You can use **Liquid** actions in multi-tenant Consumption logic app workflows and single-tenant Standard logic app workflows.
 
-While no **Liquid** triggers are available, you can use any trigger or action to feed the source JSON or XML content into your workflow for transformation. For example, you can use a built-in connector trigger, a managed or Azure-hosted connector trigger available for Azure Logic Apps, or even another app.
+While no **Liquid** triggers are available, you can use any trigger or action to feed the source JSON or XML content into your workflow. For example, you can use a built-in connector trigger, a managed or Azure-hosted connector trigger available for Azure Logic Apps, or even another app.
 
 This article shows how to complete the following tasks:
 

articles/logic-apps/logic-apps-enterprise-integration-schemas.md

@@ -71,7 +71,7 @@ This article shows how to add a schema to your integration account. If you're wo
       | Blob container | In this container, you can upload your schema. You also need this container's content URI later when you add the schema to your integration account. Learn how to [create a blob container](../storage/blobs/storage-quickstart-blobs-portal.md). |
       | [Azure Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md) | This tool helps you more easily manage storage accounts and blob containers. To use Storage Explorer, choose a step: <br><br>- In the Azure portal, select your storage account. From your storage account menu, select **Storage Explorer**. <br><br>- For the desktop version, [download and install Azure Storage Explorer](https://www.storageexplorer.com/). Then, connect Storage Explorer to your storage account by following the steps in [Get started with Storage Explorer](../vs-azure-tools-storage-manage-with-storage-explorer.md). To learn more, see [Quickstart: Create a blob in object storage with Azure Storage Explorer](../storage/blobs/quickstart-storage-explorer.md). |
 
-      To add larger schemas, you can also the [Azure Logic Apps REST API - Schemas](/rest/api/logic/schemas/create-or-update). However, for Standard workflows, the Azure Logic Apps REST API is currently unavailable.
+      To add larger schemas, you can also use the [Azure Logic Apps REST API - Schemas](/rest/api/logic/schemas/create-or-update). However, for Standard workflows, the Azure Logic Apps REST API is currently unavailable.
 
 * Usually, when you're using an integration account with your workflow, you add the schema to that account. However, if you're referencing or importing a schema that's not in your integration account, you might receive the following error when you use the element `xsd:redefine`: