Add edits

Author: cdpark

articles/logic-apps/add-run-powershell-scripts.md

@@ -242,7 +242,7 @@ To use the managed identity from inside the **Execute PowerShell Code** action,
 
 1. On the logic app resource menu, under **Development Tools**, select **Advanced Tools**.
 
-1. On the **Advanced Tools** page, select **Go**, which opens the **KuduPlus** console.
+1. On the **Advanced Tools** page, select **Go**, which opens the **Kudu Plus** console.
 
 1. Open the **Debug console** menu, and select **CMD**.
 
@@ -314,13 +314,13 @@ If you use dependency management, the following considerations apply:
 
 - To download modules, public modules require access to the [PowerShell Gallery](https://www.powershellgallery.com).
 
-- Managed dependencies currently don't support modules that require you to accept a license, either by accepting the license interactively or by providing the **-AcceptLicense** option when you run **Install-Module**.
+- Managed dependencies currently don't support modules that require you to accept a license, either by accepting the license interactively or by providing the `-AcceptLicense` option when you run **Install-Module**.
 
 ### Private modules
 
 You can generate your own private PowerShell modules. To create your first PowerShell module, see [Write a PowerShell Script Module](/powershell/scripting/developer/module/how-to-write-a-powershell-script-module).
 
-1. In the [Azure portal](https://portal.azure.com), on your logic app resource menu, under Development Tools, selects **Advanced Tools**.
+1. In the [Azure portal](https://portal.azure.com), on your logic app resource menu, under Development Tools, select **Advanced Tools**.
 
 1. On the **Advanced Tools** page, select **Go**.
 
@@ -363,7 +363,7 @@ Make sure that you use the `Push-WorkflowOutput` cmdlet.
 
 ### Execute PowerShell Code action fails: "The term '{some-text}' is not recognized..."
 
-If you incorrectly reference a public module in the **requirements.psd1** file or when your private module doesn't exist in the following path: **C:\home\site\wwwroot\Modules\{module-name}**, you get the following error:
+If you incorrectly reference a public module in the **requirements.psd1** file, or if your private module doesn't exist in the path **C:\home\site\wwwroot\Modules\{module-name}**, you get the following error:
 
 **"The term '{some-text}' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name or if a path was included, verify the path is correct and try again."**
 

articles/logic-apps/logic-apps-control-flow-conditional-statement.md

@@ -29,7 +29,7 @@ This guide shows how to add a condition to your workflow and use the result to h
 
 * An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-* Basic knowledge about [logic app workflows](logic-apps-overview.md)
+* Basic knowledge about [logic app workflows](logic-apps-overview.md).
 
 * To follow the example in this how-to guide, create either an [example Consumption logic app workflow](quickstart-create-example-consumption-workflow.md) or an [example Standard logic app workflow](create-single-tenant-workflows-azure-portal.md) and use either an Outlook.com account or a Microsoft work or school account.
 

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

@@ -148,15 +148,7 @@ After you create your Liquid template, you now have to upload the template based
 
 1. On the **Maps** pane toolbar, select **Add**.
 
-1. On the **Add Map** pane, provide the following information about your template:
-
-   | Property | Value | Description |
-   |----------|-------|-------------|
-   | **Name** | `JsonToJsonTemplate` | The name for your map, which is "JsonToJsonTemplate" in this example |
-   | **Map type** | **Liquid** | The type for your map. For JSON to JSON transformation, you must select **Liquid**. |
-   | **Map** | `SimpleJsonToJsonTemplate.liquid` | An existing Liquid template or map file to use for transformation, which is "SimpleJsonToJsonTemplate.liquid" in this example. To find this file, you can use the file picker. For map size limits, see [Limits and configuration](../logic-apps/logic-apps-limits-and-config.md#artifact-capacity-limits). |
-
-1. When you're done, select **OK**.
+1. On the **Add Map** pane, drag and drop your file to the upload box, or select **Browse for files**.
 
    After your map file finishes uploading, the map appears in the **Maps** list. On your integration account's **Overview** page, under **Artifacts**, your uploaded map also appears.
 
@@ -172,9 +164,7 @@ The following steps show how to add a Liquid transformation action for Consumpti
 
    This example continues with the Request trigger named **When a HTTP request is received**.
 
-1. On the workflow designer, under the step where you want to add the Liquid action, select **New step**.
-
-1. Under the **Choose an operation** search box, select **All**. In the search box, enter **liquid**.
+1. Under the trigger, select **Add an action**. In the search box, enter **liquid**.
 
 1. From the actions list, select the Liquid action that you want to use.
 
@@ -184,7 +174,7 @@ The following steps show how to add a Liquid transformation action for Consumpti
 
 1. In the action's **Content** property, provide the JSON output from the trigger or a previous action that you want to transform by following these steps.
 
-   1. Click inside the **Content** box so that the dynamic content list appears.
+   1. Click inside the **Content** box so that the dynamic content list appears. Select the lightning icon.
 
    1. From the dynamic content list, select the JSON data that you want to transform.
 
@@ -203,10 +193,6 @@ The following steps show how to add a Liquid transformation action for Consumpti
    > If the maps list is empty, either your logic app resource isn't linked to your 
    > integration account, or your integration account doesn't contain any map files.
 
-   When you're done, the action looks similar to the following example:
-
-   :::image type="content" source="media/logic-apps-enterprise-integration-liquid-transform/finished-transform-action-consumption.png" alt-text="Screenshot showing Consumption workflow with finished Transform JSON to JSON action.":::
-
 1. Save your workflow. On the designer toolbar, select **Save**.
 
 ### [Standard](#tab/standard)
@@ -229,7 +215,7 @@ The following steps show how to add a Liquid transformation action for Consumpti
 
 1. In the action's **Content** property, provide the JSON output from the trigger or a previous action that you want to transform by following these steps.
 
-   1. Click inside the **Content** box so that the dynamic content list appears.
+   1. Click inside the **Content** box so that the dynamic content list appears. Select the lightning icon.
 
    1. From the dynamic content list, select the JSON data that you want to transform.
 
@@ -260,10 +246,6 @@ The following steps show how to add a Liquid transformation action for Consumpti
    > If the maps list is empty, most likely your logic app resource isn't linked to your integration account. 
    > Make sure to [link your logic app resource to the integration account that has the Liquid template or map](logic-apps-enterprise-integration-create-integration-account.md?tabs=standard#link-account).
 
-   When you're done, the action looks similar to the following example:
-
-   ![Screenshot showing Standard workflow with finished "Transform JSON to JSON" action.](./media/logic-apps-enterprise-integration-liquid-transform/finished-transform-action-standard.png)
-
 1. Save your workflow. On the designer toolbar, select **Save**.
 
 ---