Update art and steps

Author: ecfan

articles/connectors/media/connectors-native-reqres/add-response.png

@@ -109,7 +109,7 @@ Before you can create an Azure function starting from inside your logic app by u
 
    * Between existing steps in your logic app's workflow, move your mouse over the arrow, select the plus (+) sign, and then select **Add an action**.
 
-1. In the search box, enter "azure functions" as your filter. From the actions list, select this action: **Choose an Azure function**
+1. In the search box, enter "azure functions" as your filter. From the actions list, select the **Choose an Azure function** action, for example:
 
    ![Find "Azure functions"](./media/logic-apps-azure-functions/find-azure-functions-action.png)
 
@@ -121,26 +121,26 @@ Before you can create an Azure function starting from inside your logic app by u
 
    1. In the **Function name** box, provide a name for your function.
 
-   1. In the **Code** box, add your code to the function template, including the response and payload that you want returned to your logic app after your function finishes running.
+   1. In the **Code** box, add your code to the function template, including the response and payload that you want returned to your logic app after your function finishes running. When you're done, select **Create**.
 
-      ![Define your function](./media/logic-apps-azure-functions/function-definition.png)
+   For example:
 
-      In the template's code, the *`context` object* refers to the message that your logic app sends through the **Request Body** field in a later step. To access the `context` object's properties from inside your function, use this syntax:
+   ![Define your function](./media/logic-apps-azure-functions/add-code-function-definition.png)
 
-      `context.body.<property-name>`
+   In the template's code, the *`context` object* refers to the message that your logic app sends through the **Request Body** field in a later step. To access the `context` object's properties from inside your function, use this syntax:
 
-      For example, to reference the `content` property inside the `context` object, use this syntax:
+   `context.body.<property-name>`
 
-      `context.body.content`
+   For example, to reference the `content` property inside the `context` object, use this syntax:
 
-      The template code also includes an `input` variable, which stores the value from the `data` parameter so your function can perform operations on that value. Inside JavaScript functions, the `data` variable is also a shortcut for `context.body`.
+   `context.body.content`
 
-      > [!NOTE]
-      > The `body` property here applies to the `context` object and 
-      > isn't the same as the **Body** token from an action's output, 
-      > which you might also pass to your function.
+   The template code also includes an `input` variable, which stores the value from the `data` parameter so your function can perform operations on that value. Inside JavaScript functions, the `data` variable is also a shortcut for `context.body`.
 
-   1. When you're done, select **Create**.
+   > [!NOTE]
+   > The `body` property here applies to the `context` object and 
+   > isn't the same as the **Body** token from an action's output, 
+   > which you might also pass to your function.
 
 1. In the **Request Body** box, provide your function's input, which must be formatted as a JavaScript Object Notation (JSON) object.
 
@@ -164,7 +164,7 @@ To call existing Azure functions from your logic apps, you can add Azure functio
 
 1. Under the step where you want to add the function, select **New step**.
 
-1. Under **Choose an action**, in the search box, enter "azure functions" as your filter. From the actions list, select this action: **Choose an Azure function**
+1. Under **Choose an action**, in the search box, enter "azure functions" as your filter. From the actions list, select the **Choose an Azure function** action.
 
    ![Find "Azure functions"](./media/logic-apps-azure-functions/find-azure-functions-action.png)
 

articles/logic-apps/logic-apps-azure-functions.md

@@ -27,13 +27,13 @@ You can use [Azure Functions](../azure-functions/functions-overview.md) to trigg
 
 ## Create logic app
 
-For this scenario, you have a function running each logic app that you want to trigger. First, create a logic app that starts with an HTTP request trigger. The function calls that endpoint whenever a queue message is received.  
+For this scenario, you have a function running each logic app that you want to trigger. First, create a logic app that starts with an HTTP request trigger. The function calls that endpoint whenever a queue message is received.
 
 1. Sign in to the [Azure portal](https://portal.azure.com), and create blank logic app.
 
    If you're new to logic apps, review [Quickstart: Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
 
-1. In the search box, enter "http request". From the triggers list, select this trigger: **When a HTTP request is received**
+1. In the search box, enter `http request`. From the triggers list, select the **When a HTTP request is received** trigger.
 
    ![Select trigger](./media/logic-apps-scenario-function-sb-trigger/when-http-request-received-trigger.png)
 
@@ -148,4 +148,4 @@ Next, create the function that acts as the trigger and listens to the queue.
 
 ## Next steps
 
-[Call, trigger, or nest workflows by using HTTP endpoints](../logic-apps/logic-apps-http-endpoint.md)
+* [Call, trigger, or nest workflows by using HTTP endpoints](../logic-apps/logic-apps-http-endpoint.md)