Merge pull request #1522 from segmentio/DOC-160_adwords-clarity

DOC-160 Adwords Update

Author: markzegarelli

netlify.toml

@@ -3,10 +3,10 @@
   # Ignore builds unless [netlify-build] is present in commit message
   # ignore = "git log -1 --pretty=%B | ( ! grep -q '\[netlify\-build\]' )"
   # Ignore if [netlify-ignore] is present
-  ignore = "git log -1 --pretty=%B | ( grep -q '\\[netlify\\-ignore\\]' )"
 
 [context.deploy-preview]
   command = "yarn develop"
+  ignore = "git log -1 --pretty=%B | ( grep -q '\\[netlify\\-ignore\\]' )"
 
 [[redirects]]
   from = "/docs/*"

src/connections/destinations/catalog/adwords-remarketing-lists/index.md

@@ -33,7 +33,7 @@ If you use Segment’s mobile SDK to collect events from a mobile app, the user
 
 When you send an audience to Google Adwords Remarketing Lists, you can choose which custom matcher (email or mobile id/IDFA) to match with. If a user has multiple emails or IDFAs on their account as `external_ids`, Personas only sends Adwords the ID that was most recently added to the user profile.
 
-These audience lists can be used serve content on Google Search, YouTube, and Gmail, but are not available on the Google Display Network. You can only target users with email addresses that are associated with a Google account, and you can target users in Gmail only if they have an `@gmail.com` address. <!--For Personas audiences that are compatible with Google Display Network, see our documentation for DV360. -->
+These audience lists can be used serve content on Google Search, YouTube, and Gmail. You can only target users with email addresses that are associated with a Google account, and you can target users in Gmail only if they have an `@gmail.com` address. <!--For Personas audiences that are compatible with Google Display Network, see our documentation for DV360. -->
 
 > info ""
 > **Note**: You must have access to Personas as part of your Segment plan to use this destination. [Contact our sales team](https://segment.com/demo/) to try this out.