From: Stefanie Molin <24376333+stefmolin@users.noreply.github.com>
Date: Fri, 6 Oct 2023 13:39:41 +0000 (-0400)
Subject: Fix typos in pooling docs
X-Git-Tag: rel_2_0_22~14
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=21ab9c62792013041c3e8f87eecbf8b6dd5b2bd4;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

Fix typos in pooling docs

<!-- Provide a general summary of your proposed changes in the Title field above -->

### Description
<!-- Describe your changes in detail -->
- fixed typo in pooling doc that mentioned three items but had a list of 4
- fixed typo "whish" to "wish" in pooling doc

### Checklist
<!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once)

-->

This pull request is:

- [x] A documentation / typographical / small typing error fix
	- Good to go, no issue or tests are needed
- [ ] A short code fix
	- please include the issue number, and create an issue if none exists, which
	  must include a complete example of the issue.  one line code fixes without an
	  issue and demonstration will not be accepted.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.   one line code fixes without tests will not be accepted.
- [ ] A new feature implementation
	- please include the issue number, and create an issue if none exists, which must
	  include a complete example of how the feature would look.
	- Please include: `Fixes: #<issue number>` in the commit message
	- please include tests.

**Have a nice day!**

Closes: #10411
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/10411
Pull-request-sha: 652ead00466ce2e85bdc2a62f7c69c16da6bb4fc

Change-Id: Ia5f2c5abfb0d76b5222aa883473291bba6df6de0
---

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`::