journeys v2 minor docs updates

src/engage/journeys/event-triggered-journeys-steps.md

@@ -5,7 +5,7 @@ plan: engage-foundations
 
 [Event-Triggered Journeys](/docs/engage/journeys/event-triggered-journeys/) in Engage use steps to control how users move through a journey based on their actions or predefined conditions.
 
-Steps are the building blocks of a journey. This page explains the **Hold Until**, **Send to Destination**, and **Data split** steps, which enable precise control over journey progression and data delivery. 
+Steps are the building blocks of a journey. This page explains the **Hold until**, **Delay**, **Data split**, **Randomized split**, and **Send to Destination** steps, which enable precise control over journey progression and data delivery. 
 
 ## Hold Until: smart pauses in journeys
 
@@ -49,7 +49,7 @@ Enable this feature by selecting **Send profiles back to the beginning of this s
 
 Segment recommends putting branches for recurring events at the top of the list to improve readability.
 
-![Flow diagram of an Event-Triggered Journey for an abandoned cart scenario. The journey starts with a trigger event labeled 'Cart_Modified,' followed by a 'Hold Until' step checking if the user buys within two hours. The Hold Until step includes three branches: 'User updated cart, reset timer' for additional cart modifications, 'User purchased' triggered by an 'Order_Confirmation' event, and a 'Maximum hold duration' fallback set to two hours, which leads to a 'Send Abandonment Nudge' step. The flow ends with a 'Completed' state.](images/hold_until.png)
+![Flow diagram of an Event-Triggered Journey for an abandoned cart scenario. The journey starts with a trigger event labeled 'Cart_Modified,' followed by a 'Hold Until' step checking if the user buys within two hours. The Hold Until step includes three branches: 'User updated cart, reset timer' for additional cart modifications, 'User purchased' triggered by an 'Order_Confirmation' event, and a 'Maximum hold duration' fallback set to two hours, which leads to a 'Send Abandonment Nudge' step. The flow ends with a 'Completed' state.](/images/hold_until.png)
 
 In this example, users enter the journey when they modify their cart and wait for either a purchase or two hours to pass. If the user modifies their cart again during those two hours, the cart contents are updated, and the two-hour timer resets. As a result, follow-ups reflect the latest information.
 

src/engage/journeys/exit-rules.md

@@ -17,7 +17,7 @@ Exit rules don't wait for a profile to reach a specific step; they apply globall
 
 ## Configuring exit rules
 
-You'll set up exit rules in the journey’s settings panel. By default, journeys don’t have any exit conditions, but you can choose to add up to five exit events.
+You'll set up exit rules in the journey’s settings panel. By default, journeys don’t have any exit conditions, but you can choose to add up to ten exit events.
 
 ## Basic setup
 
@@ -31,8 +31,6 @@ For each exit rule, choose the event that should trigger the exit. You can also
 
 You can optionally require that the exit event matches the same identifier used in the entry event. This helps tie the two together, like if a journey starts with a `Cart_Modified` event and should exit only when `Order_Purchased.cart_id` matches the same cart.
 
-Each exit rule must be mutually exclusive. 
-
 > success "Exit rules Analytics"
 > You can track how exit rules are performing from the journey overview, which shows total exits per rule, and from individual step details, which show where users exited.
 
@@ -73,6 +71,6 @@ Follow these tips to make sure your exit rules behave as expected:
 
 As you work with exit rules, keep the following in mind:
 
-- You can configure up to 5 exit events per journey.
+- You can configure up to 10 exit events per journey.
 - Journeys support only one destination send for exit events.
 - If an exit rule is triggered, it overrides all other steps. The user exits immediately, even if they’re mid-delay or hold.

src/engage/journeys/journey-context.md

@@ -11,11 +11,11 @@ This page explains Journey context, which can help you dynamically adapt each jo
 
 Unlike traditional audience-based journeys, which rely solely on user progress through predefined steps, event-triggered journeys capture and store the details of user-triggered events. This shift allows you to access the data that caused users to reach a specific step and use it to make more precise decisions throughout the journey. 
 
-With journey context, you can:
+With journey context you can personalize customer experiences using real-time event data.
 
 <!-- Split journeys based on event attributes or outcomes.-->
-- Personalize customer experiences using real-time event data.
-- Enable advanced use cases like abandonment recovery, dynamic delays, and more.
+<!-- Personalize customer experiences using real-time event data. -->
+<!-- Enable advanced use cases like abandonment recovery, dynamic delays, and more. -->
 
 For example:
 
@@ -154,4 +154,4 @@ Whether you're orchestrating real-time abandonment recovery or personalizing mes
 
 To learn more about how Event-Triggered Journeys work, visit the [Event-Triggered Journeys documentation](/docs/engage/journeys/event-triggered-journeys/).
 
-<!-- PW, 10 December 2024; on PM request, commented out certain sections with functionalities not yet available during public beta. -->
+<!-- PW, 10 December 2024; on PM request, commented out certain sections with functionalities not yet available during public beta. -->

src/engage/journeys/v2/limits.md

@@ -14,7 +14,7 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.
 | Step name           | 73 characters                           | Maximum length for step names.                                                                                             |
 | Branch name         | 73 characters                           | Maximum length for branch names within a split step. Branch names must be unique across the journey.                       |
 | Additional branches | 5                                       | Maximum number of branches supported in a split or Hold Until step.                                                        |
-| Delay duration      | Minimum: 5 minutes<br>Maximum: 6 months | Allowed time range for Delay and Hold Until steps.                                                                         |
+| Delay duration      | Minimum: 5 minutes<br>Maximum: 182 days | Allowed time range for Delay and Hold Until steps.                                                                         |
 | Unique identifier   | 500 characters                          | For “Re-enter every time event occurs” rules, you must define a unique identifier. The value is limited to 500 characters. |
 
 
@@ -24,7 +24,7 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.
 | ------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
 | Requests per second (RPS) | 25 events/sec/profile              | Maximum events per second per Segment ID. Timer events are excluded. Excess events get dropped.                             |
 | Instances per profile     | 25 concurrent instances            | Maximum concurrent Journey instances per profile.                                                                           |
-| Loop back branch          | 100 instances                      | Maximum instances that can pass through a Wait Until loop-back.                                                             |
+| 'Send profiles back' branch          | 100 instances                      | Maximum count a single journey instance can pass through a Wait Until 'Send profiles back to the beginning of this step' branch.                                                             |
 
 ## Journey context
 
@@ -72,4 +72,4 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.
 | HIPAA eligibility | [HIPAA-Eligible Services](https://www.twilio.com/content/dam/twilio-com/global/en/other/hipaa/pdf/HIPAA-Eligible-Services.pdf){:target="_blank"} |
 | GDPR & BCR        | See [Complying with the GDPR](/docs/privacy/complying-with-the-gdpr/) for more information.                                   |
 
-Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. To request access to, correction of, or deletion of personal data, reach out to [Segment support](mailto:[email protected]).
+Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. To request access to, correction of, or deletion of personal data, reach out to [Segment support](mailto:[email protected]).