Fix many spell glitches

This affects mostly docstrings, except in orm/events.py::dispose_collection()
where one parameter gets renamed: given that the method is
empty, it seemed reasonable to me to fix that too.

Closes: #4440
Pull-request: #4440
Pull-request-sha: 779ed75

Change-Id: Ic0553fe97853054b09c2453af76d96363de6eb0e
(cherry picked from commit 66e88d3)

README.dialects.rst

@@ -192,7 +192,7 @@ Going Forward
 ==============
 
 The third-party dialect can be distributed like any other Python
-module on Pypi. Links to prominent dialects can be featured within
+module on PyPI. Links to prominent dialects can be featured within
 SQLAlchemy's own documentation; contact the developers (see AUTHORS)
 for help with this.
 

doc/build/changelog/changelog_01.rst

@@ -237,7 +237,7 @@
       created for a class, qualified by the entity name. instances of those classes
       will issue all of their load and save operations through their
       entity_name-qualified mapper, and maintain separate a identity in the identity
-      map for an otherwise equilvalent object.
+      map for an otherwise equivalent object.
 
     .. change::
         :tags: 
@@ -877,7 +877,7 @@
         :tags: 
         :tickets: 
 
-      began to implement newer logic in object properities.  you can now say
+      began to implement newer logic in object properties.  you can now say
       myclass.attr.property, which will give you the PropertyLoader corresponding to that
       attribute, i.e. myclass.mapper.props['attr']
 
@@ -943,7 +943,7 @@
         :tickets: 
 
       fix to engine.process_defaults so it works correctly with a table that has
-      different column name/column keys (changset 982)
+      different column name/column keys (changeset 982)
 
     .. change::
         :tags: 

doc/build/changelog/changelog_02.rst

@@ -223,7 +223,7 @@
         :tags:
         :tickets:
 
-      modifcation to unitofwork to not maintain ordering within the
+      modification to unitofwork to not maintain ordering within the
       "new" list or within the UOWTask "objects" list; instead, new objects
       are tagged with an ordering identifier as they are registered as new
       with the session, and the INSERT statements are then sorted within the
@@ -949,7 +949,7 @@
         :tags:
         :tickets:
 
-      fixes to session cascade behavior, entity_name propigation
+      fixes to session cascade behavior, entity_name propagation
 
     .. change::
         :tags:
@@ -1098,7 +1098,7 @@
 
       overhaul to Schema to build upon MetaData object instead of an Engine.
       Entire SQL/Schema system can be used with no Engines whatsoever, executed
-      solely by an explicit Connection object.  the "bound" methodlogy exists via the
+      solely by an explicit Connection object.  the "bound" methodology exists via the
       BoundMetaData for schema objects.  ProxyEngine is generally not needed
       anymore and is replaced by DynamicMetaData.
 
@@ -1143,7 +1143,7 @@
         :tickets:
 
       backrefs create themselves against primary mapper of its originating
-      property, priamry/secondary join arguments can be specified to override.
+      property, primary/secondary join arguments can be specified to override.
       helps their usage with polymorphic mappers
 
     .. change::

doc/build/changelog/changelog_03.rst

@@ -167,7 +167,7 @@
         :tags: sql
         :tickets: 667
 
-      foreign key specs can have any chararcter in their identifiers
+      foreign key specs can have any character in their identifiers
 
     .. change::
         :tags: sql
@@ -1167,7 +1167,7 @@
       and the key will be shared.  proper positional/named args translate
       at compile time.  for the old behavior of "aliasing" bind parameters
       with conflicting names, specify "unique=True" - this option is
-      still used internally for all the auto-genererated (value-based)
+      still used internally for all the auto-generated (value-based)
       bind parameters.
 
     .. change::
@@ -1379,7 +1379,7 @@
         :tickets: 
 
       some fixes to relationship calcs when using "viewonly=True" to pull
-      in other tables into the join condition which arent parent of the
+      in other tables into the join condition which aren't parent of the
       relationship's parent/child mappings
 
     .. change::
@@ -1508,7 +1508,7 @@
       the value of "case_sensitive" defaults to True now, regardless of the
       casing of the identifier, unless specifically set to False. this is
       because the object might be label'ed as something else which does
-      contain mixed case, and propigating "case_sensitive=False" breaks that.
+      contain mixed case, and propagating "case_sensitive=False" breaks that.
       Other fixes to quoting when using labels and "fake" column objects
 
     .. change::
@@ -2622,7 +2622,7 @@
       index=True/unique=False creates a plain Index,
       index=True/unique=True on Column creates a unique Index.  'index'
       and 'unique' keyword arguments to column are now boolean only; for
-      explcit names and groupings of indexes or unique constraints, use the
+      explicit names and groupings of indexes or unique constraints, use the
       UniqueConstraint/Index constructs explicitly.
 
     .. change::
@@ -2645,7 +2645,7 @@
         :tickets: 
 
       fixed condition that occurred during reflection when a primary key
-      column was explciitly overridden, where the PrimaryKeyConstraint would
+      column was explicitly overridden, where the PrimaryKeyConstraint would
       get both the reflected and the programmatic column doubled up
 
     .. change::

doc/build/changelog/changelog_04.rst

@@ -266,7 +266,7 @@
         :tickets: 1036
 
       repaired single table inheritance such that you
-      can single-table inherit from a joined-table inherting
+      can single-table inherit from a joined-table inheriting
       mapper without issue.
 
     .. change::
@@ -674,7 +674,7 @@
           whether or not it remains attached to its also-deleted
           parent.
 
-        - delete-orphan casacde is properly detected on relations
+        - delete-orphan cascade is properly detected on relations
           that are present on superclasses when using inheritance.
 
     .. change::
@@ -2300,7 +2300,7 @@
 
       MSSQL
        - PyODBC no longer has a global "set nocount on".
-       - Fix non-identity integer PKs on autload
+       - Fix non-identity integer PKs on autoload
        - Better support for convert_unicode
        - Less strict date conversion for pyodbc/adodbapi
        - Schema-qualified tables / autoload
@@ -2712,7 +2712,7 @@
         :tickets: 
 
       Renamed the Dialect attribute 'preexecute_sequences' to
-      'preexecute_pk_sequences'.  An attribute porxy is in place for
+      'preexecute_pk_sequences'.  An attribute proxy is in place for
       out-of-tree dialects using the old name.
 
     .. change::
@@ -3415,7 +3415,7 @@
         :tickets: 
 
       Hooks added throughout base/sql/defaults to optimize the calling of bind
-      aram/result processors so that method call overhead is minimized.
+      param/result processors so that method call overhead is minimized.
 
     .. change::
         :tags: 
@@ -4080,7 +4080,7 @@
         :tags: metadata
         :tickets: 
 
-      Added "explcit" create/drop/execute support for sequences (i.e. you can
+      Added "explicit" create/drop/execute support for sequences (i.e. you can
       pass a "connectable" to each of those methods on Sequence).
 
     .. change::

doc/build/changelog/changelog_05.rst

@@ -599,7 +599,7 @@
 
       Fixed Query being able to join() from individual columns of a
       joined-table subclass entity, i.e.  query(SubClass.foo,
-      SubcClass.bar).join(<anything>).  In most cases, an error
+      SubClass.bar).join(<anything>).  In most cases, an error
       "Could not find a FROM clause to join from" would be
       raised. In a few others, the result would be returned in terms
       of the base class rather than the subclass - so applications
@@ -786,7 +786,7 @@
         the AttributeExtension interface nor any of the publicly
         documented attribute functions.
 
-      - The unit of work no longer genererates a graph of "dependency"
+      - The unit of work no longer generates a graph of "dependency"
         processors for the full graph of mappers during flush(), instead
         creating such processors only for those mappers which represent
         objects with pending changes.  This saves a tremendous number
@@ -1172,7 +1172,7 @@
 
       Query won't fail with weakref error when a non-mapper/class
       instrumented descriptor is passed, raises
-      "Invalid column expession".
+      "Invalid column expression".
 
     .. change::
         :tags: orm
@@ -1443,7 +1443,7 @@
         :tickets: 1237, 781
 
       Added a new `relation()` keyword `back_populates`. This
-      allows configuation of backreferences using explicit
+      allows configuration of backreferences using explicit
       relations. This is required when creating
       bidirectional relations between a hierarchy of concrete
       mappers and another class.
@@ -1470,7 +1470,7 @@
 
       Added a rudimental series of set operations to Query that
       receive Query objects as arguments, including union(),
-      union_all(), intersect(), except_(), insertsect_all(),
+      union_all(), intersect(), except_(), intersect_all(),
       except_all().  See the API documentation for
       Query.union() for examples.
 
@@ -1525,7 +1525,7 @@
       Using delete-orphan on a many-to-many relation is deprecated.
       This produces misleading or erroneous results since SQLA does
       not retrieve the full list of "parents" for m2m.  To get delete-orphan
-      behavior with an m2m table, use an explcit association class
+      behavior with an m2m table, use an explicit association class
       so that the individual association row is treated as a parent.
 
     .. change::
@@ -2651,7 +2651,7 @@
       Added more granularity to internal attribute access, such that
       cascade and flush operations will not initialize unloaded
       attributes and collections, leaving them intact for a
-      lazy-load later on. Backref events still initialize attrbutes
+      lazy-load later on. Backref events still initialize attributes
       and collections for pending instances.
 
     .. change::

doc/build/changelog/changelog_06.rst

@@ -524,7 +524,7 @@
       cleanup() were not explicitly closed, leaving garbage
       collection to the task instead.   This generally only
       affects non-reference-counting backends like Jython
-      and Pypy.  Thanks to Jaimy Azle for spotting
+      and PyPy.  Thanks to Jaimy Azle for spotting
       this.
 
     .. change::
@@ -1309,7 +1309,7 @@
       @classproperty 's official name/location for usage
       with declarative is sqlalchemy.ext.declarative.declared_attr.
       Same thing, but moving there since it is more of a
-      "marker" that's specific to declararative,
+      "marker" that's specific to declarative,
       not just an attribute technique.
 
     .. change::
@@ -1390,7 +1390,7 @@
         :tags: oracle
         :tickets: 1878
 
-      The implicit_retunring argument to create_engine()
+      The implicit_returning argument to create_engine()
       is now honored regardless of detected version of
       Oracle.  Previously, the flag would be forced
       to False if server version info was < 10.
@@ -1477,7 +1477,7 @@
       Added a mutex to the identity map which mutexes
       remove operations against iteration methods,
       which now pre-buffer before returning an
-      iterable.   This because asyncrhonous gc
+      iterable.   This because asynchronous gc
       can remove items via the gc thread at any time.
 
     .. change::
@@ -2479,7 +2479,7 @@
         :tags: sql
         :tickets: 1571
 
-      Fixed "table" argument on constructor of ForeginKeyConstraint
+      Fixed "table" argument on constructor of ForeignKeyConstraint
 
     .. change::
         :tags: sql
@@ -5368,7 +5368,7 @@
       session, using autocommit=False, autoflush=True. Default
       behavior of SQLSoup now requires the usual usage of commit()
       and rollback(), which have been added to its interface. An
-      explcit Session or scoped_session can be passed to the
+      explicit Session or scoped_session can be passed to the
       constructor, allowing these arguments to be overridden.
 
     .. change::

doc/build/changelog/changelog_07.rst

@@ -586,7 +586,7 @@
 
       Fixed compiler bug whereby using a correlated
       subquery within an ORDER BY would fail to render correctly
-      if the stament also used LIMIT/OFFSET, due to mis-rendering
+      if the statement also used LIMIT/OFFSET, due to mis-rendering
       within the ROW_NUMBER() OVER clause.  Fix courtesy
       sayap
 
@@ -3790,7 +3790,7 @@
         :tags: general
         :tickets:
 
-      Lots of fixes to unit tests when run under Pypy
+      Lots of fixes to unit tests when run under PyPy
       (courtesy Alex Gaynor).
 
     .. change::

doc/build/changelog/changelog_08.rst

@@ -93,7 +93,7 @@
         :tickets: 3044
 
         Fixed bug in INSERT..FROM SELECT construct where selecting from a
-        UNION would wrap the union in an anonymous (e.g. unlabled) subquery.
+        UNION would wrap the union in an anonymous (e.g. unlabeled) subquery.
 
     .. change::
         :tags: bug, postgresql
@@ -249,7 +249,7 @@
         Fixed bug in :func:`.tuple_` construct where the "type" of essentially
         the first SQL expression would be applied as the "comparison type"
         to a compared tuple value; this has the effect in some cases of an
-        inappropriate "type coersion" occurring, such as when a tuple that
+        inappropriate "type coercion" occurring, such as when a tuple that
         has a mix of String and Binary values improperly coerces target
         values to Binary even though that's not what they are on the left
         side.  :func:`.tuple_` now expects heterogeneous types within its
@@ -827,7 +827,7 @@
         by the database (such as PostgreSQL ``oid`` or ``xmin``).  The
         column will be omitted from the ``CREATE TABLE`` statement but will
         otherwise be available for querying.   In addition, the
-        :class:`.CreateColumn` construct can be appled to a custom
+        :class:`.CreateColumn` construct can be applied to a custom
         compilation rule which allows skipping of columns, by producing
         a rule that returns ``None``.
 
@@ -848,7 +848,7 @@
 
         Fixed a potential issue in an ordered sequence implementation used
         by the ORM to iterate mapper hierarchies; under the Jython interpreter
-        this implementation wasn't ordered, even though cPython and Pypy
+        this implementation wasn't ordered, even though cPython and PyPy
         maintained ordering.
 
     .. change::
@@ -1933,7 +1933,7 @@
       custom collections using an ``__instrumentation__`` datastructure
       associated with the collection has been removed, as this was a complex
       and untested feature which was also essentially redundant versus the
-      decorator approach.   Other internal simplifcations to the
+      decorator approach.   Other internal simplifications to the
       orm.collections module have been made as well.
 
     .. change::
@@ -2665,7 +2665,7 @@
       UPDATE..FROM syntax as allowed by the dialect
       to satisfy the WHERE clause.  MySQL's multi-table
       update feature is also supported if columns
-      are specified by object in the "values" dicitionary.
+      are specified by object in the "values" dictionary.
       PG's DELETE..USING is also not available
       in Core yet.
 
@@ -3183,7 +3183,7 @@
         :tags: feature, sql
         :tickets:
 
-      The Core oeprator system now includes
+      The Core operator system now includes
       the `getitem` operator, i.e. the bracket
       operator in Python.  This is used at first
       to provide index and slice behavior to the