Update links to renamed quickstart and fix terminology for Azure Logic Apps

Author: ecfan

articles/data-factory/media/tutorial-control-flow-portal/success-email-workflow.png

@@ -53,14 +53,14 @@ This tutorial uses Azure portal. You can use other mechanisms to interact with A
     3. Upload **input.txt** file to the container.
 
 ## Create email workflow endpoints
-To trigger sending an email from the pipeline, you use [Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For details on creating a Logic App workflow, see [How to create a logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+To trigger sending an email from the pipeline, you use [Azure Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For more information about creating a logic app workflow, see [Create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md).
 
 ### Success email workflow
-Create a Logic App workflow named `CopySuccessEmail`. Define the workflow trigger as `When an HTTP request is received`, and add an action of `Office 365 Outlook – Send an email`.
+Create a Consumption logic app workflow named `CopySuccessEmail`. Add the Request trigger named **When an HTTP request is received**, and add the **Office 365 Outlook** action named **Send an email**. If prompted, sign in to your Office 365 Outlook account.
 
 :::image type="content" source="media/tutorial-control-flow-portal/success-email-workflow.png" alt-text="Shows a screenshot of the Success email workflow.":::
 
-For your request trigger, fill in the `Request Body JSON Schema` with the following JSON:
+For the Request trigger, fill in the **Request Body JSON Schema** box with the following JSON:
 
 ```json
 {
@@ -82,13 +82,13 @@ For your request trigger, fill in the `Request Body JSON Schema` with the follow
 }
 ```
 
-The Request in the Logic App Designer should look like the following image:
+The Request trigger in the workflow designer should look like the following image:
 
-:::image type="content" source="media/tutorial-control-flow-portal/logic-app-designer-request.png" alt-text="Shows a screenshot of the Logic App designer - request.":::
+:::image type="content" source="media/tutorial-control-flow-portal/logic-app-designer-request.png" alt-text="Shows a screenshot of the workflow designer with Request trigger.":::
 
-For the **Send Email** action, customize how you wish to format the email, utilizing the properties passed in the request Body JSON schema. Here is an example:
+For the **Send an email** action, customize how you wish to format the email, utilizing the properties passed in the request Body JSON schema. Here is an example:
 
-:::image type="content" source="media/tutorial-control-flow-portal/send-email-action-2.png" alt-text="Shows a screenshot of the Logic App designer - send email action.":::
+:::image type="content" source="media/tutorial-control-flow-portal/send-email-action-2.png" alt-text="Shows a screenshot of the workflow designer with the action named Send an email.":::
 
 Save the workflow. Make a note of your HTTP Post request URL for your success email workflow:
 
@@ -98,9 +98,9 @@ https://prodxxx.eastus.logic.azure.com:443/workflows/000000/triggers/manual/path
 ```
 
 ### Fail email workflow
-Follow the same steps to create another Logic Apps workflow of **CopyFailEmail**. In the request trigger, the `Request Body JSON schema` is the same. Change the format of your email like the `Subject` to tailor toward a failure email. Here is an example:
+Follow the same steps to create another logic app workflow named `CopyFailEmail`. In the Request trigger, the **Request Body JSON schema** value is the same. Change the format of your email like the `Subject` to tailor toward a failure email. Here is an example:
 
-:::image type="content" source="media/tutorial-control-flow-portal/fail-email-workflow-2.png" alt-text="Shows a screenshot of the Logic App designer - fail email workflow.":::
+:::image type="content" source="media/tutorial-control-flow-portal/fail-email-workflow-2.png" alt-text="Shows a screenshot of the workflow designer with the fail email workflow.":::
 
 Save the workflow. Make a note of your HTTP Post request URL for your failure email workflow:
 

articles/data-factory/tutorial-control-flow-portal.md

@@ -296,11 +296,11 @@ In your C# project, create a class named `EmailRequest`. This class defines what
 
 ## Create email workflow endpoints
 
-To trigger sending an email, you use [Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For details on creating a Logic Apps workflow, see [How to create a Logic App](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+To trigger sending an email, you use [Azure Logic Apps](../logic-apps/logic-apps-overview.md) to define the workflow. For more information, see [Create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md).
 
 ### Success email workflow
 
-In the [Azure portal](https://portal.azure.com), create a Logic Apps workflow named *CopySuccessEmail*. Define the workflow trigger as `When an HTTP request is received`. For your request trigger, fill in the `Request Body JSON Schema` with the following JSON:
+In the [Azure portal](https://portal.azure.com), create a logic app workflow named `CopySuccessEmail`. Add the Request trigger named **When an HTTP request is received**. In the Request trigger, fill in the **Request Body JSON schema** box with the following JSON:
 
 ```json
 {
@@ -328,17 +328,17 @@ Your workflow looks something like the following example:
 
 This JSON content aligns with the `EmailRequest` class you created in the previous section.
 
-Add an action of `Office 365 Outlook – Send an email`. For the **Send an email** action, customize how you wish to format the email, using the properties passed in the request **Body** JSON schema. Here's an example:
+Add the **Office 365 Outlook** action named **Send an email**. For this action, customize how you wish to format the email, using the properties passed in the request **Body** JSON schema. Here's an example:
 
-:::image type="content" source="media/tutorial-control-flow/customize-send-email-action.png" alt-text="Logic app designer - send email action":::
+:::image type="content" source="media/tutorial-control-flow/customize-send-email-action.png" alt-text="Workflow designer with the action named Send an email.":::
 
 After you save the workflow, copy and save the **HTTP POST URL** value from the trigger.
 
 ## Fail email workflow
 
-Clone **CopySuccessEmail** as another Logic Apps workflow named *CopyFailEmail*. In the request trigger, the `Request Body JSON schema` is the same. Change the format of your email like the `Subject` to tailor toward a failure email. Here is an example:
+Clone the `CopySuccessEmail` logic app workflow to a new workflow named `CopyFailEmail`. In the Request trigger, the **Request Body JSON schema** is the same. Change the format of your email like the `Subject` to tailor toward a failure email. Here is an example:
 
-:::image type="content" source="media/tutorial-control-flow/fail-email-workflow.png" alt-text="Logic app designer - fail email workflow":::
+:::image type="content" source="media/tutorial-control-flow/fail-email-workflow.png" alt-text="Workflow designer and the fail email workflow.":::
 
 After you save the workflow, copy and save the **HTTP POST URL** value from the trigger.
 

articles/data-factory/tutorial-control-flow.md

@@ -271,9 +271,9 @@ For this logic app, you build a workflow that regularly monitors ExpressRoute ga
 
 :::image type="content" source="./media/custom-route-alert-portal/logic-apps-workflow.png" alt-text="Logic Apps workflow":::
 
-### 1. Create a logic app
+### 1. Create a logic app resource
 
-In **Logic app designer**, create a logic app using the **Blank Logic App** template. For steps, see [Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+In the Azure portal, create a Consumption logic app resource and then select the **Blank Logic App** template. For more information, see [Create an example Consumption logic app workflow](../logic-apps/quickstart-create-example-consumption-workflow.md).
 
 :::image type="content" source="./media/custom-route-alert-portal/blank-template.png" alt-text="Blank template":::
 

articles/expressroute/how-to-custom-route-alert.md

@@ -412,7 +412,7 @@
         },
         {
             "source_path_from_root": "/articles/app-service-logic/app-service-logic-create-a-logic-app.md",
-            "redirect_url": "/azure/logic-apps/quickstart-create-first-logic-app-workflow",
+            "redirect_url": "/azure/logic-apps/quickstart-create-example-consumption-workflow",
             "redirect_document_id": false
         },
         {
@@ -542,7 +542,7 @@
         },
         {
             "source_path_from_root": "/articles/logic-apps/logic-apps-create-a-logic-app.md",
-            "redirect_url": "/azure/logic-apps/quickstart-create-first-logic-app-workflow",
+            "redirect_url": "/azure/logic-apps/quickstart-create-example-consumption-workflow",
             "redirect_document_id": true
         },
         {

articles/logic-apps/.openpublishing.redirection.logic-apps.json

@@ -66,7 +66,7 @@ To develop logic apps that run in your integration service environment (ISE), fo
 
 1. When you're done, select **Create**.
 
-1. Continue [creating your logic app in the usual way](../logic-apps/quickstart-create-first-logic-app-workflow.md).
+1. Continue [creating your logic app in the usual way](../logic-apps/quickstart-create-example-consumption-workflow.md).
 
    For differences in how triggers and actions work and how they're labeled when you use an ISE compared to the multi-tenant Logic Apps service, see [Isolated versus multi-tenant in the ISE overview](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#difference).
 

articles/logic-apps/add-artifacts-integration-service-environment-ise.md

@@ -176,7 +176,7 @@ To view a task's history of runs along with their statuses, inputs, outputs, and
 
    ![Screenshot that shows an expanded action, inputs, and outputs.](./media/create-automation-tasks-azure-resources/view-action-inputs-outputs.png)
 
-To learn how you can build your own automated workflows so that you can integrate apps, data, services, and systems apart from the context of automation tasks for Azure resources, see [Quickstart: Create your first integration workflow by using Azure Logic Apps - Azure portal](quickstart-create-first-logic-app-workflow.md).
+To learn how you can build your own automated workflows so that you can integrate apps, data, services, and systems apart from the context of automation tasks for Azure resources, see [Quickstart: Create an example Consumption logic app workflow - Azure portal](quickstart-create-example-consumption-workflow.md).
 
 <a name="edit-task"></a>
 

articles/logic-apps/create-automation-tasks-azure-resources.md

@@ -24,7 +24,7 @@ For more information about multi-tenant and single-tenant Azure Logic Apps, revi
 
 * A Consumption or Standard logic app workflow
 
-  If you don't have a logic app workflow yet, review [Create your first Consumption logic app workflow using the Azure portal](quickstart-create-first-logic-app-workflow.md) or [Create your first Standard logic app workflow using the Azure portal](create-single-tenant-workflows-azure-portal.md).
+  If you don't have a logic app workflow yet, see [Create an example Consumption logic app workflow using the Azure portal](quickstart-create-example-consumption-workflow.md) or [Create an example Standard logic app workflow using the Azure portal](create-single-tenant-workflows-azure-portal.md).
 
     > [!NOTE]
     > Currently, you can create parameters for Consumption logic app workflows only by using the Azure portal. 

articles/logic-apps/create-parameters-workflows.md

@@ -18,7 +18,7 @@ To extend and expand your flow's capabilities, you can migrate that flow from [P
 > Export to Azure Logic Apps is unavailable for Power Automate flows created after August 2020. In October 2020, Power Automate 
 > standardized new flow creation on the [OpenAPI 2.0 protocol](https://swagger.io/specification/v2/). New flows based on 
 > this protocol are incompatible with Azure Logic Apps workflows, so exporting these flows to Azure Logic Apps was disabled. 
-> Instead, you must manually [create a logic app workflow](quickstart-create-first-logic-app-workflow.md) for these flows.
+> Instead, you must manually [create a Consumption logic app workflow](quickstart-create-example-consumption-workflow.md) for these flows.
 
 Not all Power Automate connectors are available in Azure Logic Apps. You can migrate only Power Automate flows that have the equivalent connectors in Azure Logic Apps. For example, the Button trigger, the Approval connector, and Notification connector are specific to Power Automate. 
 

articles/logic-apps/export-from-microsoft-flow-logic-app-template.md

@@ -57,9 +57,9 @@ landingContent:
     linkLists:
       - linkListType: quickstart
         links:
-          - text: Create Consumption logic app - Azure portal
-            url: quickstart-create-first-logic-app-workflow.md
-          - text: Create Consumption logic app - Visual Studio
+          - text: Create Consumption logic app workflow - Azure portal
+            url: quickstart-create-example-consumption-workflow.md
+          - text: Create Consumption logic app workflow - Visual Studio
             url: quickstart-create-logic-apps-with-visual-studio.md
       - linkListType: get-started
         links: