Skip to content

Commit 50e502b

Browse files
committed
small edits
1 parent 7bd7662 commit 50e502b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/connection/connection-pools.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,12 @@ Connection Pools
1717
Overview
1818
--------
1919

20-
In this guide, you can learn about how {+driver-short+} uses connection pools to manage
20+
In this guide, you can learn about how the {+driver-short+} uses connection pools to manage
2121
connections to a MongoDB deployment and how you can configure connection pool settings
2222
in your application.
2323

24-
A connection pool is a cache of open database connections maintained by {+driver-short+}.
25-
When your application requests a connection to MongoDB, {+driver-short+} seamlessly
24+
A connection pool is a cache of open database connections maintained by the {+driver-short+}.
25+
When your application requests a connection to MongoDB, the {+driver-short+} seamlessly
2626
gets a connection from the pool, performs operations, and returns the connection
2727
to the pool for reuse.
2828

@@ -38,7 +38,7 @@ concurrent MongoDB operations in your multi-threaded application.
3838

3939
The ``maxPoolSize`` option sets the maximum size of each connection pool, which
4040
defaults to 100. If the number of in-use connections to a server reaches the
41-
value of maxPoolSize, the next request to that server will wait until a
41+
value of ``maxPoolSize``, the next request to that server will wait until a
4242
connection becomes available.
4343

4444
Each ``MongoClient`` instance opens two more sockets per server in your MongoDB

0 commit comments

Comments
 (0)