Apply suggestions from code review

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

Author: cdpark

articles/logic-apps/add-run-javascript.md

@@ -1,6 +1,6 @@
 ---
-title: Add and Run JavaScript in Workflows
-description: Write and run JavaScript code snippets in workflows to perform custom integration tasks using Inline Code operations in Azure Logic Apps.
+title: Run JavaScript in Workflows
+description: Learn how to run JavaScript code snippets in workflows for custom integration tasks by using Inline Code operations in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
@@ -42,7 +42,7 @@ The following diagram shows the highlights from an example workflow:
 
 * The logic app resource with the workflow where you want to add your code snippet. The workflow must already start with a trigger.
 
-  This article's example uses the Office 365 Outlook trigger named **When a new email arrives**.
+  This article's example uses the **Office 365 Outlook** trigger named **When a new email arrives**.
 
   If you don't have a logic app resource and workflow, create them now by following the steps for the logic app that you want:
 
@@ -107,7 +107,9 @@ The following diagram shows the highlights from an example workflow:
 
    :::image type="content" source="media/add-run-javascript/save-email-body-variable-consumption.png" alt-text="Screenshot showing the Consumption workflow, Execute JavaScript Code action, and example code that creates variables.":::
 
-1. With your cursor still in the **Code** box, select **Add dynamic content**. Find the **When a new email arrives** section, and select the **Body** property, which references the email message's body.
+1. With your cursor still in the **Code** box, select the lightning icon to open the dynamic content list.
+
+1. In the list, under the **When a new email arrives** section, select the **Body** property, which references the trigger output with the email message body.
 
    :::image type="content" source="media/add-run-javascript/select-output-consumption.png" alt-text="Screenshot showing the Consumption workflow, Execute JavaScript Code action, dynamic content list, and email message's Body property selected.":::
 
@@ -355,13 +357,13 @@ Before you start, you need the JSON name for the trigger or action in the underl
 
   `My.Action.Name`
 
-1. On the workflow menu, select **Code view**. In the `actions` object, find the action's name.
+1. On the workflow menu, under **Tools**, select **Code** to view the workflow's JSON definition. In the `actions` object, find the action's name.
 
    For example, `Send_approval_email` is the JSON name for the **Send approval email** action.
 
    :::image type="content" source="media/add-run-javascript/find-action-name-json.png" alt-text="Screenshot showing the action name in JSON.":::
 
-1. To return to designer view, on the workflow menu, select **Designer**.
+1. To return to designer view, on the workflow menu, under **Tools**, select **Designer**.
 
 1. Now add the JSON name to the **Execute JavaScript Code** action.
 
@@ -394,5 +396,5 @@ For more information about the **Execute JavaScript Code** action's structure an
 
 ## Related content
 
-* [List of all Logic Apps connectors](/connectors/connector-reference/connector-reference-logicapps-connectors)
-* [Built-in connectors in Azure Logic Apps](../connectors/built-in.md)
+* [Managed connectors for Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)
+* [Built-in connectors for Azure Logic Apps](../connectors/built-in.md)

articles/logic-apps/handle-throttling-problems-429-errors.md

@@ -1,6 +1,6 @@
 ---
 title: Handle Throttling Problems or 429 Too Many Requests
-description: How to work around throttling problems or 'HTTP 429 Too many requests' errors in Azure Logic Apps.
+description: Learn how to handle workflow throttling problems or 'HTTP 429 Too many requests' errors in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
@@ -72,11 +72,11 @@ To handle throttling at this level, you have the following options:
 
   * A Standard workflow has no limit on the number of actions that can run during any interval.
 
-* Disable array debatching or **SplitOn** behavior in triggers.
+* Disable array debatching or **Split On** setting in triggers.
 
-  If a trigger returns an array for the remaining workflow actions to process, the trigger's [SplitOn setting](logic-apps-workflow-actions-triggers.md#split-on-debatch) divides up the array items and starts a workflow instance for each array item. This behavior effectively triggers multiple concurrent runs up to the [SplitOn limit](logic-apps-limits-and-config.md#concurrency-looping-and-debatching-limits).
+  If a trigger returns an array for the remaining workflow actions to process, the trigger's [**Split On** setting](logic-apps-workflow-actions-triggers.md#split-on-debatch) divides up the array items and starts a workflow instance for each array item. This behavior effectively triggers multiple concurrent runs up to the [**Split On** limit](logic-apps-limits-and-config.md#concurrency-looping-and-debatching-limits).
 
-  To control throttling, turn off the trigger's **SplitOn** behavior and have your workflow process the entire array with a single call, rather than handle a single item per call.
+  To control throttling, turn off the trigger's **Split On** setting and have your workflow process the entire array with a single call, rather than handle a single item per call.
 
 * Refactor actions into multiple, smaller workflows.
 
@@ -104,7 +104,7 @@ Each connector has its own throttling limits, which you can find on [each connec
 
 Some triggers and actions, such as HTTP, have a [retry policy](logic-apps-exception-handling.md#retry-policies) that you can customize based on the [retry policy limits](logic-apps-limits-and-config.md#retry-policy-limits) to implement exception handling. This policy specifies whether and how often a trigger or action retries a request when the original request fails or times out and results in a 408, 429, or 5xx response. So, when throttling starts and returns a 429 error, Logic Apps follows the retry policy where supported.
 
-To learn whether a trigger or action supports retry policies, check the trigger or action's settings. To view a trigger or action's retry attempts, go to your logic app's run history, select the run that you want to review, and expand that trigger or action to view details about inputs, outputs, and any retries.
+To learn whether a trigger or action supports retry policies, check the trigger or action's settings. To view a trigger or action's retry attempts, go to your logic app workflow's run history, select the run that you want to review, and expand that trigger or action to view details about inputs, outputs, and any retries.
 
 The following Consumption workflow example shows where you can find this information for an HTTP action:
 

articles/logic-apps/logic-apps-http-endpoint.md

@@ -1,6 +1,6 @@
 ---
 title: Create Callable or Nestable Workflows
-description: Create workflows that receive inbound requests over HTTPS endpoints in Azure Logic Apps.
+description: Learn how to create workflows that receive inbound requests through HTTPS endpoints in Azure Logic Apps.
 services: logic-apps
 ms.reviewer: estfan, azla
 ms.topic: how-to
@@ -210,7 +210,7 @@ Based on whether you have a Standard or Consumption logic app workflow, follow t
 
 By default, the **Request** trigger expects a `POST` request. However, you can specify a different method that the caller must use, but only a single method.
 
-1. In the **Request** trigger, select the **Method** dropdown, then choose the method that the trigger should expect instead. Or, you can specify a custom method.
+1. In the **Request** trigger, from the **Method** list, select the method that the trigger should expect instead. Or, you can specify a custom method.
 
    For example, select the **GET** method so that you can test your endpoint's URL later.
 
@@ -234,11 +234,11 @@ When you want to accept parameter values through the endpoint's URL, you have th
 
 ### [Standard](#tab/standard)
 
-1. In the **Request** trigger, select the **Method** dropdown, and then choose the **GET** method.
+1. In the **Request** trigger, from the **Method** list, select the **GET** method.
 
    For more information, see [Select expected request method](#select-method).
 
-1. Add the action named **Response** to your workflow by following the [general steps to add an action](add-trigger-action-workflow.md?tabs=standard#add-action).
+1. Add the **Response** action to your workflow by following the [general steps to add an action](add-trigger-action-workflow.md?tabs=standard#add-action).
 
 1. To build the `triggerOutputs()` expression that retrieves the parameter value, follow these steps:
 
@@ -370,7 +370,7 @@ When you want to accept parameter values through the endpoint's URL, you have th
 
    1. In the **Body** property, enter `Postal Code: ` with a trailing space. Keep your cursor inside the edit box so that the dynamic content list remains open.
 
-   1. Select the lightning symbol to open the dynamic content list. From the **When a HTTP request is received** section, select the **postalCode** trigger output.
+   1. Select the lightning icon to open the dynamic content list. From the **When a HTTP request is received** section, select the **postalCode** trigger output.
 
       :::image type="content" source="./media/logic-apps-http-endpoint/response-trigger-output-standard.png" alt-text="Screenshot shows Standard workflow, Response action, and specified trigger output to include in response body." lightbox="./media/logic-apps-http-endpoint/response-trigger-output-standard.png":::