[netlify-build]

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -79,9 +79,6 @@ oneTrust(analytics)
 analytics.load({ writeKey: '<MY_WRITE_KEY'> })
 ```
 
-> warning "Events may be generated while the Analytics.js SDK loads"
-> Any events generated before the Analytics.js SDK is fully loaded may be lost.
-
 ## Edit consent categories
 
 If you need to make changes to your consent categories, you can edit them on the Consent Management page. 
@@ -93,17 +90,8 @@ If you need to make changes to your consent categories, you can edit them on the
 
 ## Disable consent categories
 
-Disabling a consent category means that Segment no longer enforces end user consent preferences for the destinations in the disabled category. Other consent categories are not affected. You can't delete a category. 
+Disabling a consent category means that Segment no longer enforces end user consent preferences for the destinations in the disabled category. Other consent categories are not affected.  
 
 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,
-
-<!--- Fix this section when it no longer throws an error --->
-
-## Consent Observability
-
-<!--- You can view consent preference events in your [Tracking Plan](/docs/protocols/tracking-plan/create/) and view discarded events in [Delivery Overview](/docs/connections/delivery-overview/). ---> 
-<!---### Tracking Plan
-### Delivery Overview
-out of current scope--->
-Events discarded due to consent preferences appear in [Delivery Overview](/docs/connections/delivery-overview/) at the "Filtered at destination" step with the discard reason `Filtered by end user consent`.
+2. On the Consent Management page, disable the toggle for the category you'd like to disable. 
+3. On the "Disable [category-name]?" popup, enter the category name in the Consent category name field and click **Disable category**.

src/privacy/consent-management.md

@@ -10,7 +10,7 @@ related:
 
 When an end user visits your site, they set **consent preferences**, or make decisions about the types of data they want you to collect, use, and share. These consent preferences are typically presented as a set list of categories that describe how your company intends to use that data. Common categories include personalization, advertising, and site performance.
 
-Segment works with your third-party consent management platform (CMP) or bespoke consent solution to capture an end user's consent preferences and enforce those preferences by routing events to the categories consented to by an end user. 
+Segment works with your third-party consent management platform (CMP) or bespoke consent solution to capture an end user's consent preferences and enforce those preferences by only routing events to the categories consented to by an end user. 
 
 ![Diagram outlining information flowing from an end user to Segment destinations](/docs/privacy/images/consent-overview.png)
 
@@ -21,7 +21,7 @@ After a user sets their consent preferences, Segment captures them with the [Ana
 
 If a user changes the categories they consent to or if they consent using a different device or identifier, any events they generate after updating their consent preferences will contain the updated consent information. 
 
-For example, if a user agreed to share their information with you for all categories on their first visit to your site, and then on their next visit to the site only consented to sharing data for functional and advertising purposes but not for analytics or data sharing, a [Track call](/docs/connections/spec/track/) demonstrating their new consent preferences would have the following format:
+<!--- out of scope for Q2: For example, if a user agreed to share their information with you for all categories on their first visit to your site, and then on their next visit to the site only consented to sharing data for functional and advertising purposes but not for analytics or data sharing, a [Track call](/docs/connections/spec/track/) demonstrating their new consent preferences would have the following format:
 
 ``` json
 {
@@ -52,6 +52,8 @@ For example, if a user agreed to share their information with you for all catego
 >
 > See the [Semantic Events](/docs/connections/spec/semantic/) docs for more details.
 
+--->
+
 To learn more about configuring consent categories in your workspace, see the [Configure Consent Management documentation](/docs/src/privacy/configure-consent-management).
 
 ## Consent object
@@ -96,4 +98,4 @@ If the consent object and integrations object have conflicting destination infor
 <!---### Tracking Plan
 ### Delivery Overview
 out of current scope--->
-Events discarded due to consent preferences appear in [Delivery Overview](/docs/connections/delivery-overview/) at the "Filtered at destination" step with the discard reason `Filtered by end user consent`.
+Events discarded due to consent preferences appear in [Delivery Overview](/docs/connections/delivery-overview/) at the "Filtered at destination" step with the discard reason __Filtered by end user consent__.