Apply suggestions from code review

Co-authored-by: Esther Fan <[email protected]>

Author: cdpark

articles/connectors/connectors-native-http.md

@@ -207,7 +207,7 @@ If you have a Standard logic app resource in single-tenant Azure Logic Apps, and
 
 For example, if you're working in Visual Studio Code, follow these steps:
 
-1. Open your logic app project's *local.settings.json* file.
+1. Open your logic app project's **local.settings.json** file.
 
 1. In the `Values` JSON object, add or update the `WEBSITE_LOAD_ROOT_CERTIFICATES` setting:
 
@@ -248,7 +248,7 @@ For more information, see [Manage app settings - local.settings.json](../logic-a
 
 For example, if you're working in Visual Studio Code, follow these steps:
 
-1. Open your logic app project's *local.settings.json* file.
+1. Open your logic app project's **local.settings.json** file.
 
 1. In the `Values` JSON object, add or update the `WEBSITE_LOAD_USER_PROFILE` setting:
 

articles/connectors/connectors-native-reqres.md

@@ -331,6 +331,9 @@ The **Request** trigger creates a manually callable endpoint that handles *only*
 
 1. If any other parameters exist for the trigger, open the **Advanced parameters** list, and select the parameters that you want.
 
+   
+1. If any other parameters exist for the trigger, open the **Advanced parameters** list, and select the parameters that you want.
+
 
 1. When you're ready, save your workflow. On the designer toolbar, select **Save**.
 

articles/logic-apps/edit-app-settings-host-settings.md

@@ -213,7 +213,9 @@ The following example shows the syntax for these settings where each workflow ID
 
 ### *Trigger* concurrency
 
-The following settings work only for workflows that start with a recurrence-based trigger for [built-in, service provider-based connectors](/azure/logic-apps/connectors/built-in/reference/). For a workflow that starts with a function-based trigger, you might try to [set up batching where supported](logic-apps-batch-process-send-receive-messages.md). However, batching isn't always the correct solution. For example, with Azure Service Bus triggers, a batch might hold onto messages beyond the lock duration. As a result, any action, such as complete or abandon, fails on such messages.
+The following concurrency settings apply only to workflows that start with a recurrence-based trigger for [built-in, service provider-based connectors](/azure/logic-apps/connectors/built-in/reference/) and control the number of workflows that run concurrently, or at the same time.
+
+For a workflow that starts with a function-based trigger, you might try to [set up batching where supported](logic-apps-batch-process-send-receive-messages.md). However, batching isn't always the correct solution. For example, with Azure Service Bus triggers, a batch might hold onto messages beyond the lock duration. As a result, any action, such as complete or abandon, fails on such messages.
 
 | Setting | Default value | Description |
 |---------|---------------|-------------|