Update articles/logic-apps/logic-apps-limits-and-config.md

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

Author: xuehongg

articles/logic-apps/logic-apps-limits-and-config.md

@@ -414,7 +414,7 @@ For Standard logic app resources in single-tenant Azure Logic Apps, stateless wo
 | Name | Multitenant | Single-tenant | Notes |
 |------|-------------|---------------|-------|
 | Outbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of outbound requests include calls made by the HTTP trigger or action. If the server doesn't respond within the timeout limit, the HTTP action fails. <br><br>**Tip**: For longer running operations, use an [asynchronous polling pattern](logic-apps-create-api-app.md#async-pattern) or an ["Until" loop](logic-apps-workflow-actions-triggers.md#until-action). To work around timeout limits when you call another workflow that has a [callable endpoint](logic-apps-http-endpoint.md), you can use the built-in Azure Logic Apps action instead, which you can find in the designer's operation picker under **Built-in**. <br><br>To change the default timeout limit in the single-tenant service, follow these steps in the Azure portal or see [Edit host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md): <br><br>1. On the designer, in the workflow, select the **HTTP** action. <br>2. In the action pane, select the **Settings** tab. <br>3. Under **Request options - Timeout**, change the duration. |
-| Inbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of inbound requests include calls received by the Request trigger, HTTP Webhook trigger, and HTTP Webhook action. <br><br>**Note**: For the original caller to get the response, all steps in the response must finish within the limit if the Response action has "Asynchronous response" setting off. If the Response action has "Asynchronous response" setting turned on or there is no Response action in the workflow, the call pattern is asynchronous and the workflow can take as long as it needs. |
+| Inbound request | 120 sec <br>(2 min) | 225 sec <br>(3 min and 45 seconds) <br>(Default) | Examples of inbound requests include calls received by the **Request** trigger, **HTTP Webhook** trigger, and **HTTP Webhook** action. <br><br>**Note**: For the original caller to get the response when the **Response** action has the **Asynchronous response** setting turned off (default), all steps in the response must finish within the time limit. Otherwise, if the **Response** action has the **Asynchronous response** setting turned on, or if your workflow doesn't include a **Response** action, the call pattern is asynchronous. Your workflow can take whatever time is needed to respond. |
 
 <a name="content-storage-size-limits"></a>