Update articles/logic-apps/single-tenant-overview-compare.md

xuehongg · ecfan · web-flow · commit de8e30748067 · 2024-05-28T16:38:17.000-07:00
Co-authored-by: Esther Fan &lt;ecfan@users.noreply.github.com&gt;
diff --git a/articles/logic-apps/single-tenant-overview-compare.md b/articles/logic-apps/single-tenant-overview-compare.md
@@ -256,7 +256,7 @@ In single-tenant Azure Logic Apps, [built-in connectors with specific attributes
   >
   > Make sure to correctly set up and test any service provider-based trigger to confirm successful operation. 
   > A failed service provider-based trigger might create unnecessary scaling, which can dramatically increase your billing costs. 
-  > mistake is setting a trigger without providing the logic app permission to the destination such as service bus queue or Azure 
+  > For example, a common mistake is setting a trigger without giving your logic app permission or access to the destination, 
   > storage blob container etc.  This also means such trigger needs to be monitored all the times to detect and fix any issue 
   > promptly.
 

Original file line number	Diff line number	Diff line change
`@@ -256,7 +256,7 @@ In single-tenant Azure Logic Apps, [built-in connectors with specific attributes`
`256`	`256`	`>`
`257`	`257`	`> Make sure to correctly set up and test any service provider-based trigger to confirm successful operation.`
`258`	`258`	`> A failed service provider-based trigger might create unnecessary scaling, which can dramatically increase your billing costs.`
`259`		`- > mistake is setting a trigger without providing the logic app permission to the destination such as service bus queue or Azure`
	`259`	`+ > For example, a common mistake is setting a trigger without giving your logic app permission or access to the destination,`
`260`	`260`	`> storage blob container etc. This also means such trigger needs to be monitored all the times to detect and fix any issue`
`261`	`261`	`> promptly.`
`262`	`262`