Consistency edits

Author: ecfan

articles/connectors/connectors-create-api-ftp.md

@@ -278,17 +278,17 @@ Before you can use an FTP action, your workflow must already start with a trigge
 
    ![Screenshot shows Consumption workflow designer, "Get file content" action, and "File" property with "Id" entered.](./media/connectors-create-api-ftp/ftp-get-file-content-id-entered-consumption.png)
 
-1. When you're done, save your logic app workflow.
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ### [Standard](#tab/standard)
 
-The steps to add and use an FTP action differ based on whether your workflow uses an "Azure" managed connector trigger or a built-in connector trigger.
+The steps to add and use an FTP action differ based on whether your workflow uses the built-in connector or the managed, Azure-hosted connector.
 
-* [**Workflows with a built-in trigger**](#built-in-trigger-workflows): Describes the steps for workflows that start with a built-in trigger.
+* [**Built-in trigger**](#built-in-trigger-workflows): Describes the steps to add a built-in action.
 
   If you used the FTP built-in trigger, and you want the content from a newly added or updated file, you can use a **For each** loop to iterate through the array that's returned by the trigger. You can then use just the **Get file content** action without any other intermediary actions. For more information about FTP built-in connector operations, review [FTP built-in connector operations](#ftp-built-in-connector-operations) later in this article.
 
-* [**Workflows with a managed trigger**](#managed-trigger-workflows): Describes the steps for workflows that start with a managed trigger.
+* [**Managed trigger**](#managed-trigger-workflows): Describes the steps to add a managed action.
 
  If you used the FTP managed connector trigger, and want the content from a newly added or modified file, you can use a **For each** loop to iterate through the array that's returned by the trigger. You then have to use intermediary actions such as the FTP action named **Get file metadata** before you use the **Get file content** action.
 
@@ -327,7 +327,9 @@ The steps to add and use an FTP action differ based on whether your workflow use
 
    ![Screenshot shows Standard workflow designer and "Get file content" action complete.](./media/connectors-create-api-ftp/ftp-action-get-file-content-complete-built-in-standard.png)
 
-1. Add any other actions that your workflow needs. When you're done, save your logic app workflow.
+1. Add any other actions that your workflow needs. 
+
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 <a name="managed-trigger-workflows"></a>
 
@@ -384,7 +386,9 @@ The steps to add and use an FTP action differ based on whether your workflow use
 
    ![Screenshot shows Standard workflow designer, "Get file content" action, and "File" property set to "Id" action output.](./media/connectors-create-api-ftp/ftp-get-file-content-complete-azure-standard.png)
 
-1. Add any other actions that your workflow needs. When you're done, save your logic app workflow.
+1. Add any other actions that your workflow needs.
+
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ---
 

articles/connectors/connectors-create-api-servicebus.md

@@ -251,7 +251,7 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
 1. To add any other available properties to the trigger, open the **Add new parameter** list, and select the properties that you want.
 
-1. Continue building your workflow by adding the actions that you want.
+1. Add any actions that your workflow needs.
 
    For example, you can add an action that sends email when a new message arrives. When your trigger checks your queue and finds a new message, your workflow runs your selected actions for the found message.
 
@@ -307,7 +307,7 @@ The steps to add and use a Service Bus trigger differ based on whether you want
    > for events or data that meet the specified condition before running a workflow. The trigger doesn't check 
    > for events or data based on a specified schedule. For more information, review [Triggers](apis-list.md#triggers).
 
-1. Continue building your workflow by adding the actions that you want.
+1. Add any actions that your workflow needs.
 
    For example, you can add an action that sends email when a new message arrives. When your trigger checks your queue and finds a new message, your workflow runs your selected actions for the found message.
 
@@ -352,7 +352,7 @@ The steps to add and use a Service Bus trigger differ based on whether you want
 
 1. To add any other available properties to the trigger, open the **Add new parameter** list, and select the properties that you want.
 
-1. Continue building your workflow by adding the actions that you want.
+1. Add any actions that your workflow needs.
 
    For example, you can add an action that sends email when a new message arrives. When your trigger checks your queue and finds a new message, your workflow runs your selected actions for the found message.
 
@@ -405,15 +405,15 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
 1. To add any other available properties to the action, open the **Add new parameter** list, and select the properties that you want.
 
-1. Continue building your workflow by adding any other actions that you want.
+1. Add any other actions that your workflow needs.
 
    For example, you can add an action that sends email to confirm that your message was sent.
 
 1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ### [Standard](#tab/standard)
 
-The steps to add and use a Service Bus action differ based on whether you want to use the built-in connector trigger or the managed, Azure-hosted connector.
+The steps to add and use a Service Bus action differ based on whether you want to use the built-in connector or the managed, Azure-hosted connector.
 
 * [**Built-in action**](#built-in-connector-action): Describes the steps to add a built-in action.
 
@@ -458,7 +458,7 @@ The steps to add and use a Service Bus action differ based on whether you want t
 
 1. To add any other available properties to the action, open the **Add new parameter** list, and select the properties that you want.
 
-1. Continue building your workflow by adding the actions that you want.
+1. Add any other actions that your workflow needs.
 
    For example, you can add an action that sends email to confirm that your message was sent.
 
@@ -505,14 +505,38 @@ The steps to add and use a Service Bus action differ based on whether you want t
 
 1. To add any other available properties to the action, open the **Add new parameter** list, and select the properties that you want.
 
-1. Continue building your workflow by adding any other actions that you want.
+1. Add any other actions that your workflow needs.
 
    For example, you can add an action that sends email to confirm that your message was sent.
 
 1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ---
 
+<a name="built-in-connector-operations"></a>
+
+## Service Bus built-in connector operations
+
+The Service Bus built-in connector is available only for Standard logic app workflows and provides the following triggers and actions:
+
+| Trigger | Description |
+|-------- |-------------|
+| When messages are available in a queue | Start a workflow when one or more messages are available in a queue. |
+| When messages are available in a topic subscription | Start a workflow when one or more messages are available in a topic subscription. |
+
+These Service Bus triggers follow the *push trigger* pattern, which means that the trigger waits and listens for events or data that meet the specified condition before running a workflow. The trigger doesn't check for events or data based on a specified schedule. For more information, review [Triggers](apis-list.md#triggers).
+
+| Action | Description |
+|--------|-------------|
+| Send message | Send a message to a queue or topic. |
+| Send multiple messages | Send more than one message to a queue or topic. |
+
+<a name="built-in-connector-app-settings"></a>
+
+## Service Bus built-in connector app settings
+
+In a Standard logic app resource, the Service Bus built-in connector includes app settings that control various thresholds, such as timeout for sending messages and number of message senders per processor core in the message pool. For more information, review [Reference for app settings - local.settings.json](../logic-apps/edit-app-settings-host-settings.md#reference-local-settings-json).
+
 ## Troubleshooting
 
 ### Delays in updates to your workflow taking effect
@@ -539,30 +563,6 @@ The chance exists that requests might not get routed to the same role instance,
 
 As long as this error happens only occasionally, the error is expected. When the error happens, the message is still preserved in the service bus. The next trigger or workflow run tries to process the message again.
 
-<a name="built-in-connector-operations"></a>
-
-## Service Bus built-in connector operations
-
-The Service Bus built-in connector is available only for Standard logic app workflows and provides the following triggers and actions:
-
-| Trigger | Description |
-|-------- |-------------|
-| When messages are available in a queue | Start a workflow when one or more messages are available in a queue. |
-| When messages are available in a topic subscription | Start a workflow when one or more messages are available in a topic subscription. |
-
-These Service Bus triggers follow the *push trigger* pattern, which means that the trigger waits and listens for events or data that meet the specified condition before running a workflow. The trigger doesn't check for events or data based on a specified schedule. For more information, review [Triggers](apis-list.md#triggers).
-
-| Action | Description |
-|--------|-------------|
-| Send message | Send a message to a queue or topic. |
-| Send multiple messages | Send more than one message to a queue or topic. |
-
-<a name="built-in-connector-app-settings"></a>
-
-## Service Bus built-in connector app settings
-
-In a Standard logic app resource, the Service Bus built-in connector includes app settings that control various thresholds, such as timeout for sending messages and number of message senders per processor core in the message pool. For more information, review [Reference for app settings - local.settings.json](../logic-apps/edit-app-settings-host-settings.md#reference-local-settings-json).
-
 ## Next steps
 
 * [Managed connectors in Azure Logic Apps](/connectors/connector-reference/connector-reference-logicapps-connectors)

articles/connectors/connectors-create-api-sqlazure.md

@@ -125,7 +125,7 @@ The following steps use the Azure portal, but with the appropriate Azure Logic A
 
    For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server managed connector reference](/connectors/sql/).
 
-1. When you're done, save your workflow.
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ### [Standard](#tab/standard)
 
@@ -157,7 +157,7 @@ In Standard logic app workflows, only the SQL Server managed connector has trigg
 
    For example, to view the data in this row, you can add other actions that create a file that includes the fields from the returned row, and then send email alerts. To learn about other available actions for this connector, see the [SQL Server managed connector reference](/connectors/sql/).
 
-1. When you're done, save your workflow.
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ---
 
@@ -215,7 +215,7 @@ In this example, the logic app workflow starts with the [Recurrence trigger](../
 
    This action returns only one row from the selected table, and nothing else. To view the data in this row, add other actions. For example, such actions might create a file, include the fields from the returned row, and store the file in a cloud storage account. To learn about other available actions for this connector, see the [connector's reference page](/connectors/sql/).
 
-1. When you're done, save your workflow.
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ### [Standard](#tab/standard)
 
@@ -263,7 +263,7 @@ In this example, the logic app workflow starts with the [Recurrence trigger](../
 
    This action returns only one row from the selected table, and nothing else. To view the data in this row, add other actions. For example, such actions might create a file, include the fields from the returned row, and store the file in a cloud storage account. To learn about other available actions for this connector, review the [managed connector's reference page](/connectors/sql/).
 
-1. When you're done, save your workflow.
+1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
 ---