diff --git a/src/engage/journeys/v2/limits.md b/src/engage/journeys/v2/limits.md
index ab0269f8d0..88ebe3551c 100644
--- a/src/engage/journeys/v2/limits.md
+++ b/src/engage/journeys/v2/limits.md
@@ -9,7 +9,7 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.
 
 | Name                | Limit                                   | Description                                                                                                                |
 | ------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Steps               | 25                                      | Maximum number of steps per journey.                                                                                       |
+| Steps               | 50                                      | Maximum number of steps per journey.                                                                                       |
 | Journey name        | 73 characters                           | Maximum length for Journey names. Names must be unique.                                                                    |
 | 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.                       |
@@ -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:friends@segment.com).
\ No newline at end of file
+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:friends@segment.com).