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

xuehongg · ecfan · web-flow · commit 891a0a9b13a5 · 2024-05-28T16:38:08.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
@@ -255,7 +255,7 @@ In single-tenant Azure Logic Apps, [built-in connectors with specific attributes
   > [!IMPORTANT]
   >
   > Make sure to correctly set up and test any service provider-based trigger to confirm successful operation. 
-  > service provider trigger may cause additional unnecessary scaling which may dramatically increase your billing cost. A common 
+  > 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 
   > 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
`@@ -255,7 +255,7 @@ In single-tenant Azure Logic Apps, [built-in connectors with specific attributes`
`255`	`255`	`> [!IMPORTANT]`
`256`	`256`	`>`
`257`	`257`	`> Make sure to correctly set up and test any service provider-based trigger to confirm successful operation.`
`258`		`- > service provider trigger may cause additional unnecessary scaling which may dramatically increase your billing cost. A common`
	`258`	`+ > A failed service provider-based trigger might create unnecessary scaling, which can dramatically increase your billing costs.`
`259`	`259`	`> mistake is setting a trigger without providing the logic app permission to the destination such as service bus queue or Azure`
`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.`