UX refresh

Author: ecfan

articles/logic-apps/create-workflow-with-trigger-or-action.md

@@ -57,7 +57,7 @@ The following steps use the Azure portal, but you can also use the following too
      | **Shared** | Connectors with triggers that are Microsoft-managed, hosted, and run in multitenant Azure. In previous designer versions, this group combines the legacy **Standard** and **Enterprise** groups. |
      | **Custom** | Any connectors with triggers that you created and installed. |
 
-     The following example shows the designer for a Consumption logic app with a blank workflow and shows the **In-app** runtime selected. The list shows the available operation collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=consumption#connectors-triggers-actions-designer).
+     The following example shows the designer for a Consumption logic app with a blank workflow and shows the **In-app** runtime selected. The list shows the available collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=consumption#connectors-triggers-actions-designer).
 
      :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-consumption.png" alt-text="Screenshot shows Azure portal, Consumption workflow designer, pane named Add a trigger, and Runtime set to In-app." lightbox="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-consumption.png":::
 
@@ -95,7 +95,7 @@ The following steps use the Azure portal, but you can also use the following too
      | **Shared** | For stateful workflows only, connectors with triggers that are Microsoft-managed, hosted, and run in multitenant Azure. In previous designer versions, this group is the same as the **Azure** group. |
      | **Custom** | Any connectors with triggers that you created and installed. |
 
-     The following example shows the designer for a Standard logic app with a blank workflow and shows the **In-app** runtime selected. The list shows the available operation collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
+     The following example shows the designer for a Standard logic app with a blank workflow and shows the **In-app** runtime selected. The list shows the available collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
 
      :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-standard.png" alt-text="Screenshot shows Azure portal, Standard workflow designer, pane named Add a trigger, and Runtime set to In-app." lightbox="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-standard.png":::
 
@@ -143,7 +143,7 @@ The following steps use the Azure portal, but you can also use the following too
      | **Shared** | Connectors with actions that are Microsoft-managed, hosted, and run in multitenant Azure. In previous designer versions, this group combines the legacy **Standard** and **Enterprise** groups. |
      | **Custom** | Any connectors with actions that you created and installed. |
 
-     The following example shows the designer for a Consumption logic app workflow with an existing trigger and shows the **In-app** runtime selected. The list shows the available operation collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=consumption#connectors-triggers-actions-designer).
+     The following example shows the designer for a Consumption logic app workflow with an existing trigger and shows the **In-app** runtime selected. The list shows the available collections, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=consumption#connectors-triggers-actions-designer).
 
      :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-actions-consumption.png" alt-text="Screenshot shows Azure portal, designer for Consumption workflow with existing trigger, pane named Add an action, and Runtime set to In-app." lightbox="media/create-workflow-with-trigger-or-action/in-app-connectors-actions-consumption.png":::
 
@@ -185,11 +185,11 @@ The following steps use the Azure portal, but you can also use the following too
      | **Shared** | For stateful workflows only, connectors with actions that are Microsoft-managed, hosted, and run in multitenant Azure. In previous designer versions, this group is the same as the **Azure** group. |
      | **Custom** | Any connectors with actions that you created and installed. |
 
-     The following example shows the designer for a Standard workflow with an existing trigger and shows the **In-app** group selected. The list shows the available operation collections and connectors, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
+     The following example shows the designer for a Standard workflow with an existing trigger and shows the **In-app** group selected. The list shows the available collections and connectors, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
 
      :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-actions-standard.png" alt-text="Screenshot showing Azure portal, the designer for Standard logic app workflow with a trigger, and In-app connectors with actions gallery.":::
 
-     The following example shows the designer for a Standard workflow with an existing trigger and shows the **Shared** group selected. The list shows the available operation collections and connectors, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
+     The following example shows the designer for a Standard workflow with an existing trigger and shows the **Shared** group selected. The list shows the available collections and connectors, which appear in a [specific order](create-workflow-with-trigger-or-action.md?tabs=standard#connectors-triggers-actions-designer).
 
      :::image type="content" source="media/create-workflow-with-trigger-or-action/shared-connectors-actions-standard.png" alt-text="Screenshot showing Azure portal, the designer for Standard logic app workflow with a trigger, and Shared connectors with actions gallery.":::
 
@@ -213,9 +213,9 @@ When the **Add a trigger** or **Add an action** pane opens, the gallery lists th
 
 ### In-app (built-in) operations
 
-The following example shows the **In-app** operation collections and connectors when you add a trigger:
+The following Standard workflow example shows the **In-app** collections and connectors when you add a trigger:
 
-:::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app with blank stateful workflow, and In-app operation collections and connectors.":::
+:::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-triggers-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app with blank stateful workflow, and In-app collections and connectors.":::
 
 After you select a collection or connector, the individual triggers are grouped by collection or connector name and appear in ascending order, first numerically if any exist, and then alphabetically. 
 
@@ -233,23 +233,23 @@ The following example selected the **Azure Queue Storage** connector and shows t
 
 ### Shared (Azure) operations
 
-The following example shows the **Shared** connectors gallery when you add a trigger:
+The following The following Standard workflow example shows the **Shared** connectors gallery when you add a trigger:
 
-:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-connectors-triggers-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app with blank stateful workflow, and Shared connectors with triggers." lightbox="media/create-workflow-with-trigger-or-action/shared-connectors-triggers-standard.png":::
+:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-connectors-triggers-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app with blank stateful workflow, and Shared connectors with triggers.":::
 
 After you select a collection or connector, the individual triggers are grouped by collection or connector name and appear in ascending order, first numerically if any exist, and then alphabetically. 
 
 The following example selected the **365 Training** connector and shows the available triggers:
 
-:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-selected-connector-triggers.png" alt-text="Screenshot shows Azure portal, workflow designer, and 365 Training connector with triggers." lightbox="media/create-workflow-with-trigger-or-action/shared-selected-connector-triggers.png":::
+:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-selected-connector-triggers.png" alt-text="Screenshot shows Azure portal, workflow designer, and 365 Training connector with triggers.":::
 
 The following example shows the **Shared** connectors gallery when you add an action:
 
-:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-connectors-actions-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app stateful workflow, and Shared connectors with actions." lightbox="media/create-workflow-with-trigger-or-action/shared-connectors-actions-standard.png":::
+:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-connectors-actions-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app stateful workflow, and Shared connectors with actions.":::
 
 The following example selected the **365 Training** connector and shows the available actions:
 
-:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-selected-connector-actions.png" alt-text="Screenshot shows Azure portal, workflow designer, and 365 Training connector with actions." lightbox="media/create-workflow-with-trigger-or-action/shared-selected-connector-actions.png":::
+:::image type="content" source="media/create-workflow-with-trigger-or-action/shared-selected-connector-actions.png" alt-text="Screenshot shows Azure portal, workflow designer, and 365 Training connector with actions.":::
 
 For more information, see the following documentation: