From 652ead00466ce2e85bdc2a62f7c69c16da6bb4fc Mon Sep 17 00:00:00 2001
From: Stefanie Molin <24376333+stefmolin@users.noreply.github.com>
Date: Tue, 3 Oct 2023 10:17:16 -0400
Subject: [PATCH] Fix typos in pooling docs

---
 doc/build/core/pooling.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/build/core/pooling.rst b/doc/build/core/pooling.rst
index 8e7f1592d0..78bbdcb1af 100644
--- a/doc/build/core/pooling.rst
+++ b/doc/build/core/pooling.rst
@@ -584,7 +584,7 @@ typically the most common).
 The SQLAlchemy :class:`_engine.Engine` object refers to a connection pool of existing
 database connections.  So when this object is replicated to a child process,
 the goal is to ensure that no database connections are carried over.  There
-are three general approaches to this:
+are four general approaches to this:
 
 1. Disable pooling using :class:`.NullPool`.  This is the most simplistic,
    one shot system that prevents the :class:`_engine.Engine` from using any connection
@@ -687,7 +687,7 @@ Using a pool instance directly
 ------------------------------
 
 A pool implementation can be used directly without an engine. This could be used
-in applications that just whish to use the pool behavior without all other
+in applications that just wish to use the pool behavior without all other
 SQLAlchemy features.
 In the example below the default pool for the ``MySQLdb`` dialect is obtained using
 :func:`_sa.create_pool_from_url`::
-- 
2.47.3