diff --git a/README.md b/README.md
index 5252f93370..3f88b2fa57 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ entire test with a note (e.g. *Removed*).
 
 ## Building Documents
 
-We use [mkdocs](https://www.mkdocs.org/) to render the documentation.  To see a live view of the documentation, run:
+We use [mkdocs](https://www.mkdocs.org/) to render the documentation. To see a live view of the documentation, run:
 
 ```bash
 pip install mkdocs
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 b1179698c5..9107efb251 100644
--- a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md
+++ b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.md
@@ -1265,8 +1265,8 @@ longer full, it is immediately filled. It is not a favorable situation to be in,
 guarantee that the waitQueue normally provides.
 
 Because of these issues, it does not make sense to
-[go against driver mantras and provide an additional knob](../driver-mantras.md#). We may eventually pursue an alternative
-configurations to address wait queue size in [Advanced Pooling Behaviors](#advanced-pooling-behaviors).
+[go against driver mantras and provide an additional knob](../driver-mantras.md#). We may eventually pursue an
+alternative configurations to address wait queue size in [Advanced Pooling Behaviors](#advanced-pooling-behaviors).
 
 Users that wish to have this functionality can achieve similar results by utilizing other methods to limit concurrency.
 Examples include implementing either a thread pool or an operation queue with a capped size in the user application.
diff --git a/source/driver-mantras.md b/source/driver-mantras.md
index 467f741dd2..bf52c62f0a 100644
--- a/source/driver-mantras.md
+++ b/source/driver-mantras.md
@@ -66,4 +66,4 @@ Drivers should follow X.Y.Z versioning, where breaking API changes require a bum
 
 Backward breaking behavior changes can be more dangerous and disruptive than backward breaking API changes. When
 thinking about the implications of a behavior change, ask yourself what could happen if a user upgraded your library
-without carefully reading the changelog and/or adequately testing the change.
\ No newline at end of file
+without carefully reading the changelog and/or adequately testing the change.