Transactions convenient api alignment (mongodb#1898)

Author: tadjik1

source/transactions-convenient-api/transactions-convenient-api.md

@@ -416,7 +416,7 @@ Previously, the driver would retry transactions immediately, which is fine for l
 server load increases, immediate retries can result in retry storms, unnecessarily further overloading the server.
 
 Exponential backoff is well-researched and accepted backoff strategy that is simple to implement. A low initial backoff
-(1-millisecond) and growth value (1.25x) were chosen specifically to mitigate latency in low levels of contention.
+(5-milliseconds) and growth value (1.5x) were chosen specifically to mitigate latency in low levels of contention.
 Empirical evidence suggests that 500-millisecond max backoff ensured that a transaction did not wait so long as to
 exceed the 120-second timeout and reduced load spikes.
 
@@ -439,6 +439,8 @@ provides an implementation of a technique already described in the MongoDB 4.0 d
 
 ## Changelog
 
+- 2026-02-20: Fix initial backoff and growth value parameters in "Design Rationale" section.
+
 - 2026-02-17: Clarify expected error when timeout is reached
     [DRIVERS-3391](https://jira.mongodb.org/browse/DRIVERS-3391).