[netlify-build]

Author: stayseesong

src/connections/destinations/destination-filters.md

@@ -20,20 +20,21 @@ Common use cases for destination filters include:
 
 ### Limitations
 
-Keep the following limitations in mind when you use Destination Filters:
+Keep the following limitations in mind when you use destination filters:
 
-- Segment applies Destination Filters one at a time in the order that they appear in your workspace.
-- You can't apply Destination Filters to Warehouses or S3 destinations.
+- Segment applies destination filters one at a time in the order that they appear in your workspace.
+- You can't apply destination filters to Warehouses or S3 destinations.
 - Each filter can only apply to one source-destination pair.
 - *(For device-mode)* Destination filters don't apply to items that are added to the payload server-side such as IP addresses.
 - *(For device-mode)* Destination filters don't filter on native events that the destination SDK collects. Instead, you can use the load option to conditionally load relevant bundled JavaScript on the page. See the docs for [load options](/docs/connections/sources/catalog/libraries/website/javascript/#load-options).
+- *(For device-mode)* Destination filters don't filter some fields that are collected by the destination SDK outside of Segment such as `page.url` and `page.referrer`.
 - *(For web device-mode)* Destination filters for web device-mode only supports the Analytics.js 2.0 source. You need to enable device mode destination filters for your Analytics.js source. To do this, go to your Javascript source and navigate to **Settings > Analytics.js** and turn the toggle on for **Destination Filters**.
 
 [Contact Segment](https://segment.com/help/contact/){:target="_blank"} if these limitations impact your use case.
 
 ## Create a destination filter
 
-To create a Destination Filter:
+To create a destination filter:
 1. Go to **Connections > Destinations** and select your destination.
 2. Click on the **Filters** tab of your destination.
 3. Click **+ New Filter**.
@@ -45,9 +46,9 @@ To create a Destination Filter:
 
 ## Destination filters API
 
-The Destination Filters API provides more power than Segment's dashboard Destination Filters settings. With the API, you can create complex filters that are conditionally applied using Segment's [Filter Query Language (FQL)](/docs/api/config-api/fql/).
+The destination filters API provides more power than Segment's dashboard destination filters settings. With the API, you can create complex filters that are conditionally applied using Segment's [Filter Query Language (FQL)](/docs/api/config-api/fql/).
 
-The Destination Filters API offers four different filter types:
+The destination filters API offers four different filter types:
 
 | Filter             | Details                                                      |
 | ------------------ | ------------------------------------------------------------ |
@@ -60,7 +61,7 @@ To learn more, read Segment's [Destination Filters API docs](https://docs.segmen
 
 ## Examples
 
-The following examples illustrate common Destinations Filters use cases:
+The following examples illustrate common destinations filters use cases:
 * [PII management](#pii-management)
 * [Control event volume](#control-event-volume)
 * [Cleaner data](#cleaner-data)
@@ -72,7 +73,7 @@ The following examples illustrate common Destinations Filters use cases:
 
 Example: Remove email addresses from `context` and `properties`:
 
-Property-level allowlisting is available with Segment's API. Using Destination Filters, you can configure a rule that removes email addresses from `context` and `properties`. As a result, Segment only sends traits without PII to the destination.
+Property-level allowlisting is available with Segment's API. Using destination filters, you can configure a rule that removes email addresses from `context` and `properties`. As a result, Segment only sends traits without PII to the destination.
 
 
 ![PII management example](images/destination-filters/pii_example.png)
@@ -101,31 +102,31 @@ In the example below, the rule prevents an event from sending if `Order Complete
 
 ### Sample a percentage of events
 
-Using the [Destination Filters API](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
+Using the [destination filters API](https://docs.segmentapis.com/tag/Destination-Filters){:target="_blank"}, you can create a rule to randomly sample video heartbeat events.
 
 ### Drop events
 
-[Watch this Destination Filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco){:target="_blank"} to learn how to use event names to filter events sent to destinations.
+[Watch this destination filters walkthrough](https://www.youtube.com/watch?v=47dhAF1Hoco){:target="_blank"} to learn how to use event names to filter events sent to destinations.
 
 ## Important notes
 
 #### Conflicting settings
 
-Some destinations offer settings that also allow you to filter data. For example, the Facebook App Events destination allows you to map `Screen` events to `Track` events. Because Destination Filters are evaluated and applied _before_ the Destination settings are applied, they can conflict with your settings.
+Some destinations offer settings that also allow you to filter data. For example, the Facebook App Events destination allows you to map `Screen` events to `Track` events. Because destination filters are evaluated and applied _before_ the destination settings are applied, they can conflict with your settings.
 
-For example, if you have a Destination Filter that filters Track events _and_ you have the **Use Screen Events as Track Events** setting enabled, `Track` events drop, but `Screen` events still process. The destination settings transform it into a `Track` event - *after* the filters.
+For example, if you have a destination filter that filters Track events _and_ you have the **Use Screen Events as Track Events** setting enabled, `Track` events drop, but `Screen` events still process. The destination settings transform it into a `Track` event - *after* the filters.
 
 #### Error handling
 
-Segment makes effort to ensure that Destination Filters can handle unexpected situations. For example, if you use the `contains()` FQL function on the `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
+Segment makes effort to ensure that destination filters can handle unexpected situations. For example, if you use the `contains()` FQL function on the `null` field, Segment returns `false` instead of returning an error. If Segment can't infer your intent, Segment logs an internal error and drops the event. Segment defaults to this behavior to prevent sensitive information, like a PII filter, from getting through.
 
 Errors aren't exposed in your Destination's Event Deliverability tab. For help diagnosing missing destination filter events, [contact Segment](https://segment.com/help/contact/){:target="_blank"}.
 
 ## FAQs
 
-#### How do Destination Filters work with array properties?
+#### How do destination filters work with array properties?
 
-Destination Filters can filter properties out of objects nested in an array. For example, you can filter out the `price` property of every object in an array at `properties.products`. You can also filter out an entire array from the payload. However, you can't drop nested objects in an array or filter properties out of a single object in an array.
+Destination filters can filter properties out of objects nested in an array. For example, you can filter out the `price` property of every object in an array at `properties.products`. You can also filter out an entire array from the payload. However, you can't drop nested objects in an array or filter properties out of a single object in an array.
 
 To block a specific property from all of the objects within a properties array, set the filter using the following the format: `<propertyType>.<arrayName>.<arrayElementLabel>​`.
 
@@ -141,7 +142,7 @@ Segment supports 10 filters per destination. If you need help consolidating filt
 
 #### Can I set multiple `Only Send` destination filters?
 
-Segment evaluates multiple `Only Send` filters against each other and resolves Destination Filters in order. If multiple `Only Send` filters conflict with each other, Segment won't send information downstream.
+Segment evaluates multiple `Only Send` filters against each other and resolves destination filters in order. If multiple `Only Send` filters conflict with each other, Segment won't send information downstream.
 
 #### How many properties can I view in the filter dropdown?
 
@@ -155,14 +156,14 @@ To filter out events from warehouses, use Selective Sync.
 
 Generally, only Track calls have *name* properties, which correspond to the *event* field in an event.
 
-#### How can I find out when new Destination Filters have been added or removed?
+#### How can I find out when new destination filters have been added or removed?
 
-The Activity Feed shows the action, date, and user who performed the action when a Destination Filter is created, modified, enabled, disabled, or deleted. You can also subscribe to notifications for any of these changes in the **Activity Feed** settings page.
+The Activity Feed shows the action, date, and user who performed the action when a destination filter is created, modified, enabled, disabled, or deleted. You can also subscribe to notifications for any of these changes in the **Activity Feed** settings page.
 
 #### Why am I getting a permissions denied error when I try to save a filter?
 
 You must have write access to save and edit filters. Read permission access only allows viewing and testing access.
 
 #### How can I test my filter?
 
-Use the Destination Filter tester during setup to verify that you're filtering out the right events. Filtered events show up on the schema page but aren't counted in event deliverability graphs.
+Use the destination filter tester during setup to verify that you're filtering out the right events. Filtered events show up on the schema page but aren't counted in event deliverability graphs.