Apply suggestions from code review [netlify-build]

Co-authored-by: rchinn-segment <[email protected]>

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -2,7 +2,7 @@
 title: Configure Consent Management
 hidden: true
 ---
-> info "Consent Management is currently in private beta"
+> 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.
 
 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. 
@@ -19,20 +19,20 @@ Before you can configure consent in Segment, take the following steps:
 ## Step 1: Create consent categories in the Segment app
 
 > info "Limited availability of sources and destinations during private beta"
-> During the private beta, you can send events from web sources to consent categories. Enforcement of consent preferences is only available for event streaming destinations, webhooks, and functions. You can map one event streaming destination, webhook, or function to multiple consent categories. All other source and destination types are not impacted by consent mappings. 
+> During private beta, you can send events from web sources to consent categories. Enforcement of consent preferences is only available for event streaming destinations, webhooks, and functions. You can map one event streaming destination, webhook, or function to multiple consent categories. All other source and destination types are not impacted by consent mappings. 
 
 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 **Create categories**.
 3. Confirm that you have completed the required prerequisites, and click **Next**.
 4. On the Create consent categories page, add the following information to the category form:
-  - **Category name**: Enter a name that describes your use case for the data sent to this destination
+  - **Category name**: Enter a name that describes your use case for the data sent to this destination.
   - **Category ID**: In OneTrust, this is a string of up to five alphanumeric characters, but other CMPs may have a different format. This field is case sensitive.
   - **Mapped destinations**: Select one or more of your destinations to map to this category. Category mappings apply to all instances of a destination. 
   <br/><br/>**Optional**: Click **Add category** to create another category.
-5. Once you have finished setting up your category or categories, click **Save**.
+5. Once you've finished setting up your category or categories, click **Save**.
 
 > warning "Segment recommends mapping all destinations to a category"
-> Any destinations without a mapping are assumed to not require user consent and will receive all events containing a consent object. 
+> Destinations without a mapping are assumed to not require user consent and will receive all events containing a consent object. 
 
 ## Step 2: Add the consent wrapper to Analytics.js
 
@@ -84,11 +84,11 @@ If you need to make changes to your consent categories, you can edit them on the
 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've made your changes, click **Save**.
 
 ## 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.  
+Disabling a consent category means that Segment no longer enforces end user consent preferences for the destinations in the disabled category. Other consent categories aren't 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, disable the toggle for the category you'd like to disable. 

src/privacy/consent-management.md

@@ -5,8 +5,8 @@ related:
   - "/privacy/account-deletion/"
   - "/privacy/complying-with-the-gdpr/"
 ---
-> 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.
+> info "Consent Management is in private beta"
+> 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.
 
 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.
 
@@ -25,7 +25,7 @@ Segment routes events with a consent object to the destinations in categories co
 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.
 
 > warning "Segment recommends mapping all destinations to a category"
-> Any destinations without a mapping are assumed to not require user consent and will receive all events containing a consent object. 
+> Segment assumes any destinations without a mapping do not require user consent and will receive all events containing a consent object. 
 
 
 <!--- 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:

src/privacy/reconcile-consent.md

@@ -5,7 +5,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 currently in private beta"
+> 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.
 
 ## Reconcile consent category trait conflicts
@@ -16,7 +16,7 @@ Segment detects when there are conflicting consent categories for a user and
 
 ## 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:
+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 |
 | -------- | ----------------- | ------------------ |