Add DO note, info about dropped events

Author: forstisabella

src/connections/delivery-overview.md

@@ -23,7 +23,7 @@ The pipeline view shows the following steps:
 - **Successfully received**: Events that Segment ingested from your source
 - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
 - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) tracking plans
-- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). Actions destinations also have a filtering capability: for example, if your action is set to only send Identify events, all other event types will be filtered out.
+- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). Actions destinations also have a filtering capability: for example, if your action is set to only send Identify events, all other event types will be filtered out. Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.
 - **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
 - **Successful delivery**: Events that were successfully delivered to the destination
 

src/privacy/configure-consent-management.md

@@ -130,11 +130,23 @@ analytics.load({ writeKey: '<MY_WRITE_KEY'> })
 
 1. 
 
-## Editing consent categories
+## Edit consent categories
 
 If you need to make changes to your consent categories, you can edit them on the Consent Management page. 
 
 1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
 2. On the Consent Management page, navigate to the consent category you'd like to edit and click **Edit**.
 3. On the Edit consent category page, you can make changes to the consent category name, ID, and the destinations connected to a category.
-4. When you have made your changes, click **Save**. 
+4. When you have made your changes, click **Save**.
+
+## View discarded events
+
+You can view events that were discarded due to consent preferences in your [Tracking Plan](/docs/protocols/tracking-plan/create/) and in [Delivery Overview](/docs/connections/delivery-overview/). 
+
+### Tracking Plan
+
+<!-- ask for more context on this. "Events that are discarded due to consent preferences are surfaced in Protocols as a new Tracking Plan. While you can edit this Tracking Plan, Segment recommends leaving it intact" <!---why??--->
+
+### Delivery Overview
+
+Events discarded due to consent preferences appear in Delivery Overview at the "Filtered at destination" step with the discard reason "Filtered by end user consent".