Fix many typos throughout the codebasepr/85

Found using: https://github.com/intgr/topy

6 files changed, 8 insertions, 8 deletions

diff --git a/doc/build/core/constraints.rst b/doc/build/core/constraints.rst
index 1f2761125..554d003bb 100644
--- a/doc/build/core/constraints.rst
+++ b/doc/build/core/constraints.rst
@@ -101,7 +101,7 @@ within a "CREATE TABLE" statement when
 :func:`~sqlalchemy.schema.MetaData.create_all` is issued, and
 :class:`~sqlalchemy.schema.ForeignKeyConstraint` invokes the "CONSTRAINT"
 keyword inline with "CREATE TABLE". There are some cases where this is
-undesireable, particularly when two tables reference each other mutually, each
+undesirable, particularly when two tables reference each other mutually, each
 with a foreign key referencing the other. In such a situation at least one of
 the foreign key constraints must be generated after both tables have been
 built. To support such a scheme, :class:`~sqlalchemy.schema.ForeignKey` and
@@ -424,7 +424,7 @@ name as follows::
 .. seealso::
 
     :paramref:`.MetaData.naming_convention` - for additional usage details
-    as well as a listing of all avaiable naming components.
+    as well as a listing of all available naming components.
 
     :ref:`alembic:tutorial_constraint_names` - in the Alembic documentation.
 
diff --git a/doc/build/core/event.rst b/doc/build/core/event.rst
index 1b873972a..e6f6c9e06 100644
--- a/doc/build/core/event.rst
+++ b/doc/build/core/event.rst
@@ -7,7 +7,7 @@ SQLAlchemy includes an event API which publishes a wide variety of hooks into
 the internals of both SQLAlchemy Core and ORM.
 
 .. versionadded:: 0.7
-    The system supercedes the previous system of "extension", "proxy",
+    The system supersedes the previous system of "extension", "proxy",
     and "listener" classes.
 
 Event Registration
diff --git a/doc/build/core/events.rst b/doc/build/core/events.rst
index 55dbc7bc4..d19b910b1 100644
--- a/doc/build/core/events.rst
+++ b/doc/build/core/events.rst
@@ -12,7 +12,7 @@ ORM events are described in :ref:`orm_event_toplevel`.
    :members:
 
 .. versionadded:: 0.7
-    The event system supercedes the previous system of "extension", "listener",
+    The event system supersedes the previous system of "extension", "listener",
     and "proxy" classes.
 
 Connection Pool Events
diff --git a/doc/build/core/reflection.rst b/doc/build/core/reflection.rst
index 952f48f74..57389cbec 100644
--- a/doc/build/core/reflection.rst
+++ b/doc/build/core/reflection.rst
@@ -149,7 +149,7 @@ includes but is not limited to:
 
 * The value of the ``.quote`` setting for :class:`.Column` or :class:`.Table`
 
-* The assocation of a particular :class:`.Sequence` with a given :class:`.Column`
+* The association of a particular :class:`.Sequence` with a given :class:`.Column`
 
 The relational database also in many cases reports on table metadata in a
 different format than what was specified in SQLAlchemy.   The :class:`.Table`
diff --git a/doc/build/core/tutorial.rst b/doc/build/core/tutorial.rst
index 585d9ceb2..22b903d28 100644
--- a/doc/build/core/tutorial.rst
+++ b/doc/build/core/tutorial.rst
@@ -119,7 +119,7 @@ We define our tables all within a catalog called
 :class:`~sqlalchemy.schema.Table` construct, which resembles regular SQL
 CREATE TABLE statements. We'll make two tables, one of which represents
 "users" in an application, and another which represents zero or more "email
-addreses" for each row in the "users" table:
+addresses" for each row in the "users" table:
 
 .. sourcecode:: pycon+sql
 
@@ -1510,7 +1510,7 @@ method:
     (4,)
     {stop}[(u'wendy', 2)]
 
-A common system of dealing with duplicates in composed SELECT statments
+A common system of dealing with duplicates in composed SELECT statements
 is the DISTINCT modifier.  A simple DISTINCT clause can be added using the
 :meth:`.Select.distinct` method:
 
diff --git a/doc/build/core/types.rst b/doc/build/core/types.rst
index b4781ee51..14e30e46d 100644
--- a/doc/build/core/types.rst
+++ b/doc/build/core/types.rst
@@ -426,7 +426,7 @@ meaning, in-place changes to values will not be detected and will not be
 flushed. Without further steps, you instead would need to replace the existing
 value with a new one on each parent object to detect changes. Note that
 there's nothing wrong with this, as many applications may not require that the
-values are ever mutated once created.  For those which do have this requirment,
+values are ever mutated once created.  For those which do have this requirement,
 support for mutability is best applied using the ``sqlalchemy.ext.mutable``
 extension - see the example in :ref:`mutable_toplevel`.