diff --git a/source/transactions-convenient-api/transactions-convenient-api.md b/source/transactions-convenient-api/transactions-convenient-api.md
index 025fe4a939..b4d4a16124 100644
--- a/source/transactions-convenient-api/transactions-convenient-api.md
+++ b/source/transactions-convenient-api/transactions-convenient-api.md
@@ -396,7 +396,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.