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

xuehongg · ecfan · web-flow · commit 6fd9c246545e · 2022-08-29T15:19:52.000-07:00
Co-authored-by: Esther Fan &lt;ecfan@users.noreply.github.com&gt;
diff --git a/articles/connectors/connectors-native-reqres.md b/articles/connectors/connectors-native-reqres.md
@@ -419,7 +419,7 @@ When you use the Request trigger to receive inbound requests, you can model the
 > processes at least one Response action during runtime. Otherwise, if all Response actions are skipped, 
 > the caller receives a **502 Bad Gateway** error, even if the workflow finishes successfully.
 >
-> * In a Standard logic app **stateless** workflow, the Response action must appear last in your workflow. If the action appears 
+> * In a Standard logic app *stateless* workflow, the Response action must appear last in your workflow. If the action appears 
 > anywhere else, Azure Logic Apps still won't run the action until all other actions finish running.
 
 

Original file line number	Diff line number	Diff line change
`@@ -419,7 +419,7 @@ When you use the Request trigger to receive inbound requests, you can model the`
`419`	`419`	`> processes at least one Response action during runtime. Otherwise, if all Response actions are skipped,`
`420`	`420`	`> the caller receives a 502 Bad Gateway error, even if the workflow finishes successfully.`
`421`	`421`	`>`
`422`		`-> * In a Standard logic app stateless workflow, the Response action must appear last in your workflow. If the action appears`
	`422`	`+> * In a Standard logic app stateless workflow, the Response action must appear last in your workflow. If the action appears`
`423`	`423`	`> anywhere else, Azure Logic Apps still won't run the action until all other actions finish running.`
`424`	`424`
`425`	`425`