Draft updates

Author: ecfan

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

@@ -16,7 +16,7 @@ ms.custom: engagement-fy23, devx-track-dotnet
 
 This guide shows how to locally create an example Standard logic app workflow that you can run in single-tenant Azure Logic Apps when you use Visual Studio Code with the **Azure Logic Apps (Standard)** extension.
 
-In this guide, you'll create a Standard logic app workspace and project, build your workflow, and ultimately deploy your project as a Standard logic app resource in Azure where your workflow can run in single-tenant Azure Logic Apps or in App Service Environment v3 (Windows-based App Service plans only). You can also deploy and run your workflow anywhere that Kubernetes can run, such as Azure, Azure Kubernetes Service, on premises, or even other cloud providers, due to the containerized runtime for Azure Logic Apps (Standard).
+In this guide, you create a Standard logic app workspace and project, build your workflow, and deploy your project as a Standard logic app resource in Azure where your workflow can run in single-tenant Azure Logic Apps or in App Service Environment v3 (Windows-based App Service plans only). You can also deploy and run your workflow anywhere that Kubernetes can run, such as Azure, Azure Kubernetes Service, on premises, or even other cloud providers, due to the containerized runtime for Azure Logic Apps (Standard).
 
 Here are just some benefits that Standard logic apps provide:
 
@@ -908,7 +908,7 @@ Deployment for the Standard logic app resource requires a hosting plan and prici
 
    1. For the option to use SQL storage in this example, select **No**.
 
-      If you already set up a SQL database to use for storage by following [Set up SQL database storage for Standard logic app workflows](/azure/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows), you can select **Yes**.
+      If you already set up an SQL database to use for storage by following [Set up SQL database storage for Standard logic app workflows](/azure/logic-apps/set-up-sql-db-storage-single-tenant-standard-workflows), you can select **Yes**.
 
    1. For the Application Insights resource, which enables diagnostic logging and tracing for your logic app, choose from the following options:
 
@@ -1149,7 +1149,7 @@ After Application Insights opens, you can review various metrics for your logic
 
 ### Designer fails to open
 
-When you try to open the designer, you get this error, **"Workflow design time could not be started"**. If you previously tried to open the designer, and then discontinued or deleted your project, the extension bundle might not correctly download. To check whether this reason is the cause, follow these steps:
+When you try to open the designer, you get this error, **"Workflow design time could not be started"**. If you previously tried to open the designer, but you discontinued or deleted your project, the extension bundle might not correctly download. To check whether this reason is the cause, follow these steps:
 
   1. In Visual Studio Code, open the Output window. From the **View** menu, select **Output**.
 
@@ -1213,7 +1213,7 @@ The missing triggers and actions now appear in the designer.
 
 When a run fails, and you inspect the run in monitoring view, this error might appear on a trigger or action that has a longer name, which causes the underlying Uniform Resource Identifier (URI) to exceed the default character limit.
 
-To resolve this problem and adjust for the longer URI, edit the **`UrlSegmentMaxCount`** and **`UrlSegmentMaxLength`** registry keys on your computer by following the steps below. These key's default values are described in this topic, [Http.sys registry settings for Windows](/troubleshoot/iis/httpsys-registry-windows).
+To resolve this problem and adjust for the longer URI, edit the **`UrlSegmentMaxCount`** and **`UrlSegmentMaxLength`** registry keys on your computer by following these steps. These key's default values are described in this article, [Http.sys registry settings for Windows](/troubleshoot/iis/httpsys-registry-windows).
 
 > [!IMPORTANT]
 >
@@ -1252,7 +1252,7 @@ To resolve this problem and adjust for the longer URI, edit the **`UrlSegmentMax
 
 When you try to start a debugging session, you get the error, **"Error exists after running preLaunchTask 'generateDebugSymbols'"**. To resolve this problem, edit the **tasks.json** file in your project to skip symbol generation.
 
-1. In your project, expand the **.vscode** folder, and open the **tasks.json** file.
+1. In your project, expand the.vscode** folder, and open the **tasks.json** file.
 
 1. In the following task, delete the line, **`"dependsOn: "generateDebugSymbols"`**, along with the comma that ends the preceding line, for example:
 

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

@@ -14,7 +14,7 @@ ms.custom: devx-track-dotnet
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
-This guide shows how to manage deployed logic apps that you create using Visual Studio Code and how to perform tasks such as edit, disable, enable, and delete workflows. If you have both extensions for **Azure Logic Apps (Consumption)** and **Azure Logic Apps (Standard)** installed in Visual Studio Code, you can view all the deployed logic apps in your Azure subscription and perform management tasks with some that vary based on the logic app type.
+This guide shows how to work with deployed logic apps in Visual Studio Code and how to perform tasks such as edit, disable, enable, and delete. If you have both extensions for **Azure Logic Apps (Consumption)** and **Azure Logic Apps (Standard)** installed in Visual Studio Code, you can view all the deployed logic apps in your Azure subscription and perform management tasks with some that vary based on the logic app type.
 
 ## Prerequisites
 
@@ -159,7 +159,7 @@ To edit a deployed Consumption or Standard workflow using the designer, make tho
 > Before you change your workflow, you might want to stop or disable your workflow. Make sure 
 > that you understand how your changes affect your workflow's operation. When you're done, 
 > remember to restart or reenable your workflow. For considerations around stopping, disabling, 
-> restarting, or reenabling workflows, see the following documentation:
+> restarting, or re-enabling workflows, see the following documentation:
 >
 > - [Considerations for stopping Consumption logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=consumption#considerations-stop-consumption-logic-apps)
 > - [Considerations for stopping Standard logic apps](/azure/logic-apps/manage-logic-apps-with-azure-portal?tabs=standard#considerations-stop-standard-logic-apps)
@@ -220,7 +220,7 @@ Deployed Consumption and Standard logic apps have different ways to disable and
 
 1. In the **Logic Apps (Consumption)** section, expand your Azure subscription, and find your logic app.
 
-1. Open the logic app shortcut menu. Based on the current actvitity state, select **Disable** or **Enable**.
+1. Open the logic app shortcut menu. Based on the current activity state, select **Disable** or **Enable**.
 
 ### [Standard](#tab/standard)
 
@@ -232,13 +232,13 @@ Stopping the resource versus disabling a workflow have different effects, so rev
 
 1. In the **Resources** section, expand your Azure subscription, and find your logic app.
 
-1. Open the logic app shortcut menu. Based on the current actvitity state, select **Stop** or **Start**. Or, you can select **Restart**.
+1. Open the logic app shortcut menu. Based on the current activity state, select **Stop** or **Start**. Or, you can select **Restart**.
 
 ---
 
 ## Post logic app stoppage
 
-After you stop a logic app, workflow triggers won't fire the next time that their conditions are met. However, trigger states remember the points at where you stopped the logic app. When you a restart a logic app, the trigger fires for all unprocessed items since the last workflow run.
+After you stop a logic app, workflow triggers won't fire the next time that their conditions are met. However, trigger states remember the points at where you stopped the logic app. When you restart a logic app, the trigger fires for all unprocessed items since the last workflow run.
 
 To stop a trigger from firing on unprocessed items since the last workflow run, you must clear the trigger state before you restart a logic app by following these steps:
 
@@ -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. When you're done, [restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=consumption#disable-enable-logic-apps).
+1. [Restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?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. When you're done, [restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=standard#disable-enable-logic-apps).
+1. [Restart your logic app](/azure/logic-apps/manage-logic-apps-visual-studio-code?tabs=standard#disable-enable-logic-apps).
 
 ---
 

articles/logic-apps/toc.yml

@@ -447,6 +447,8 @@ items:
     items:
     - name: Manage logic apps - Azure portal
       href: manage-logic-apps-with-azure-portal.md
+    - name: Manage logic apps - Visual Studio Code
+      href: manage-logic-apps-visual-studio-code.md
     - name: Manage logic apps - Visual Studio
       href: manage-logic-apps-with-visual-studio.md
     - name: Manage integration accounts