grammer and voice activitation DOC-1

Author: markzegarelli

src/personas/identity-resolution/externalids.md

@@ -3,15 +3,15 @@ title: Identity Resolution ExternalIDs
 ---
 
 > note ""
-> **NOTE:** This setup guide is intended for spaces created before September 27th, 2020. For spaces created after September 27th, 2020, please refer to the onboarding guide [here](/docs/personas/identity-resolution/identity-onboarding/).
+> **NOTE:** The steps in this guide pertain to spaces created before September 27th, 2020. For spaces created after September 27th, 2020, please refer to the onboarding guide [here](/docs/personas/identity-resolution/identity-onboarding/).
 
 ## Default ExternalIDs
 
 The Identity Graph creates or merges profiles based on externalIDs. ExternalIDs will become the Identities attached to a User Profile in the User Explorer:
 
 ![](images/jane_doe_new_identities.png)
 
-We automatically promote the following traits and IDs in track and identify calls to externalIDs:
+Segment automatically promotes the following traits and IDs in track and identify calls to externalIDs:
 
 | External ID Type   | Message Location in Track or Identify Call                                                                    |
 | ------------------ | ------------------------------------------------------------------------------------------------------------- |
@@ -73,7 +73,7 @@ For example, the following user had anonymous_id and user_id promoted as identif
 
 ## Example
 
-Let's say a new anonymous user visits your Pricing page:
+For example, a new anonymous user visits your Pricing page:
 
 ``` js
 analytics.page('Pricing', {
@@ -88,9 +88,9 @@ At this point, the Identity Graph will create a new user with external id (anony
 
 ![](images/identity_resolution_2.png)
 
-Any new events received with the same external id (anonymous_id: `anon_123`) will be appended to same user `use_4paotyretuj4Ta2bEYQ0vKOq1e7`.
+Any new events received with the same external id (anonymous_id: `anon_123`) are appended to same user `use_4paotyretuj4Ta2bEYQ0vKOq1e7`.
 
-Next, the user goes to a signup form and signs up:
+Next, the user goes to a sign up form and signs up:
 
 ``` js
 analytics.track('User Signup', {

src/personas/identity-resolution/identity-resolution-onboarding.md

@@ -1,21 +1,11 @@
 ---
 title: Identity Resolution Onboarding
 ---
-<!-- COMMENTS HERE 
-- Are all the images necessary? Concerned that they break up the flow of content too much, making important text more difficult to scan.
-- Double-check to make sure code `style` is used correctly? Is it fields or values that get it?
-- A heading says Select Identity Resolution settings, but this is not described in that section.
-- "Merge Protection Rules" are mentioned as referenceable below, but not found in the doc.
-- For Limits, we might want to mention in the examples that a time period is included with a numeric value.
--->
-
 > note ""
 > **NOTE:** The steps in this guide pertain to spaces created after **October 5th, 2020**. For spaces created before **October 5th, 2020**, please refer to[Identity Resolution Settings](/docs/personas/identity-resolution/identity-resolution-settings).
 
-## Select Identity Resolution settings
-
 > note ""
-> **NOTE:** Workspace owners, Personas administrators, and users with the Identty Admin role can edit Identity Resolution Settings.
+> **NOTE:** Workspace owners, Personas administrators, and users with the Identity Admin role can edit Identity Resolution Settings.
 
 Segment creates and merges user profiles based a space's Identity Resolution configuration. Segment searches for identifiers such as `userId`, `anonymousId` and `email` on incoming events and matches them to existing profiles or creates new profiles. These identifiers display in the Identities tab of a User Profile in the User Explorer:
 
@@ -25,46 +15,38 @@ Segment creates and merges user profiles based a space's Identity Resolution con
 
 When Personas receives a new event, Segment looks for any profiles that match any of the identifiers on the event.
 
-Based on the existance of a match, one of three actions can occur:
+Based on the existence of a match, one of three actions can occur:
 
 **1: Create a new profile**
 When there are no pre-existing profiles that have matching identifiers to the event, Segment create a new user profile.
 
 **2: Add to existing profile**
-When there is one profile that matches all identifiers in an event, Segment attempta to map the traits, identifiers and events on the call to that existing profile. If there is an excess of any identifier on the final profile, Segment defers to the merge protection rules outlined below.
+When there is one profile that matches all identifiers in an event, Segment attempts to map the traits, identifiers and events on the call to that existing profile. If there is an excess of any identifier on the final profile, Segment defers to the Identity Resolution rules outlined below.
 
 **3: Merge existing profiles**
-When there are multiple profiles that match the identifiers in an event, Segment checks the merge protection rules outlined below, and attemts to merge profiles.
+When there are multiple profiles that match the identifiers in an event, Segment checks the Identity Resolution rules outlined below, and attempts to merge profiles.
 
 ## Identity Resolution settings
 
 Identity Admins should first configure Identity Resolution Settings page to protect the identity graph from inaccurate merges and user profiles.
 
-During the space creation process, the first step is to choose an Identity Resolution configuration. If this is your first space, you have the option to choose a Segment-suggested Out-of-the-Box configuration or a custom Identity Resolution setup. All subsequent spaces have a third option of importing settings from a different space.
+During the space creation process, the first step is to choose an Identity Resolution configuration. If this is your first space, you have the option to choose a Segment-suggested Out-of-the-Box configuration or a custom Identity Resolution setup. All other spaces have a third option of importing settings from a different space.
 
 ![](images/first_screen.png)
 
 ### Out-of-the-Box
 
 For most first-time Personas users, Segment recommends that you use the out-of-the-box configuration and answer a short series of questions for a best-fit setup for your use-case.
 
-![](images/out_of_the_box_1.png)
-
-![](images/out_of_the_box.png)
-
 If you have custom unique identifiers or do not have a canonical `user_id` are automatically redirected to the Identity Resolution Settings page to complete your setup.
 
 ### Custom rules
 
 If you are familiar with identity or have custom identifiers, Segment recommends that you select Custom Rules.
 
-![](images/custom_rules_1.png)
+Segment redirects you to the Identity Resolutions Settings page where you can add Default Identifiers or Custom Identifiers.
 
-Segment redirects youto the Identity Resolutions Settings page where you can add default or custom identifiers.
-
-![](images/add_identifiers.png)
-
-Find Segment's default 11 identifiers below.
+Segment's 11 default are:
 
 | External ID Type     | Message Location in Track or Identify Call                                                                    |
 | -------------------- | ------------------------------------------------------------------------------------------------------------- |
@@ -105,15 +87,16 @@ Before sending data through, Segment also recommends that you add any default ha
 
 #### Limit
 
-Identity Admins can specify the total number of values allowed per identifier type on a profile during a certain period. This will vary depending on how companies define a user today. In most cases, companies rely on `user_id` to distinguish user profiles and Segment defaults to the following configurations:
+Identity Admins can specify the total number of values allowed per identifier type on a profile during a certain period. For example, in the image below, the `anonymous_id` field has a limit of **5 Weekly**.
+![](images/anonymous-id.png)
+
+This will vary depending on how companies define a user today. In most cases, companies rely on `user_id` to distinguish user profiles and Segment defaults to the following configurations:
 
 | Identifier            | Limit |
 | --------------------- | ----- |
 | user_id               | 1     |
 | all other identifiers | 5     |
 
-![](images/user-id.png)
-
 Specific cases may deviate from this default. For example, a case where a user can have more than one `user_id` but one email, like when `shopify_id` and an internal UUID define a user. In this case, an example configuration may be:
 
 | Identifier            | Limit |
@@ -125,14 +108,12 @@ Specific cases may deviate from this default. For example, a case where a user c
 When you choose the limit on an identifier, ask the following questions about each of the identifiers you send to Segment:
 
 1. Is it an immutable ID? An immutable ID, such as `user_id`, should have `1 ever` per user profile.
-2. Is it a constantly changing ID? A constantly changing ID, such as `anonymous_id` or `ga_client_id`, should have a short sliding window, such as `5 weekly` or `5 monthly`, depending on how often your application automatically logs out the user.
-3. Is it an ID that updates on a yearly basis? Most customers will have around 5 emails or devices at any one time, but can update these over time. For identifiers like `email`, `android.id` or `ios.id`, Segment recommends a longer limit like `5 annually`.
-
-![](images/anonymous-id.png)
+2. Is it a constantly changing ID? A constantly changing ID, such as `anonymous_id` or `ga_client_id`, should have a short sliding window, such as **5 weekly** or **5 monthly**, depending on how often your application automatically logs out the user.
+3. Is it an ID that updates on a yearly basis? Most customers will have around 5 emails or devices at any one time, but can update these over time. For identifiers like `email`, `android.id` or `ios.id`, Segment recommends a longer limit like **5 annually**.
 
 #### Priority
 
-Segment considers the priority of an identifier once the limit of any identifier on the final profile is exceeded.
+Segment considers the priority of an identifier once that identifier exceeds the limit on the final profile.
 
 For example, consider a Personas space with the following Identity Resolution configurations:
 
@@ -142,9 +123,11 @@ For example, consider a Personas space with the following Identity Resolution co
 | email        | 5     | 2        |
 | anonymous_id | 5     | 3        |
 
-A profile already exists with user_id `abc123` and email `[email protected]`. A new event comes in with new user_id `abc456` but the same email `[email protected]`. If this event maps to this profile, the resulting profile would then contain two user_ids and one email. Given that user_id has a limit of 1, this exceeds the limit of an identifier. As a result, the priority of these identifiers is checked. Because email and user_id are the two identifiers on the event and email ranks lower than user_id, Segment demotes email as an identifier on the incoming event and tries again.
+A profile already exists with `user_id` **abc123** and `email` **[email protected]**. A new event comes in with new `user_id` **abc456** but the same `email` **[email protected]**. 
 
-At this point, the event searches for any profiles that match just the identifier user_id `abc456`. Now there are no existing profiles with this identifier, so Segment creates a new profile is created with user_id `abc456`.
+If this event maps to this profile, the resulting profile would then contain two `user_id` values and one `email`. Given that `user_id` has a limit of 1, this exceeds the limit of that identifier. As a result, Segment checks the priority of the `user_id` identifier. Because `email` and `user_id` are the two identifiers on the event and `email` ranks lower than `user_id`, Segment demotes `email` as an identifier on the incoming event and tries again.
+
+At this point, the event searches for any profiles that match just the identifier user_id `abc456`. Now there are no existing profiles with this identifier, so Segment creates a new profile with user_id `abc456`.
 
 By default, Segment explicitly orders user_id and email as rank `1` and `2`, respectively. All other identifiers are in alphabetical order beginning from rank `3`. This means that if the identifiers sent with events flowing into personas are user_id, email, anonymous_id and ga_client_id, the rank would be as follows:
 
@@ -165,7 +148,7 @@ If a new android.id identifier appeared without first giving it explicit order,
 | anonymous_id | 4        |
 | ga_client_id | 5        |
 
-Thus, if you require an explicit order for all identifiers, configure this in the Identity Resolution settings page before sending in events.
+If you require an explicit order for all identifiers, configure this in the Identity Resolution settings page before sending in events.
 
 ![](images/edit-priority.png)
 
@@ -177,24 +160,24 @@ When choosing the priority of your identifier, ask the following questions about
 
 ### Importing from an existing space
 
-This option is available to new spaces once the initial Dev space is created. Segment recommends this option when identity settings are validated as correct in the initial Dev space and should be copied into the Prod space.
+This option is available to new spaces after you create an initial Dev space. Segment recommends this option when identity settings are validated as correct in the initial Dev space and should be copied into the Production space.
 
-![](images/import.png)
+You can review the identifiers, priorities, limits, and blocked values before you complete the import.
 
-## Connecting a source
+![](images/import.png)
 
-After you configure Identity Resolution settings, the next step is to connect a source to the Personas space.
+## Connect a source
 
-![](images/connect_sources.png)
+After you configure Identity Resolution settings, the next step is to connect a [source](/docs/connections/sources/) to the Personas space.
 
-## Creating an Audience
+## Create an Audience
 
 After you connect a source, Personas creates user profiles based off of replayed and newly incoming data.
 
 ![](images/create_audience.png)
 
 The next step, which is important in the Dev space, is to create an audience to ensure that user profiles have populated correctly and that the identity resolution settings follow expected business logic.
 
-For example, if there should be 100,000 distinct users who have a user_id, this would be a great way to validate that the identity resolution settings have calculated profiles correctly.
+For example, if there should be 100,000 distinct users who have a `user_id`, this would be a great way to validate that the identity resolution settings have calculated profiles correctly.
 
-Users can learn more about creating audiences and traits [here](/docs/personas/audiences.md).
+For more information about how to create audiences and traits, see [Audiences](/docs/personas/audiences/).