From 1ec330eb1347ef97f0f21cbb66b9db2bbbf4248b Mon Sep 17 00:00:00 2001
From: Valentin Kovalenko <valentin.kovalenko@mongodb.com>
Date: Tue, 8 Aug 2023 16:30:35 -0600
Subject: [PATCH] Use "not greater than" consistently

DRIVERS-2469
---
 .../connection-monitoring-and-pooling.rst                       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst
index cea6ab4604..edaa73a099 100644
--- a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst
+++ b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst
@@ -1023,7 +1023,7 @@ See the `Load Balancer Specification <../load-balancers/load-balancers.rst#event
        * Naturally, if a new connection was not created (`ConnectionCreatedEvent`)
        * and established (`ConnectionReadyEvent`) as part of checking out,
        * this duration is usually
-       * smaller than or equal to `ConnectionPoolOptions.waitQueueTimeoutMS`,
+       * not greater than `ConnectionPoolOptions.waitQueueTimeoutMS`,
        * but MAY occasionally be greater than that,
        * because a driver does not provide hard real-time guarantees.
        *