Apply suggestions from code review

Author: rchinn1

src/unify/linked-profiles/data-graph.md

@@ -4,6 +4,9 @@ plan: unify
 beta: true
 ---
 
+> info "Segment's Data Graph is in private beta"
+> The Data Graph is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
+
 With Linked Profiles, you can build a Data Graph that defines relationships between any entity data set in the warehouse and the Segment Profiles you send with Profiles Sync. 
 
 Make this relational data accessible to marketers and business stakeholders to empower them with the data they need to create targeted and personalized customer engagements.
@@ -15,10 +18,10 @@ Make this relational data accessible to marketers and business stakeholders to e
 
 To use the Data Graph, you'll need the following:
 - A Snowflake Data Warehouse. 
-- An [Actions-based Destination](/docs/connections/destinations/actions/#available-actions-based-destinations).
+- An [actions-based destination](/docs/connections/destinations/actions/#available-actions-based-destinations).
 
 > info ""
-> Linked Profiles follows Zero Copy principles, and doesn't copy entities to store in Segment. Segment stores and processes all data in the United States. 
+> Linked Profiles follows zero-copy principles, and doesn't copy entities to store in Segment. Segment stores and processes all data in the United States. 
 
 > warning ""
 > Don't send any personal health information with the Data Graph.
@@ -47,31 +50,23 @@ To track what data has been sent to Segment on previous syncs, Segment stores de
 
 To connect your warehouse to the Data Graph:
 
-1. In your Segment workspace, navigate to **Unify**, and select **Data Graph**.
+1. Navigate to **Unify > Data Graph**.
 - This should be a Unify space with Profiles Sync already set up.
 2. Click **Connect warehouse**.
 3. Select your warehouse type.
+- Note that Linked Audiences only supports Snowflake.
 4. Enter your warehouse credentials. 
 5. Test your connection, then click **Save**.
 
 ## Step 3: Build your Data Graph
 
 The Data Graph is a semantic layer that represents a subset of relevant business data that you'll use for audience targeting and personalization in downstream tools. 
 
-Use the configuration language spec below to add models to build your Data Graph.
-
-### Delete and edit entities and/or relationships from your Data Graph
-
-> info ""
-> Each Unify space has one Data Graph. The current version is v0.0.6.
-
-Segment recommends creating a new Linked Audience or Linked Event. Deleting entities and relationships are not yet supported. Editing entities and relationships in the Data Graph may lead to errors if these entities or relationships are referenced in existing Linked Audiences and Linked Events. 
-
-While you can delete relationships or entities from the Data Graph, these relationships and entities will still display in the Linked Audience builder and Linked Events.
+Use the configuration language spec below to add models to build your Data Graph. The Data Graph currently supports 6 layers of depth, including the Profile entity.
 
 ### Define entities
 
-Use the parameters, defintions, and examples below to help you define entities.
+Use the parameters, definitions, and examples below to help you define entities.
 
 > warning ""
 > Snowflake schemas are case sensitive, so you'll need to reflect the schema, table, and column names based on how you case them in Snowflake.
@@ -131,7 +126,6 @@ Use the following relationship, parameters, and examples to help you relate enti
 > warning ""
 > Snowflake schemas are case sensitive, so you'll need to reflect the schema, table, and column names based on how you case them in Snowflake.
 
-<!--Bookmark -->
 #### Relate Entity to Profile
 
 | Parameters     | Definition                                                           |
@@ -194,7 +188,7 @@ data_graph {
 | `relationship`      | A unique slug for the relationship, which is immutable and treated as a delete if you make changes. The slug must be in all lowercase and will support dashes or underscores (for example, `user-account` or `user_account`).   |
 | `name`        | This should be a unique label that displays throughout your Segment space.                          |
 | `related_entity`   | Reference your already defined entity. |
-| `join_on`         |    Define relationships between two entity tables `[lefty entity name].[column name] = [right entity name].[column name]`. Note that the entity name is a reference to the alias provided in the config and doesn't need to be the fully qualified table name. |
+| `join_on`         |    Defines relationships between two entity tables `[lefty entity name].[column name] = [right entity name].[column name]`. Note that the entity name is a reference to the alias provided in the config and doesn't need to be the fully qualified table name. |
 
 
 ```py
@@ -215,15 +209,17 @@ data_graph {
 
 ```
 
-#### relating entities with a junction table
+#### Relating entities with a junction table
 
-If you're relating entities with a junction table:
+If you're relating entities with a junction table:    
 
-- `Junction_table`: Define relationships between two entities tables joined by a junction table.
-     - `table_ref`: Define the table reference to the join table. In order to specify a connection to your table in Snowflake, a fully qualified table reference is required: `[database name].[schema name].[table name]`.
-     - `primary_key`: The unique identifier on the join table and should be a column with unique values per row.
-     - `left_join_on`: Define relationship between the two entity tables: `[left entity name].[column name] = [junction table column name]`.
-     - `right_join_on`: Define relationship between the two entity tables: `[junction table column name] = [right entity name].[column name]`.
+| Parameters     | Definition                                                           |
+| ----------- | --------------------------------------------------------------------- |
+| `Junction_table`      | Define the table reference to the join table. In order to specify a connection to your table in Snowflake, a fully qualified table reference is required: `[database name].[schema name].[table name]`.  |
+| `table_ref`      | Define the table reference to the join table. In order to specify a connection to your table in Snowflake, a fully qualified table reference is required: `[database name].[schema name].[table name]`.  |
+| `primary_key`    | The unique identifier on the join table and should be a column with unique values per row. |
+| `left_join_on`   | Define relationship between the two entity tables: `[left entity name].[column name] = [junction table column name]`. |
+| `right_join_on`  | Define relationship between the two entity tables: `[junction table column name] = [right entity name].[column name]`. |
 
 Note that `schema.table` is implied within the junction table column name and doesn't need to be provided. 
 
@@ -244,7 +240,7 @@ data_graph {
                     related_entity = "product-entity"
                     junction_table {
                          primary_key = "id"
-                         table_ref = "PRODUCTION.CUSTOM.CART_PRODUCT"
+                         table_ref = "PRODUCTION.CUSTOMER.CART_PRODUCT"
                          left_join_on = "CART.ID = CART_ID"
                          #schema.table is implied within the cart_id key
                          right_join_on = "PRODUCT_ID = PRODUCT.SKU"
@@ -253,9 +249,9 @@ data_graph {
                }
           }
      }         
-}
 
 ```
+## Data Graph Example 
 
 ![An example of a data graph](/docs/unify/images/data-graph-example.png)
 
@@ -334,6 +330,11 @@ To edit your Data Graph:
 1. Navigate to **Unify > Data Graph**.
 2. Select the **Builder** tab, and click **Edit Data Graph**.
 
+Segment recommends creating a new Linked Audience or Linked Event. Deleting entities and relationships are not yet supported. Editing entities and relationships in the Data Graph may lead to errors if these entities or relationships are referenced in existing Linked Audiences and Linked Events. 
+
+> info ""
+> While you can edit entities and relationships in the Data Graph, these relationships and entities will still display in the Linked Audience Builder and Linked Events.
+
 You can edit your Data Graph at any time. However, some types of edits may impact existing Linked Audiences and Linked Events. These include:
 
 - Adding a new relationship before an existing relationship

src/unify/linked-profiles/linked-audiences.md

@@ -4,10 +4,16 @@ plan: unify
 beta: true
 ---
 
+> info "Linked Audiences is in private beta"
+> Linked Audiences is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
+
 With Linked Audiences, you can use the relational data you've defined in your Data Graph to build audiences and send them to your downstream destinations. 
 
 From the relationships you've defined between the profiles and entities in your warehouse, you can filter on an entity, profile trait, and audience membership conditions to create hyper-segmented audiences.
 
+> info "Linked Audiences warehouse support"
+> At this time, Linked Audiences only supports Snowflake. 
+
 > success ""
 > Before you build Linked Audiences, be sure you've defined entities in your [Data Graph](/docs/unify/linked-profiles/data-graph/). 
 
@@ -17,7 +23,7 @@ From the relationships you've defined between the profiles and entities in your
 To help you get started with Linked Audiences, consider the following best practices: 
 
 1. It may be helpful to first identify an entity that is directly associated with your users, such as `Accounts`, `Households`, or `Organizations`.
-2. From there you can define relationships between this entity with any of the other entities that may associated with it, such as how `Accounts` can have the following: `Subscriptions`, `Purchases`, or `Carts`. 
+2. From there you can define relationships between this entity with any of the other entities that may be associated with it, such as how `Accounts` can have the following: `Subscriptions`, `Purchases`, or `Carts`. 
 3. You can create entity relationships up to six levels in depth. For example, an entity condition that queries for relationships between `Profiles`, `Accounts`, `Credit Cards`, and `Transactions` has four levels of depth. 
 4. To further refine your audience, identify column values that you might also want to filter your entities by, or configure profile trait and audience membership conditions. 
 
@@ -28,7 +34,7 @@ Below are some example use cases to help you learn more about Linked Audiences.
 ### Build an audience of cat owners who are also a part of the platinum membership tier
 
 Build an audience with `Households` and `Pets` where:
-- `pets.type` equals "cat"
+- `pets.type` = "cat"
 
 And where:
 - `profile.audience_membership` = "Platinum membership tier"
@@ -46,8 +52,8 @@ Furthermore, filtering the audience against `profile.audience_membership` for "P
 ### Build an audience of users with premium subscriptions who are located in Canada
 
 Build an audience with `Accounts` and `Subscriptions`, where the following are true:
-- `subscription.status` equals "active"
-- `subscription.tier` equals "premium"
+- `subscription.status` = "active"
+- `subscription.tier` = "premium"
 
 And where:
 - `profile.country` = "Canada"
@@ -91,7 +97,7 @@ Use the Audience overview page to build or maintain a Linked Audiences.
 6. Enter an audience name and description, then click **Create Audience**.
 
 > warning ""
-> At this time, Linked Audiences can't be edited or deleted. Create a new audience to update conditions. To disable an audience, navigate to the **Settings** tab of an audience and toggle the **Enabled** button off.
+> Linked Audiences can't be edited or deleted. Create a new audience to update conditions. To disable an audience, navigate to the **Settings** tab of an audience and toggle the **Enabled** button off.
 
 
 ## Step 2: Activate your Linked Audience
@@ -106,12 +112,12 @@ You can use your Linked Audience to activate any [actions-based destination](/do
 
 ### Step 2a: Add an action destination
 
-To activate your Linked Audience, you'll first need to add an action destination.
+To activate your Linked Audience, you first need to add an action destination.
 
 From the Add destination window, select your destination and click **Next**.
 
 ### Step 2b: Select event 
-After adding an actions destination, select what type of event you want to send to the destination. Events update the destination about changes to your entity or audiences. You can then use these actions to orchestrate campaigns in other tools.
+After adding an actions-based destination, select what type of event you want to send to the destination. Events update the destination about changes to your entity or audiences. You can then use these actions to orchestrate campaigns in other tools.
 
 You can send events:
 - When an entity on a profile changes:
@@ -123,7 +129,7 @@ You can send events:
     - [Audience Exited](#audience-exited)
 
 > info ""
-> Note that you can't send events before you identify people. Ensure you're making the profile(s) known in the destination before you send events. You can do this by sending an `Audience Membership Changed` event first, or by creating an Identify event in Connections.
+> You can't send events before you identify people. Ensure you're making the profile(s) known in the destination before you send events. You can do this by sending an `Audience Membership Changed` event first, or by creating an Identify event in Connections.
 
 #### Entity added
 
@@ -170,29 +176,38 @@ Example use case:
 
 ### Step 2c: Select an action
 
-Next, you'll select the destination action to call when the event happens.
+Select the destination action to call when the event happens.
 
 Segment displays available actions based on the destination action you've connected with your Linked Audience. 
 
 Visit the [destination actions docs](/docs/connections/destinations/actions/) learn more about destination actions, and view available actions for your destination.
 
 ### Step 2d: Configure the event
 
-Finally, you'll configure your event and select additional properties to include in the event. 
+Configure your event and select additional properties to include in the event. 
 
 To configure your event:
 
 1. Select additional properties to include in each event. 
 - As you're configuring your event, you can view a preview of the enriched event based on your property selections. 
 2. Map your event from your audience to your destination.
 - You can preview what the event will look like in your destination.
-3. After configuring, click **Save** to enable your Linked Audience. 
+3. Select if you'd like to [send events for current profiles and entities in the audience](#send-events-for-current-profiles-and-entities-in-the-audience).
+4. After configuring, click **Save** to enable your Linked Audience. 
 
 After saving, you'll be redirected to a destination sidesheet where you can view all events and their corresponding actions.
 
+#### Send events for current profiles and entities in the audience
+
+Select if you'd like to sync existing profiles and entities in the audience with the **Send events for current profiles and entities in audience** checkbox.
+
+This box is unchecked by default. If you leave this box unchecked, Segment only sends events for new profiles and entities that match the audience conditions.
+
+However, if you select this checkbox, Segment will also send events for profiles and entities that currently match the audience description. 
+
 ## Step 3: Confirm the payload in your destination
 
-Linked Audiences will send events to your destination after Segment computes the audience. 
+Linked Audiences sends events to your destination after Segment computes the audience. 
 
 To confirm your destination is receiving events, Segment recommends that you log in to your destination and perform one of the following:
 - Monitor the event activity

src/unify/linked-profiles/linked-events.md

@@ -12,6 +12,9 @@ Use Linked Events to enrich real-time event streams with entities from your data
 
 On this page, you'll learn how to get started with Linked Events.
 
+> info "Linked Events warehouse support"
+> Linked Events supports Snowflake, BigQuery, and Redshift.
+
 ## Use cases
 
 With Linked Events, you can:
@@ -156,7 +159,7 @@ Use enrichments to select the entity you wish to send to your downstream destina
 
 In the Mappings tab, locate the **Select Mappings** section where you can enrich source properties from the entities you've selected in the previous step.
 
-1. Select the propery field that you'd like to enrich, then select the **Enrichments** tab. 
+1. Select the property field that you'd like to enrich, then select the **Enrichments** tab. 
 2. Select the entity you want to send to your destination. 
 - You’ll have access to all rows/columns in your data warehouse associated with the property you've selected in the previous step.
 3. Add the key name on the right side, which is what Segment sends to your destination. 

src/unify/linked-profiles/setup-guides/BigQuery-setup.md

@@ -7,8 +7,14 @@ plan: unify
 > info "Linked Events is in private beta"
 > Linked Events is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
+> info ""
+> At this time, you can only use BigQuery with Linked Events. 
+
 On this page, you'll learn how to connect your BigQuery data warehouse to Segment. 
 
+
+## Set up BigQuery
+
 > warning ""
 > You need to be an account admin to set up the Segment BigQuery connector as well as write permissions for the `__segment_reverse_etl` dataset. 
 

src/unify/linked-profiles/setup-guides/redshift-setup.md

@@ -7,6 +7,9 @@ plan: unify
 > info "Linked Events is in private beta"
 > Linked Events is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
+> info ""
+> At this time, you can only use Redshift with Linked Events.
+
 On this page, you'll learn how to connect your Redshift data warehouse to Segment. 
 
 ## Getting started 

src/unify/linked-profiles/setup-guides/snowflake-setup.md

@@ -7,10 +7,14 @@ beta: true
 > info "Linked Profiles is in private beta"
 > Linked Profiles (Data Graph, Linked Events, and Linked Audiences) is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
 
+
 On this page, you'll learn how to connect your Snowflake data warehouse to Segment.
 
 Be sure to log in with a user that has read and write permissions so that Segment can write to your database. 
 
+> info ""
+> Both Linked Events and Linked Profiles support Snowflake. 
+
 
 ## Getting started 
 
@@ -108,7 +112,7 @@ GRANT SELECT ON TABLE <schema-name>.<table_name> TO ROLE segment_entities;
 
 ### Reverse ETL table permissions
 
-If you've ever run Segment's Reverse ETL in your database, you'll need to add the following [table permissions](https://docs.snowflake.com/en/user-guide/security-access-control-privileges#table-privileges){:target="_blank"}:
+If you've ever run Segment's [Reverse ETL](/docs/connections/reverse-etl/) in your database, you'll need to add the following [table permissions](https://docs.snowflake.com/en/user-guide/security-access-control-privileges#table-privileges){:target="_blank"}:
 
 ```sql
 GRANT USAGE ON SCHEMA __segment_reverse_etl TO ROLE segment_entities;