final fixes

Author: pwseg

src/engage/journeys/v2/journey-context.md

@@ -13,11 +13,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.-->
+<!-- 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.
+- Enable advanced use cases like abandonment recovery, dynamic delays, and more. -->
 
 For example:
 

src/engage/journeys/v2/limits.md

@@ -14,17 +14,17 @@ 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. |
 
 
 ## Throughput
 
-| Name                      | Limit                              | Description                                                                                                                 |
-| ------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| 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.                                                             |
+| Name                      | Limit                   | Description                                                                                                                     |
+| ------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| 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.                                                                               |
+| 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