Apply suggestions from code review

Co-authored-by: Esther Fan <[email protected]>

Author: cdpark

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

@@ -23,7 +23,7 @@ This capability provides the following benefits:
 
 - Write your own scripts within the workflow designer so you can solve complex integration challenges. No other service plans are necessary.
 
-  This benefit streamlines workflow development, and it reduces the complexity and cost with managing more services.
+  This benefit reduces the complexity and cost because you can manage more services and streamlines workflow development.
 
 - Generate a dedicated code file, which provides a personalized scripting space within your workflow.
 
@@ -68,7 +68,7 @@ This guide shows how to add the action in your workflow and add the PowerShell c
 
 1. On the workflow sidebar menu, under **Tools**, select the designer to open the workflow.
 
-1. Add the **Inline Code Operations** action named **Execute PowerShell Code** to your workflow by following the [general steps to add a trigger](add-trigger-action-workflow.md?tabs=standard#add-action).
+1. Add the **Inline Code Operations** action named **Execute PowerShell Code** to your workflow by following the [general steps to add an action](add-trigger-action-workflow.md?tabs=standard#add-action).
 
 1. After the action information pane opens, on the **Parameters** tab, in the **Code File** box, update the prepopulated sample code with your own code.
 
@@ -224,7 +224,7 @@ From inside the **Execute PowerShell Code** action, you can authenticate and aut
 
 To use the managed identity from inside the **Execute PowerShell Code** action, you must follow these steps:
 
-1. Set up the managed identity on your logic app and grant the managed identity access on the target Azure resource. To learn how, see [Authenticate access and connections to Azure resources with managed identities](authenticate-with-managed-identity.md?tabs=standard).
+1. Set up the managed identity on your logic app and grant the managed identity access on the target Azure resource. For detailed steps, see [Authenticate access and connections to Azure resources with managed identities](authenticate-with-managed-identity.md?tabs=standard).
 
    On the target Azure resource, review the following considerations:
 
@@ -291,15 +291,15 @@ A module organizes PowerShell code, making it easier to distribute. For example,
 
 To find publicly available modules, visit the [PowerShell gallery](https://www.powershellgallery.com). A Standard logic app resource can support up to 10 public modules. To use any public module, you must enable this capability by following these steps:
 
-1. In the [Azure portal](https://portal.azure.com), on your logic app resource menu, under Development Tools, select **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**.
 
 1. On the **Kudu** toolbar, from the **Debug console** menu, select **CMD**.
 
 1. Browse to your logic app's root level at **C:\home\site\wwwroot** by using the directory structure or the command line.
 
-1. Open the workflow's *host.json* file, and set the **managed dependency** property to **true**, which is already set by default.
+1. Open the workflow's *host.json* file, and set the `ManagedDependency.enabled` property to `true`, which is already set by default.
 
    ```json
    "managedDependency": {
@@ -328,7 +328,7 @@ If you use dependency management, the following considerations apply:
 
 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, select **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**.
 

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

@@ -1,14 +1,14 @@
 ---
-title: Add Conditions to Control Workflow Actions
-description: Learn how to create conditions that control workflow actions in Azure Logic Apps.
+title: Add Conditions to Control Action Execution
+description: Learn how to create conditions so you can control action execution in workflows for Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.date: 06/20/2025
 ---
 
-# Add conditions to control workflow actions in Azure Logic Apps
+# Add conditions to control workflow action execution in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
@@ -41,21 +41,23 @@ This guide shows how to add a condition to your workflow and use the result to h
 
 1. On the sidebar menu, under **Development Tools**, select the designer to open the blank workflow.
 
-1. Add the trigger named **When a feed item is published** to your workflow by following the [general steps to add a trigger](add-trigger-action-workflow.md?tabs=consumption#add-trigger).
+   This example uses the **RSS** trigger named **When a feed item is published** to start the workflow. However, you can use any trigger that you want in your own scenarios.
+
+1. Add the trigger that you want by following the [general steps to add a trigger](add-trigger-action-workflow.md?tabs=consumption#add-trigger).
 
 1. Add the **Condition** action to your workflow by following the [general steps to add an action](add-trigger-action-workflow.md?tabs=consumption#add-action).
 
 1. In the **Condition** action, follow these steps to build your condition:
 
-   1. In the box named **Choose a value**, enter the first value or field that you want to compare.
+   1. In the left-side box named **Choose a value**, enter the first value or field that you want to compare.
 
       After you select inside the **Choose a value** box, the options to open the dynamic content list (lightning icon) or expression editor (formula icon) appear.
 
       :::image type="content" source="media/logic-apps-control-flow-conditional-statement/open-dynamic-content-consumption.png" alt-text="Screenshot shows Azure portal, Consumption workflow designer, RSS trigger, and Condition action with information pane open, and dynamic content button selected.":::
 
    1. Select the lightning icon to open the dynamic content list.
 
-      From this list, you can select outputs from previous steps in your workflow. This example selects the RSS trigger output named **Feed summary**. If you don't see this option, you might need to select **See more**.
+      From this list, you can select outputs from previous steps in your workflow. This example selects the **RSS** trigger output named **Feed summary**. If you don't see this option, you might need to select **See more**.
 
       :::image type="content" source="media/logic-apps-control-flow-conditional-statement/edit-condition-consumption.png" alt-text="Screenshot shows Azure portal, Consumption workflow designer, RSS trigger, and Condition action with criteria construction.":::