Fix Acrolinx issues

Author: ecfan

articles/logic-apps/concepts-schedule-automated-recurring-tasks-workflows.md

@@ -6,6 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
 ms.date: 02/14/2025
+# As an Azure Logic Apps developer, I want to understand how recurring schedules work for triggers.
 ---
 
 # Schedules for recurring triggers in Azure Logic Apps workflows
@@ -38,7 +39,7 @@ This guide describes the capabilities for the Schedule-type built-in triggers an
 
 ## Run recurring workloads without creating multiple logic apps
 
-You can schedule and run recurring workloads without creating a separate Consumption logic app for each scheduled job and running into the [limit on workflows per region and subscription](logic-apps-limits-and-config.md#definition-limits). Instead, you can either [create a Standard logic app with multiple workflows](create-single-tenant-workflows-azure-portal.md), or use the Consumption logic app pattern that's created by the [Azure QuickStart template: Logic Apps job scheduler](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.logic/logicapps-jobscheduler/).
+You can schedule and run recurring workloads without creating a separate Consumption logic app for each scheduled job and running into the [limit on workflows per region and subscription](logic-apps-limits-and-config.md#definition-limits). Instead, you can either [create a Standard logic app with multiple workflows](create-single-tenant-workflows-azure-portal.md), or use the Consumption logic app pattern that's created by the [Azure Quickstart Template: Logic Apps job scheduler](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.logic/logicapps-jobscheduler/).
 
 The Azure Logic Apps job scheduler template creates a logic app named **CreateTimerJob** that calls a **TimerJob** logic app. You can then call the **CreateTimerJob** logic app as an API by making an HTTP request and passing a schedule as input for the request. Each call to the **CreateTimerJob** logic app also calls the **TimerJob** logic app, which creates a new **TimerJob** instance that continuously runs based on the specified schedule or until meeting a specified limit. That way, you can run as many **TimerJob** instances as you want without worrying about workflow limits because instances aren't individual logic app workflow definitions or resources.
 
@@ -161,7 +162,7 @@ For more information, review the following documentation:
 
 ### Recurrence for managed triggers
 
-For recurring managed triggers, such as Office 365 Outlook, Outlook.com, and so on, the schedule isn't the only driver that controls execution. The time zone determines only the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior, for example:
+The schedule isn't the only driver that controls execution for recurring managed triggers such as Office 365 Outlook, Outlook.com, and so on. The time zone determines only the initial start time. Subsequent runs depend on the recurrence schedule, the last trigger execution, and other factors that might cause run times to drift or produce unexpected behavior, for example:
 
 * Whether the trigger accesses a server that has more data, which the trigger immediately tries to fetch.
 * Any failures or retries that the trigger incurs.

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

@@ -195,7 +195,7 @@ The following steps use the Azure portal, but you can also use the following too
 
 1. From the actions list, select the action that you want. If more triggers exist that aren't shown, select **See more**.
 
-1. If the **Create connection** pane appears, provide any necessary connection information, which differs based on the connector. When you're done, select **Sign in** or **Create new** to complete the connection.
+1. If the **Created connection** pane appears, provide any necessary connection information, which differs based on the connector. When you're done, select **Sign in** or **Create new** to complete the connection.
 
 1. After the action information box appears, provide the necessary details for your selected action.
 
@@ -217,37 +217,37 @@ The following Standard workflow example shows the **In-app** collections and con
 
 :::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. 
+After you select a collection or connector, triggers appear by collection or connector name.
 
-The following example selected the **Schedule** operation collection and shows the triggers named **Recurrence** and **Sliding Window**:
+The following example shows the selected **Schedule** collection and its triggers:
 
 :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-selected-connector-triggers.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app with blank stateful workflow, and Schedule operation collection with Recurrence trigger.":::
 
 The following example shows the **In-app** collections and connectors when you add an action:
 
 :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-connectors-actions-standard.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app stateful workflow with Recurrence trigger, pane named Add an action, and Runtime set to In-app.":::
 
-The following example selected the **Azure Queue Storage** connector and shows the available actions:
+The following example shows the selected **Azure Queue Storage** connector and its actions:
 
 :::image type="content" source="media/create-workflow-with-trigger-or-action/in-app-selected-connector-actions.png" alt-text="Screenshot shows Azure portal, designer for Standard logic app stateful workflow with Azure Queue Storage connector with actions.":::
 
 ### Shared (Azure) operations
 
-The following The following Standard workflow example shows the **Shared** connectors gallery when you add a trigger:
+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.":::
 
-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. 
+After you select a collection or connector, triggers appear by collection or connector name.
 
-The following example selected the **365 Training** connector and shows the available triggers:
+The following example shows the selected **365 Training** connector and its 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.":::
 
 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.":::
 
-The following example selected the **365 Training** connector and shows the available actions:
+The following example shows the selected **365 Training** connector and its 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.":::