Fix Acrolinx issues

Author: ecfan

articles/logic-apps/create-standard-workflows-visual-studio-code.md

@@ -307,8 +307,6 @@ To create your workflow, start your workflow with a trigger, and then initially
 
 1. Save your workflow. On the designer toolbar, select **Save**.
 
-If you need to delete an item from the designer, [follow these steps for deleting items from the designer](/azure/logic-apps/manage-standard-workflows-visual-studio-code#delete-from-designer).
-
 ### Add the Office 365 Outlook action
 
 1. On the designer, under the **Request** trigger, [follow these general steps to add the **Office 365 Outlook** action named **Send an email (V2)**](/azure/logic-apps/create-workflow-with-trigger-or-action?tabs=standard#add-action).
@@ -519,7 +517,7 @@ In specific scenarios, your workflow might include operations that require depen
 | Maps | **.xslt** | For more information, see [Add maps for transformations in workflows](/azure/logic-apps/logic-apps-enterprise-integration-maps?tabs=standard#visual-studio-code-1). |
 | Schemas | **.xsd** | For more information, see [Add schemas for validation](/azure/logic-apps/logic-apps-enterprise-integration-schemas?tabs=standard#visual-studio-code). |
 | Rules | **.xml** | For more information, see [Create an Azure Logic Apps Rules Engine project](/azure/logic-apps/rules-engine/create-rules-engine-project#create-an-azure-logic-apps-rules-engine-project). |
-| Assemblies | - **.dll** (.NET Framework or .NET 8) <br><br>- **.jar** (Java) | A Standard logic app resource can use or reference specific kinds of assemblies, which you can upload to your project in Visual Studio Code. However, you must add them to specific project folders. For more information, see [Add referenced assemblies](azure/logic-apps/logic-apps-enterprise-integration-maps?tabs=standard#visual-studio-code-1). <br><br>**Note**: If you have a NuGet package-based (.NET) logic app project before assemblies support became available, see [Migrate NuGet package-based projects to use assemblies in the **lib** folder](#migrate-nuget-assemblies). |
+| Assemblies | - **.dll** (.NET Framework or .NET 8) <br><br>- **.jar** (Java) | A Standard logic app resource can use or reference specific kinds of assemblies, which you can upload to your project in Visual Studio Code. However, you must add them to specific project folders. For more information, see [Add referenced assemblies](/azure/logic-apps/logic-apps-enterprise-integration-maps?tabs=standard#visual-studio-code-1). <br><br>**Note**: If you have a NuGet package-based (.NET) logic app project before assemblies support became available, see [Migrate NuGet package-based projects to use assemblies in the **lib** folder](#migrate-nuget-assemblies). |
 
 <a name="convert-project-nuget"></a>
 

articles/logic-apps/manage-logic-apps-visual-studio-code.md

@@ -198,7 +198,7 @@ To edit a deployed Consumption or Standard workflow using the designer, make tho
 
    - Open the **workflow.json** file, and make your changes in the underlying JSON definition.
 
-1. When you're done, [publish your updated Standard logic app](/azure/logic-apps/create-standard-workflows-visual-studio-code#publish-new-logic-app).
+1. When you're done, [publish your updated Standard logic app](create-standard-workflows-visual-studio-code.md#publish-new-logic-app).
 
 1. If your workflow is disabled, remember to reenable your workflow.
 
@@ -224,7 +224,7 @@ Deployed Consumption and Standard logic apps have different ways to disable and
 
 ### [Standard](#tab/standard)
 
-In Visual Studio Code, you can stop, start, or restart a Standard logic app, which affects all workflow instances. You can also restart a Standard logic app without first stopping its activity. However, to disable and reenable individual workflows, [you must use the Azure portal](/azure/logic-apps/manage-logic-apps-with-azure-portal/stop-start-standard-workflows).
+In Visual Studio Code, you can stop, start, or restart a Standard logic app, which affects all workflow instances. You can also restart a Standard logic app without first stopping its activity. However, to disable and reenable individual workflows, [you must use the Azure portal](/azure/logic-apps/manage-logic-apps-with-azure-portal#stop-start-standard-workflows).
 
 Stopping the resource versus disabling a workflow have different effects, so review the considerations before you continue.
 
@@ -248,7 +248,7 @@ To stop a trigger from firing on unprocessed items since the last workflow run,
 
 1. Save your changes. This step resets your trigger's current state.
 
-1. [Restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=consumption#disable-enable-logic-apps).
+1. [Restart your logic app](manage-logic-apps-visual-studio-code.md?tabs=consumption#disable-enable-logic-apps).
 
 ### [Standard](#tab/standard)
 
@@ -258,7 +258,7 @@ To stop a trigger from firing on unprocessed items since the last workflow run,
 
 1. Repeat for each existing workflow.
 
-1. [Restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=standard#disable-enable-logic-apps).
+1. [Restart your logic app](manage-logic-apps-visual-studio-code.md?tabs=standard#disable-enable-logic-apps).
 
 ---
 

articles/logic-apps/manage-logic-apps-with-azure-portal.md

@@ -76,7 +76,7 @@ This guide shows how to manage Consumption or Standard logic app workflows using
 
 ## View connections
 
-When you create connections in a workflow using [connectors managed by Microsoft](../connectors/managed.md), these connections are actually separate Azure resources with their own resource definitions and are hosted in global, multitenant Azure. Standard logic app workflows can also use [built-in service provider connectors](/azure/logic-apps/connectors/built-in/reference/) that natively run and are powered by the single-tenant Azure Logic Apps runtime. To view and manage these connections, follow these steps, based on the logic app resource type:
+When you create connections in a workflow using [connectors managed by Microsoft](../connectors/managed.md), these connections are separate Azure resources with their own resource definitions and are hosted in global, multitenant Azure. Standard logic app workflows can also use [built-in service provider connectors](/azure/logic-apps/connectors/built-in/reference/) that natively run and are powered by the single-tenant Azure Logic Apps runtime. To view and manage these connections, follow these steps, based on the logic app resource type:
 
 ### [Consumption](#tab/consumption)
 
@@ -141,7 +141,7 @@ Stopping a Consumption logic app affects all workflow instances in the following
 
 * You can resubmit workflow runs while the logic app is stopped.
 
-* The workflow trigger doesn't fire while the logic app is stopped. However, the trigger state remembers the point where you stopped the logic app. When you restart the logic app, the trigger fires for all unprocessesd items since the last workflow run.
+* The workflow trigger doesn't fire while the logic app is stopped. However, the trigger state remembers the point where you stopped the logic app. When you restart the logic app, the trigger fires for all unprocessed items since the last workflow run.
 
   To stop the trigger from firing on all unprocessed items since the last workflow run, you must [clear the trigger state](#post-stoppage).
 
@@ -187,7 +187,7 @@ Stopping a Standard logic app affects all its workflow instances in the followin
 
 * You can resubmit workflow runs while the logic app is stopped.
 
-* Workflow triggers don't fire while the logic app is stopped. However, the trigger states remember the point where you stopped the logic app. When you restart the logic app, the triggers fire for all unprocessesd items since the last time that the corresponding workflows ran.
+* Workflow triggers don't fire while the logic app is stopped. However, the trigger states remember the point where you stopped the logic app. When you restart the logic app, the triggers fire for all unprocessed items since the last time that the corresponding workflows ran.
 
   To stop the triggers from firing on all unprocessed items since the last time that the workflows ran, you must [clear the trigger state for each workflow](#post-stoppage).
 
@@ -261,7 +261,7 @@ Disabling a workflow affects all its workflow instances in the following ways:
 
 * You can resubmit workflow runs while the workflow is disabled.
 
-* The workflow trigger doesn't fire while the logic app is stopped or the workflow is disabled. However, the trigger state remembers the point where you disabled the workflow. When you restart the logic app or re-enable the workflow, the trigger fires for all unprocessesd items since the last workflow run.
+* The workflow trigger doesn't fire while the logic app is stopped or the workflow is disabled. However, the trigger state remembers the point where you disabled the workflow. When you restart the logic app or re-enable the workflow, the trigger fires for all unprocessed items since the last workflow run.
 
   To stop the trigger from firing on all unprocessed items since the last workflow run, you must [clear the trigger state](#post-stoppage).
 
@@ -363,7 +363,7 @@ Deleting a Standard logic app affects all its workflow instances in the followin
 
 * Although you can [manually recover deleted Standard logic apps](#recover-deleted-standard-logic-apps), using source control to manage your Standard logic apps makes recovery and redeployment much easier.
 
-* If you don't use source control, and you might have to later recover a deleted Standard logic app, make sure to save any custom settings that you need for recovery before you delete the logic app logic app.
+* If you don't use source control, and you might have to later recover a deleted Standard logic app, make sure to save any custom settings that you need for recovery before you delete the logic app.
 
   1. In the [Azure portal](https://portal.azure.com), go to the Standard logic app.
 
@@ -373,7 +373,7 @@ Deleting a Standard logic app affects all its workflow instances in the followin
 
   1. On the logic app menu, under **Settings**, select **Configuration**.
 
-  1. On the each settings tab, find, and note any custom settings that you need for later recovery.
+  1. On each settings tab, note any custom settings that you need for later recovery.
 
 * If you delete a logic app and its workflows, but you then recreate the same logic app and workflows, the recreated logic app and workflows don't have the same metadata as the deleted resources.
 
@@ -508,7 +508,7 @@ To recover a deleted Standard logic app that uses the **Workflow Service Plan**
 
 1. Return to your replacement logic app.
 
-1. If you have custom settings to restore, on the logic app menu, under **Settings**, select **Environment variables** or **Configuration**, based on the types of settings that you have.
+1. If you have custom settings to restore, on the logic app menu, under Settings, selects **Environment variables** or **Configuration**, based on the types of settings that you have.
 
 1. When you're done, restart your logic app.