Merge branch 'consent-management-private-beta' of https://github.com/segmentio/segment-docs into consent-management-private-beta

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -3,7 +3,7 @@ title: Configure Consent Management
 hidden: true
 ---
 > info "Consent Management is 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.
+> This means that 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.
 
 After setting up a third-party consent management platform (CMP), you can enforce the consent collected from your users by configuring consent categories in your your Segment workspace and adding the [consent object](/docs/privacy/consent-management/#consent-object) to your web libraries. 
 
@@ -37,7 +37,7 @@ Before you can configure consent in Segment, take the following steps:
 5. Once you've finished setting up your category or categories, click **Save**.
 
 > warning "Segment recommends mapping all destinations to a category"
-> Destinations without a mapping are assumed to not require user consent and will receive all events containing a consent object. 
+> Segment assumes all destinations without a mapping do not require user consent and will receive all events containing a consent object. 
 
 ## Step 2: Add the consent wrapper to Analytics.js
 

src/privacy/consent-management.md

@@ -22,7 +22,7 @@ After a user sets their consent preferences, Segment captures them with the [Ana
 ## Enforce consent
 Segment routes events with a consent object to the destinations in categories consented to by a user and to destinations that do not have a consent category.
 
-If an end 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. Events will be sent only to the destinations in the categories that are currently consented to.
+If an end 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. Segment only sends events to the destinations in the categories that are currently consented to.
 
 > warning "Segment recommends mapping all destinations to a category"
 > Segment assumes any destinations without a mapping do not require user consent and will receive all events containing a consent object. 

src/privacy/reconcile-consent.md

@@ -6,7 +6,7 @@ hidden: true
 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.
 
 > info "Consent Management is 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.
+> This means that 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.
 
 ## Reconcile consent category trait conflicts