Merge pull request #1799 from segmentio/pwseg-patch-1

DOC-282 added True/False exclusivity [netlify-ignore]

Author: pwseg

src/personas/journeys/build-journey.md

@@ -21,15 +21,15 @@ For more information, see [Setting up your Sources](/docs/personas/quickstart/#s
    3. Check **Use historical data** to allow users who have already matched the entry criteria to enter the Journey. Otherwise, only users who meet the entry conditions after publication will enter the Journey.
    4. Click **Preview** to see the list of user who meet your criteria. Verify that you've defined the right conditions.
    5. Click **Save**.
-4. Segment displays the entry condition on the Journey Builder canvas. It may take up to two minutes for Segment to estimated the number of users in the journey.
+4. Segment displays the entry condition on the Journey Builder canvas. It may take up to 2 minutes for Segment to estimate the number of users in the journey.
 5. Click **+** to add the next step and view available step types.
 
 > info ""
 > Users can only enter a Journey once.
 
 ### Using historical data for the entry step
 
-If you select the **Use historical data** option, Segment queries all historical data to generate a list of users who enter the Journey upon publication. If you do not select **Use historical data**, only users who satisfy the entry condition *after* you publish will enter the Journey.
+If you select the **Use historical data** option, Segment queries all historical data to generate a list of users who enter the Journey upon publication. If you don't select **Use historical data**, only users who satisfy the entry condition *after* you publish enter the Journey.
 
 > info ""
 > Your **Use historical data** selection won't impact subsequent Journey steps.  Only future events and existing trait memberships trigger post-entry Journey steps.
@@ -46,24 +46,28 @@ Journeys provides 5 step types, which you can add after the entry condition.
 
 **Wait for duration** defines the length of time in minutes, hours, days, or weeks that a user must wait before moving to the next step.
 
-**True/false split** divides the previous step's user group into two branches, based on Boolean logic against a defined condition. Users who satisfy the condition(s) move to the **True** branch. Otherwise, they move to the **False** branch.  
+**True/false split** divides the previous step's user group into 2 branches, based on Boolean logic against a defined condition. Users who satisfy the condition(s) move to the **True** branch. Otherwise, they move to the **False** branch. To enforce mutual exclusivity, Journeys evaluates true/false conditions when a user reaches the relevant step.  
 
 You can add Step Names to describe the users in the True and False branch.
 
 ![true/false split](images/journey_t-f-split.png)
 
-**Multi-branch split** divides the group of users from the previous step into two or more branches based on conditions you define for each branch. 
+**Multi-branch split** divides the group of users from the previous step into 2 or more branches based on conditions you define for each branch. 
 
 Define the number of branches you want to create. Then, add a **Wait for condition** step to define each branch's condition.
 
 > info ""
-> Journeys does not enforce mutual exclusivity in branch conditions. For more information about ensuring branch exclusivity, see [Best Practices](#).
+> Journeys doesn't enforce mutual exclusivity in branch conditions. For more information about ensuring branch exclusivity, see [Best Practices](#).
 
 **Send to Destinations** delivers information about the journey to the selected Destination. For more information, see [Send data to Destinations](/docs/personas/journeys/send-data)
 
 ## Cloning a Journey
 
-In Journey List view, click the **…** icon at the end of a row.  Next, select **Clone Journey**. Segment then creates a draft of your Journey. 
+To clone a Journey: 
+1. In Journey List view, click the **…** icon at the end of a row.  
+2. Select **Clone Journey**. 
+
+Segment then creates a draft of your Journey. 
 
 You can also clone a Journey from a Journey’s Overview by clicking the **…** icon. 
 
@@ -80,23 +84,23 @@ When you’ve finished creating your Journey, click **Save as Draft** in the bot
 
 #### When Journeys are in a draft state
 - Journeys estimates user counts only for the entry step.
-- Journeys does not send data to connected Destinations.
+- Journeys doesn't send data to connected Destinations.
 
 ### About Published Journeys
 
 Keep the following considerations in mind when working with a published Journey:
 
-- It may take up to three hours for Journeys to compute user counts after publication.
+- It may take up to 3 hours for Journeys to compute user counts after publication.
 - You can edit a Journey's name, description, and Destination steps.
-- You cannot add, edit, or delete other steps in the Journey.
+- You can't add, edit, or delete other steps in the Journey.
 - Once Journeys computes and displays user counts, you’ll see the list of users at each step of the Journey.
 - Click a user profile to see the Journey list to which they belong.
 - Journeys sends and updates data to Destinations in real-time.
 
 ## Edit name, description, and Destinations
 
 ### Edit name and description
-To edit your Journey name and description, navigate to the Settings tab of the Journey Overview.
+To edit your Journey name and description, navigate to the **Settings** tab of the Journey Overview.
 
 ### Edit destinations
 To edit Destinations, click **Edit Destinations** from the Journey Overview. You can add, edit, or delete connected Destinations within existing Send to Destinations steps.