update supported destinations, add version, move configure consent management blurb

Author: forstisabella

src/privacy/configure-consent-management.md

@@ -22,9 +22,9 @@ 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 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 data lakes, warehouses, event streaming destinations, webhooks, and functions. You can map one data lake, warehouse, event streaming destination, webhook, or function to multiple consent categories. All other source and destination types are not impacted by consent mappings.
 >
-> Storage, RETL, and Engage destinations do not enforce consent preferences. 
+> Blob storage, RETL, and Engage destinations do not enforce consent preferences. 
 
 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**.

src/privacy/consent-management.md

@@ -10,11 +10,11 @@ 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 only 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)
 
-After a user sets their consent preferences, Segment captures them with the [Analytics.js Consent Tools wrapper](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools) and updates the [consent object](#consent-object). The events are then sent downstream to any streaming destinations in categories that a user consented to share data with.
+After a user sets their consent preferences, Segment captures them with the [Analytics.js Consent Tools wrapper](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} and updates the [consent object](#consent-object). The events are then sent downstream to any streaming destinations in categories that a user consented to share data with.
 
 > info ""
 > Segment collects consent for both registered users and anonymous users.
@@ -42,6 +42,7 @@ For example, if a user agreed to share their information with you for all catego
   "timestamp": "2023-01-01T00:00:00.000Z",
   "context": {
     "consent": {
+      "version": 1,
       "consentPreferences" : {
    "Advertising": true,
    "Analytics": false,
@@ -58,9 +59,6 @@ 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/privacy/configure-consent-management/).
-
 ## Consent object
 
 Segment requires every event from all of your sources to include the end-user consent preferences, captured by your consent management tools or your application logic, in the form of the **consent object**. The consent object is a JSON object with the following format:
@@ -88,6 +86,8 @@ Segment assigns a `version` to your consent object. The `version` describes the
 
 A consent conflict flag and the categories consented to by a user are both pulled from the consent object and are visible as traits on a user's profile in Unify.
 
+<!--- To learn more about configuring consent categories in your workspace, see the [Configure Consent Management documentation](/docs/privacy/configure-consent-management/). --->
+
 
 ## Reconcile consent conflicts