Fix docs typo: subuqery -> subquery

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

### Description
Fixes #5839
(sorry, realized just now that an issue wasn't required)

### 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 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: #5840
Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5840
Pull-request-sha: b6f6af929fab4dab771565f6373b0275acbca793

Change-Id: I0b4c9b2d893e8141ee1cd21742a9b111fe371bac

diff --git a/doc/build/core/operators.rst b/doc/build/core/operators.rst
index ac9633b77631a3f8f2b1884dfe3b1cb5338444d5..ef821c8d0474e1fe2e20838c8e49166b68d5befe 100644 (file)
--- a/doc/build/core/operators.rst
+++ b/doc/build/core/operators.rst
@@ -248,7 +248,7 @@ To illustrate the parameters rendered:
     [...] (1, 1, 2, 2){stop}
     [('spongebob',), ('sandy',)]
 
-Subuqery IN
+Subquery IN
 ~~~~~~~~~~~
 
 Finally, the :meth:`_sql.ColumnOperators.in_` and :meth:`_sql.ColumnOperators.not_in`

diff --git a/doc/build/orm/queryguide.rst b/doc/build/orm/queryguide.rst
index c7a0af717a8560dc0d7c4ed31aee1062ba3dca3a..faa1efdef685744e24a5272471fdacdd3ca542d1 100644 (file)
--- a/doc/build/orm/queryguide.rst
+++ b/doc/build/orm/queryguide.rst
@@ -361,7 +361,7 @@ construct, in a similar manner as discussed below in :ref:`orm_queryguide_subque
 
 The difference between using the :class:`_sql.TextualSelect` directly with
 :meth:`_sql.Select.from_statement` versus making use of :func:`_sql.aliased`
-is that in the former case, no subuqery is produced in the resulting SQL.
+is that in the former case, no subquery is produced in the resulting SQL.
 This can in some scenarios be advantageous from a performance or complexity
 perspective.
 

diff --git a/doc/build/tutorial/data.rst b/doc/build/tutorial/data.rst
index fe3b2c5ab0f4c31918805ea18f4e13bfa087bf7f..bc81cb027436ff2a7e4b5f53749537798045b356 100644 (file)
--- a/doc/build/tutorial/data.rst
+++ b/doc/build/tutorial/data.rst
@@ -1387,7 +1387,7 @@ Correlated Updates
 ~~~~~~~~~~~~~~~~~~
 
 An UPDATE statement can make use of rows in other tables by using a
-:ref:`correlated subquery <tutorial_scalar_subquery>`.  A subuqery may be used
+:ref:`correlated subquery <tutorial_scalar_subquery>`.  A subquery may be used
 anywhere a column expression might be placed::
 
   >>> scalar_subq = (