editing pass

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -8,10 +8,10 @@ title: Configure Consent Management
 
 ## Prerequisites
 
-Before you can configure consent in Segment, you'll need to take the following steps:
-- **Access your consent management tool and set up consent categories**. You'll need a list of your consent categories and the key or ID associated with each topic.
-- **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.
+Before you can configure consent in Segment, take the following steps:
+- **Access your consent management tool and set up consent categories**. You need a list of your consent categories and the key or ID associated with each topic.
+- **Know how your company maps each destination**. You need to know which destinations map to which categories. 
+- **Update your web libraries with the consent object**. You need access to your web libraries so you can include the consent object in every event.
 
 <!-- Ask Aaron about consent object order of ops/can it be tested??? Can you undo or pause this?? -->
 
@@ -29,6 +29,8 @@ Before you can configure consent in Segment, you'll need to take the following s
 > warning "You can map website sources and event streaming destinations to consent categories during the private beta"
 > All other sources and destinations are not affected by consent mappings.
 
+<!-- Add note that category ID is case sensitive--->
+
 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. 
@@ -38,7 +40,6 @@ Before you can configure consent in Segment, you'll need to take the following s
 > 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: 
 

src/privacy/consent-management.md

@@ -7,18 +7,18 @@ related:
 > info "Consent Management is currently in private beta"
 > This means that the Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
-Segment works with your third party consent management platform to collect the categories an end user consents to, map each of your Segment destinations to a consent category, and route events only to the categories consented to by a user.
+Segment works with your third party consent management platform to capture the categories consented to by an end user, map each of your Segment destinations to a consent category, and route events only to the appropriate categories.
 
-![Diagram outlining information flowing from an end user to Segment destinations](src/privacy/images/consent-overview.png)
+![Diagram outlining information flowing from an end user to Segment destinations](/docs/privacy/images/consent-overview.png)
 
 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.
 
-After a user sets their consent preferences, Segment updates the [consent object](#consent-object) with a user's preferences. The events are then sent downstream to any destinations in categories that a user consents to sharing data with.
+After a user sets their consent preferences, Segment updates the [consent object](#consent-object) with a user's preferences. The events are then sent downstream to any destinations in categories that a user consented to share data with.
 
 > success ""
 > Segment collects consent for both registered users and anonymous users.
 
-If a user changes the categories they consent to or if they consent using a different device or identifier, Segment sends the information about their consent, using a [Track call](docs/connections/spec/track), to your downstream destinations and storage destinations.
+If a user changes the categories they consent to or if they consent using a different device or identifier, Segment sends the information about their consent, using a [Track call](/docs/connections/spec/track), to your downstream destinations and storage destinations.
 
 For example: 
 
@@ -48,7 +48,7 @@ For example:
 
 If a **consent conflict** exists (for example, one user on two different devices consented to two different categories), Segment resolves the conflict according to the [Reconcile Consent](/docs/privacy/reconcile-consent) documentation.
 
-You can view more information about a user's consent preferences on their profile in Unity. Consent information and a consent conflict flag are visible as traits on a user's profile in Unity.
+Consent information and a consent conflict flag are visible as traits on a user's profile in Unify.
 
 ## Consent object