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: https://github.com/sqlalchemy/sqlalchemy/pull/4440
Pull-request-sha: 779ed75acb6142e1f1daac467b5b14134529bb4b

Change-Id: Ic0553fe97853054b09c2453af76d96363de6eb0e

1 files changed, 4 insertions, 4 deletions

diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index d9555b196..07c0017b9 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -857,7 +857,7 @@ class Table(DialectKWArgs, SchemaItem, TableClause):
 
             m1 = MetaData()
 
-            user = Table('user', m1, Column('id', Integer, priamry_key=True))
+            user = Table('user', m1, Column('id', Integer, primary_key=True))
 
             m2 = MetaData()
             user_copy = user.tometadata(m2)
@@ -1494,7 +1494,7 @@ class Column(DialectKWArgs, SchemaItem, ColumnClause):
             event.listen(self, "after_parent_attach", fn)
 
     def copy(self, **kw):
-        """Create a copy of this ``Column``, unitialized.
+        """Create a copy of this ``Column``, uninitialized.
 
         This is used in ``Table.tometadata``.
 
@@ -4028,7 +4028,7 @@ class MetaData(SchemaItem):
             automatic resolution of dependency cycles between tables, which
             are usually caused by mutually dependent foreign key constraints.
             To resolve these cycles, either the
-            :paramref:`.ForeignKeyConstraint.use_alter` parameter may be appled
+            :paramref:`.ForeignKeyConstraint.use_alter` parameter may be applied
             to those constraints, or use the
             :func:`.schema.sort_tables_and_constraints` function which will
             break out foreign key constraints involved in cycles separately.
@@ -4074,7 +4074,7 @@ class MetaData(SchemaItem):
           the existing bind on this ``MetaData``, if any.
 
         :param schema:
-          Optional, query and reflect tables from an alterate schema.
+          Optional, query and reflect tables from an alternate schema.
           If None, the schema associated with this :class:`.MetaData`
           is used, if any.