From 46fc12b1387d1d1fdd22ed63ae0fef787ffb3253 Mon Sep 17 00:00:00 2001 From: Valentin Kovalenko Date: Wed, 27 Nov 2024 07:15:09 -0700 Subject: [PATCH] Fix formatting DRIVERS-3056 --- .../connection-monitoring-and-pooling.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md index 805745651f..9ff8e788ef 100644 --- a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md +++ b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md @@ -244,10 +244,10 @@ A concept that represents pending requests for [Connections](#connection). When either receives a [Connection](#connection) or times out. A WaitQueue has the following traits: - **Thread-Safe**: When multiple threads attempt to enter or exit a WaitQueue, they do so in a thread-safe manner. -- **Ordered/fair**: When [Connections](#connection) are made available, they SHOULD be issued out to - threads in the order that the threads entered the WaitQueue. If this is behavior poses too much of an implementation - burden, then at the very least threads that have entered the queue more recently MUST NOT be intentionally - prioritized over those that entered it earlier. +- **Ordered/fair**: When [Connections](#connection) are made available, they SHOULD be issued out to threads in the + order that the threads entered the WaitQueue. If this is behavior poses too much of an implementation burden, then + at the very least threads that have entered the queue more recently MUST NOT be intentionally prioritized over those + that entered it earlier. - **Timeout aggressively:** Members of a WaitQueue MUST timeout if they are enqueued for longer than the computed timeout and MUST leave the WaitQueue immediately in this case.