Merge pull request #6881 from segmentio/linked-audiences-updates

Update linked-audiences.md [netlify-build]

src/engage/audiences/linked-audiences.md

@@ -58,37 +58,44 @@ Optionally, select a folder to add this audience.
 
 ### Maintaining Linked Audiences 
 
-After creating your Linked Audience, you will be brought to the Overview page with the Linked Audience in a disabled state. On the Overview page, you can view relevant audience information, such as Profiles in Audience, Run Schedule, Latest run, Next compute. You can edit or delete your Linked Audience. 
+After creating your Linked Audience, you will be brought to the Overview page with the Linked Audience in a disabled state. On the Overview page, you can view relevant audience information, such as Profiles in audience, Run schedule, Latest run, and Next run. 
 
-If you edit an audience with configured activation events, you should disable or delete impacted events for your audience to successfully compute. Events are impacted if they reference entities that are edited or removed from the audience definition.
+You can also delete Linked Audiences from the menu options or edit your Linked Audience in the Builder tab. If you edit an audience with configured activation events, you should disable or delete impacted events for your audience to successfully compute. Events are impacted if they reference entities that are edited or removed from the audience definition.
 
 You can also clone your linked audience to the same space from the List and Overview pages. Cloning a linked audience creates a new linked audience in the builder create flow with the same conditions as the linked audience that was cloned.
 
 ### Linked Audience conditions 
 
 The linked audiences builder sources profile trait and event keys from the data warehouse. This data must be synced to the data warehouse through [Profiles Sync](/docs/unify/profiles-sync/overview/) before you can reference it in the linked audience builder. If there is a profile trait that exists in the Segment Profile that hasn’t successfully synced to the data warehouse yet, it will be grayed out so that it can’t be selected.
 
-The linked audience builder also returns a subset of available entity property key values, event property and context key values, and profile trait key values that you can select in the input field drop-down so that you don’t need to type in the exact value that you want to filter on.If you don’t see the value you’re looking for, you can manually enter it into the input field. Segment displays 
+The linked audience builder also returns a subset of available entity property key values, event property and context key values, and profile trait key values that you can select in the input field drop-down so that you don’t need to type in the exact value that you want to filter on. If you don’t see the value you’re looking for, you can manually enter it into the input field. 
+Segment displays: 
 
 * the first 100 unique string entity property values from the data warehouse.
-    * If you want to opt out of displaying entity property values from the data warehouse, contact Segment Support.
 * the top 65 event property and context key values.
 * the top 65 profile trait key values.
 
-You can only create nested entity conditions 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.
+You can duplicate your conditions in the audience builder into the same condition group.You can only create nested entity conditions 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.
 
 As you're building your Linked Audience, you can choose from the following conditions:
 
-| Profiles Conditions     | Description                           |
+| Conditions     | Description                           |
 |---------------------------|---------------------------------------|
-| with entity   | Creates a condition that filters profiles associated with entity relationships defined in the [Data Graph](/docs/unify/data-graph/). With this condition, you can navigate the full, nested entity relationships, and filter your audience on entity column values. The event condition type supports these configurations: at least: supports 1 or greater,  exactly: supports 0 or greater, at most: supports 0 or greater* *When filtering by 0, you can’t filter on by entity properties or on additional nested entities. 
-| without entity   | Creates a condition that filters profiles that are not associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/).
+| with entity   | Creates a condition that filters profiles associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/). With this condition, you can navigate the full, nested entity relationships, and filter your audience on entity column values.|
+| without entity   | Creates a condition that filters profiles that are not associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/). With this condition, you can navigate the full, nested entity relationships, and filter your audience on entity column values.|
 | with [ trait](/docs/unify/#enrich-profiles-with-traits) | Creates a condition that filters profiles with a specific trait. |
 | without [ trait](/docs/unify/#enrich-profiles-with-traits)| Creates a condition that filters profiles without a specific trait.|
 | part of [audience](/docs/glossary/#audience)    | Creates a condition that filters profiles that are part of an existing audience. |
 | not part of [audience](/docs/glossary/#audience)     | Creates a condition that filters profiles that are not part of an existing audience. |
-| with [event](/docs/glossary/#event)         | Creates a condition that filters profiles that have a specific event in their event history. You can also filter on event property values. The event condition type supports these configurations: at least: supports 1 or greater, exactly: supports 0 or greater, at most: supports 0 or greater|
-| without [event](/docs/glossary/#event)        | Creates a condition that filters profiles that do not have a specific event in their event history. You can also filter on event property values. You can also duplicate your conditions in the audience builder into the same condition group.|
+| with [event](/docs/glossary/#event)         | Creates a condition that filters profiles that have a specific event in their event history. You can also filter on event property values.|
+| without [event](/docs/glossary/#event)        | Creates a condition that filters profiles that do not have a specific event in their event history. You can also filter on event property values.|
+
+The entity and event condition type supports these configurations: 
+at least: supports 1 or greater,  
+exactly: supports 0 or greater, 
+at most: supports 0 or greater.
+
+*When filtering by 0, you can’t filter on by entity properties or on additional nested entities.
 
 #### Operator Selection
 
@@ -102,21 +109,19 @@ You can create audience definitions using either `AND` or `OR` operators across
 
 If you have defined entity conditions in your audience definition, you will see a “Matched Entities” tab in the audience preview to help you understand what entities qualified a user to be a part of an audience.
 
-This information appears when you click the user profile generated from the audience preview. The contextual information encompasses entity relationships as well as entity column values that were used as filtering criteria in the audience definition. By default, Segment includes the entity ID.The data being returned is truncated - 10 entities at each level, 6 levels of depth. If you want to opt out of this functionality, contact Segment Support.
+This information appears when you click the user profile generated from the audience preview. The contextual information encompasses entity relationships as well as entity column values that were used as filtering criteria in the audience definition. By default, Segment includes the entity ID. The data being returned is truncated - 10 entities at each level, 6 levels of depth. If you want to opt out of this functionality, contact Segment Support.
 
 ![A screenshot of the Entity Explorer.](/docs/engage/images/entity_explorer.png)
 
 #### Dynamic References
 
 **Event Conditions**
 
-When filtering on event properties, you can dynamically reference the value of another profile trait, or enter a constant value. These operators support dynamic references:
-equals, not equals, less than, greater than, less than or equal, greater than or equal, contains, does not contain, starts with, ends with.
+When filtering on event properties, you can dynamically reference the value of another profile trait, or enter a constant value. These operators support dynamic references: equals, not equals, less than, greater than, less than or equal, greater than or equal, contains, does not contain, starts with, ends with.
 
 **Entity Conditions**
 
-When filtering on entity properties, you can dynamically reference the value of another entity column (from the same entity branch at the same level or above it), profile trait, or enter a constant value.
-You can only dynamically reference properties of the same data type. Dynamic references are only supported for certain operators depending on the data type:
+When filtering on entity properties, you can dynamically reference the value of another entity column (from the same entity branch at the same level or above it), profile trait, or enter a constant value.You can only dynamically reference properties of the same data type. Dynamic references are only supported for certain operators depending on the data type:
 NUMBER data type: equals, not equals, less than, greater than, less than or equal, greater than or equal
 STRING data type: equals, not equals, contains, does not contain, starts with, ends with
 TIMESTAMP data type: equals, not equals, less than, greater than, less than or equal, greater than or equal