Updated per feedback

ecfan · web-flow · commit 20a858b6b0e2 · 2023-03-28T17:02:01.000-07:00
diff --git a/articles/logic-apps/logic-apps-limits-and-config.md b/articles/logic-apps/logic-apps-limits-and-config.md
@@ -530,8 +530,8 @@ For Azure Logic Apps to receive incoming communication through your firewall, yo
 
 > [!NOTE]
 > 
-> Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use role-based access control 
-> on the logic app resource, you must make sure that the calls from these target systems (IP addresses) have permissions 
+> Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use access control (IAM) on 
+> the logic app resource, you must make sure that the calls from these target systems (IP addresses) have permissions 
 > to access your logic app. The following connectors make inbound webhook callbacks to Azure Logic Apps:
 >
 > Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Microsoft Sentinel, Event Grid, 

Original file line number	Diff line number	Diff line change
`@@ -530,8 +530,8 @@ For Azure Logic Apps to receive incoming communication through your firewall, yo`
`530`	`530`
`531`	`531`	`> [!NOTE]`
`532`	`532`	`>`
`533`		`-> Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use role-based access control`
`534`		`-> on the logic app resource, you must make sure that the calls from these target systems (IP addresses) have permissions`
	`533`	`+> Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use access control (IAM) on`
	`534`	`+> the logic app resource, you must make sure that the calls from these target systems (IP addresses) have permissions`
`535`	`535`	`> to access your logic app. The following connectors make inbound webhook callbacks to Azure Logic Apps:`
`536`	`536`	`>`
`537`	`537`	`> Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Microsoft Sentinel, Event Grid,`