q's/updates from content office hours

Author: forstisabella

src/_data/sidenav/main.yml

@@ -452,8 +452,8 @@ sections:
       title: Consent Management Overview
     - path: /privacy/configure-consent-management
       title: Configure Consent Management
-    - path: /privacy/enforce-consent
-      title: Enforce Consent Management
+    - path: /privacy/reconcile-consent
+      title: Reconcile Consent Conflicts
   - path: /privacy/account-deletion
     title: Account & Data Deletion
   - path: /privacy/hipaa-eligible-segment

src/privacy/configure-consent-management.md

@@ -13,19 +13,32 @@ Before you can configure consent in Segment, you'll need to take the following s
 - **Know how your company maps each destination**. You'll need to know which destinations map to each categories. 
 - **Update your web libraries with the consent object**. To ensure Segment is receiving your end-user consent preferences, you'll need access to your web libraries so you can include the consent object to every event.
 
+<!-- Ask Aaron about consent object order of ops/can it be tested??? Can you undo or pause this?? -->
+
 > error "After adding the consent object to your events, your data is immediately impacted"
 > If you disable a consent category, events are not sent to mapped destinations.
 >  
-> If a destination is mapped to multiple categories, and the end user has conflicted preferences, data will be sent to the destination.
+> If a destination is mapped to multiple categories, and the end user has conflicting preferences, data will be sent to the destination.
 > 
 > If Segment receives an API call with both an integrations object and a consent object, the consent object takes preference.
 
-## Step 1: Access the Consent Management feature
+<!-- does this need to be added to multiple pages-->
+
+## Step 1: Create consent categories
+
+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, click **Get started**.
+3. 
+
+
+<br/>
+> warning "Segment recommends mapping all destinations to a category"
+> Any destination that doesn't have a mapping won't receive events with a consent object. 
+
+<!-- does it get backfilled???--->
 
-## Step 2: Create consent categories 
+## Step 2: 
 
-> info "Segment recommends mapping all destinations to a category"
-> Each destination should be mapped to a category <!---why though?---> to ensure completeness of data in your downstream destinations. Any destination that doesn't have a mapping will not receive events with a consent object. 
 
 ## Step 3: 
 

src/privacy/enforce-consent.md renamed to src/privacy/reconcile-consent.md

@@ -1,5 +1,5 @@
 ---
-title: Enforce Consent
+title: Reconciling Consent Conflicts
 ---
 
 Segment sends data only to destinations in categories consented to by the end user. When conflicts arise between the consent object and integrations object or your consent management tool, Segment reconciles consent according to the following tables.
@@ -11,15 +11,28 @@ Segment sends data only to destinations in categories consented to by the end us
 
 Segment detects when there are conflicting consent categories for a user and 
 
+<!--- ask Emma about table/edge cases --->
+
+## Reconcile a user's conflicting preferences
+
+If a user has conflicting preferences (for example, they consented yes for a category on mobile, but not on the web, or consented differently using two different emails,) Segment routes data according to the following table:
+
+| Category | Consent on mobile | Consent on the web |
+| -------- | ----------------- | ------------------ | 
+
+<!--- can you treat mobile/web data differently? -->
+
 ## Reconcile consent object and integrations object conflicts
 
-You can add the integrations object and the consent object to your Segment payloads to control how Segment routes data to your downstream destination. 
+You can add the integrations object and the consent object to your Segment payloads to control how Segment routes data to your downstream destinations. 
 
 > success " "
 > For more information about the Integrations object, please see [Filtering your Segment Data](/docs/guides/filtering-data/#filtering-with-the-integrations-object).
 
 If the consent object and integrations object have conflicting destination information, Segment routes data according to the following table:
 
+<!-- ask Atit if consent object takes precedence over integrations object, except if specifically called out in Integrations object-->
+
 | Consent Object                                                                                                  | Integration Object                          | Result |
 | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | ------ |
 | Not provided or empty object                                                                                    | Not provided or empty object                | Message delivered to all enabled destinations |