Update articles/connectors/connectors-native-reqres.md

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

Author: xuehongg

articles/connectors/connectors-native-reqres.md

@@ -375,7 +375,7 @@ Now, continue building your workflow by adding another action as the next step.
 > Your workflow keeps an inbound request open only for a [limited time](../logic-apps/logic-apps-limits-and-config.md#http-limits). 
 > Assuming that your workflow includes a **Response** action with the **Asynchronous response** setting turned off (default), if your workflow 
 > doesn't return a response to the caller after this time expires, your workflow returns the **504 GATEWAY TIMEOUT** status to the caller. 
-> If your workflow doesn't include a Response action or the Response action has "Asynchronous response" setting turned on, your workflow 
+> If the **Response** action has the **Asynchronous response** setting turned on, or if your workflow doesn't include a **Response** action, your workflow 
 > immediately returns the **202 ACCEPTED** status to the caller.
 
 For information about security, authentication, and encryption for inbound calls to your workflow, such as [Transport Layer Security (TLS)](https://en.wikipedia.org/wiki/Transport_Layer_Security), [OAuth with Microsoft Entra ID](/entra/architecture/auth-oauth2), [Shared Access Signatures (SAS)](../logic-apps/logic-apps-securing-a-logic-app.md#sas), exposing your logic app resource with Azure API Management, or restricting the IP addresses that originate inbound calls, see [Access for inbound calls to request-based triggers](../logic-apps/logic-apps-securing-a-logic-app.md#secure-inbound-requests).