Streamline and clarity edits

mwsteb · Jun 16, 2020 · 47851e0 · 47851e0
1 parent 0c1423e
commit 47851e0
Showing 1 changed file with 5 additions and 3 deletions.
diff --git a/articles/connectors/connectors-google-data-security-privacy-policy.md b/articles/connectors/connectors-google-data-security-privacy-policy.md
@@ -39,15 +39,17 @@ Under this policy, when you use a Gmail consumer account, you can use the Gmail
 
 ## Non-compliant examples
 
-* This logic app uses the Gmail connector with the HTTP built-in trigger, which isn't approved by Google:
+Here are some examples that use the Gmail connector with built-in triggers and actions or managed connectors that aren't approved by Google:
+
+* This logic app uses the Gmail connector with the HTTP built-in trigger:
 
   ![Non-compliant logic app - Example 1](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-1.png)
 
-* This logic app uses the Gmail connector with the Azure Blob Storage connector, which isn't approved by Google:
+* This logic app uses the Gmail connector with the Azure Blob Storage connector:
 
   ![Non-compliant logic app - Example 2](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-2.png)
 
-* This logic app uses the Gmail connector with the Twitter connector, which isn't approved by Google:
+* This logic app uses the Gmail connector with the Twitter connector:
 
   ![Non-compliant logic app - Example 3](./media/connectors-google-data-security-privacy-policy/not-compliant-logic-app-3.png)