some more changes

Author: pwseg

src/guides/filtering-data.md

@@ -36,14 +36,15 @@ You can use the `integrations` JSON object as part of your Segment payloads to c
 }
 ```
 
-By *default*, the `integrations` object is set to `'All': true`. You do not need to include this flag in the object to use this behavior, but if you'll be using the integrations object frequently to control destination filtering, you might want to do this to make it explicit for later readers. Change this to `'All': false` to prevent any downstream destinations from receiving data, not including data warehouses. If you set `'Segment.io': false` in the integrations object, Analytics.js 2.0 drops the event before it reaches your Source Debugger. You can also add destinations to the object by key, and provide a `true` or `false` value to allow or disallow data to flow to them on an individual basis. The Destination Info box at the top of each destination page lets you know how to refer to each destination in the Integrations object. 
+By default the `integrations` object is set to `'All': true`. You don’t need to include this flag in the object, but if you’ll be using the Integrations object frequently, you might want to include it for clarity. Change this to `'All': false` to block data from all downstream destinations, except data warehouses. 
 
-If you are using [multiple instances of a destination](/docs/connections/destinations/add-destination/#connecting-one-source-to-multiple-instances-of-a-destination), any settings you set in the integrations object are applied to all instances of the destination. You cannot specify an instance of a destination to apply Integrations object settings to. 
+If you set `'Segment.io': false` in the `integrations` object, Analytics.js 2.0 drops the event before it reaches your [Source Debugger](/docs/connections/sources/debugger/). You can also add destinations by key and set their value to `true` or `false` to allow or block data on an individual basis. The Destination Info box on each destination page shows the exact name to use in the object. 
 
-Note that destination flags are **case sensitive** and match the destination's name in the docs (for example, "AdLearn Open Platform", "awe.sm", or "MailChimp").
+If you’re using [multiple instances of a destination](/docs/connections/destinations/add-destination/#connecting-one-source-to-multiple-instances-of-a-destination), any settings in the Integrations object apply to all instances. You can’t configure them separately.  
 
-The syntax to filter data to a data warehouse is different. Refer to the [Warehouse FAQs](/docs/connections/storage/warehouses/faq/#can-i-selectively-filter-dataevents-sent-to-my-warehouse-based-on-a-property) for more details.
+Destination flags are case sensitive and must match the destination’s name in the docs (for example, “AdLearn Open Platform,” “awe.sm,” or “MailChimp”).  
 
+Filtering data for warehouses uses a different syntax. See the [Warehouse FAQs](/docs/connections/storage/warehouses/faq/#can-i-selectively-filter-dataevents-sent-to-my-warehouse-based-on-a-property) for details.
 
 ## Destination filters