7 files changed, 11 insertions, 11 deletions
diff --git a/lib/sqlalchemy/dialects/mssql/base.py b/lib/sqlalchemy/dialects/mssql/base.py
index 051efa719..2f94d61ea 100644
--- a/lib/sqlalchemy/dialects/mssql/base.py
+++ b/lib/sqlalchemy/dialects/mssql/base.py
@@ -425,7 +425,7 @@ Compatibility Levels
 --------------------
 MSSQL supports the notion of setting compatibility levels at the
 database level. This allows, for instance, to run a database that
-is compatible with SQL2000 while running on a SQL2005 database
+is compatible with SQL2000 while running on an SQL2005 database
 server. ``server_version_info`` will always return the database
 server version information (in this case SQL2005) and not the
 compatibility level information. Because of this, if running under
diff --git a/lib/sqlalchemy/dialects/postgresql/base.py b/lib/sqlalchemy/dialects/postgresql/base.py
index eb3449e40..6c1909e1d 100644
--- a/lib/sqlalchemy/dialects/postgresql/base.py
+++ b/lib/sqlalchemy/dialects/postgresql/base.py
@@ -901,7 +901,7 @@ class ENUM(sqltypes.Enum):
          or :meth:`~.postgresql.ENUM.drop`
          are called directly.
          Setting to ``False`` is helpful
-         when invoking a creation scheme to a SQL file
+         when invoking a creation scheme to an SQL file
          without access to the actual database -
          the :meth:`~.postgresql.ENUM.create` and
          :meth:`~.postgresql.ENUM.drop` methods can
diff --git a/lib/sqlalchemy/dialects/postgresql/hstore.py b/lib/sqlalchemy/dialects/postgresql/hstore.py
index 67923fe39..ca8cffcd2 100644
--- a/lib/sqlalchemy/dialects/postgresql/hstore.py
+++ b/lib/sqlalchemy/dialects/postgresql/hstore.py
@@ -137,7 +137,7 @@ class HSTORE(sqltypes.Indexable, sqltypes.Concatenable, sqltypes.TypeEngine):
 
         def has_key(self, other):
             """Boolean expression.  Test for presence of a key.  Note that the
-            key may be a SQLA expression.
+            key may be an SQLA expression.
             """
             return self.operate(HAS_KEY, other, result_type=sqltypes.Boolean)
 
@@ -169,13 +169,13 @@ class HSTORE(sqltypes.Indexable, sqltypes.Concatenable, sqltypes.TypeEngine):
 
         def defined(self, key):
             """Boolean expression.  Test for presence of a non-NULL value for
-            the key.  Note that the key may be a SQLA expression.
+            the key.  Note that the key may be an SQLA expression.
             """
             return _HStoreDefinedFunction(self.expr, key)
 
         def delete(self, key):
             """HStore expression.  Returns the contents of this hstore with the
-            given key deleted.  Note that the key may be a SQLA expression.
+            given key deleted.  Note that the key may be an SQLA expression.
             """
             if isinstance(key, dict):
                 key = _serialize_hstore(key)
@@ -246,7 +246,7 @@ ischema_names['hstore'] = HSTORE
 
 
 class hstore(sqlfunc.GenericFunction):
-    """Construct an hstore value within a SQL expression using the
+    """Construct an hstore value within an SQL expression using the
     Postgresql ``hstore()`` function.
 
     The :class:`.hstore` function accepts one or two arguments as described
diff --git a/lib/sqlalchemy/dialects/postgresql/json.py b/lib/sqlalchemy/dialects/postgresql/json.py
index b0f0f7cf0..1791b49d5 100644
--- a/lib/sqlalchemy/dialects/postgresql/json.py
+++ b/lib/sqlalchemy/dialects/postgresql/json.py
@@ -242,7 +242,7 @@ class JSONB(JSON):
 
         def has_key(self, other):
             """Boolean expression.  Test for presence of a key.  Note that the
-            key may be a SQLA expression.
+            key may be an SQLA expression.
             """
             return self.operate(HAS_KEY, other, result_type=sqltypes.Boolean)
 
diff --git a/lib/sqlalchemy/dialects/postgresql/psycopg2.py b/lib/sqlalchemy/dialects/postgresql/psycopg2.py
index fe245b21d..046aa22a8 100644
--- a/lib/sqlalchemy/dialects/postgresql/psycopg2.py
+++ b/lib/sqlalchemy/dialects/postgresql/psycopg2.py
@@ -188,7 +188,7 @@ one of these characters in its name.  One is to specify the
     )
 
 Above, an INSERT statement such as ``measurement.insert()`` will use
-``size_meters`` as the parameter name, and a SQL expression such as
+``size_meters`` as the parameter name, and an SQL expression such as
 ``measurement.c.size_meters > 10`` will derive the bound parameter name
 from the ``size_meters`` key as well.
 
diff --git a/lib/sqlalchemy/dialects/sqlite/base.py b/lib/sqlalchemy/dialects/sqlite/base.py
index ddd869448..63f2d896f 100644
--- a/lib/sqlalchemy/dialects/sqlite/base.py
+++ b/lib/sqlalchemy/dialects/sqlite/base.py
@@ -16,7 +16,7 @@ Date and Time Types
 
 SQLite does not have built-in DATE, TIME, or DATETIME types, and pysqlite does
 not provide out of the box functionality for translating values between Python
-`datetime` objects and a SQLite-supported format. SQLAlchemy's own
+`datetime` objects and an SQLite-supported format. SQLAlchemy's own
 :class:`~sqlalchemy.types.DateTime` and related types provide date formatting
 and parsing functionality when SQlite is used. The implementation classes are
 :class:`~.sqlite.DATETIME`, :class:`~.sqlite.DATE` and :class:`~.sqlite.TIME`.
@@ -153,7 +153,7 @@ with an error.
 This behavior becomes more critical when used in conjunction with the
 SQLAlchemy ORM.  SQLAlchemy's :class:`.Session` object by default runs
 within a transaction, and with its autoflush model, may emit DML preceding
-any SELECT statement.   This may lead to a SQLite database that locks
+any SELECT statement.   This may lead to an SQLite database that locks
 more quickly than is expected.   The locking mode of SQLite and the pysqlite
 driver can be manipulated to some degree, however it should be noted that
 achieving a high degree of write-concurrency with SQLite is a losing battle.
diff --git a/lib/sqlalchemy/dialects/sqlite/pysqlite.py b/lib/sqlalchemy/dialects/sqlite/pysqlite.py
index 33d04deeb..9db4cebdf 100644
--- a/lib/sqlalchemy/dialects/sqlite/pysqlite.py
+++ b/lib/sqlalchemy/dialects/sqlite/pysqlite.py
@@ -37,7 +37,7 @@ Connect Strings
 ---------------
 
 The file specification for the SQLite database is taken as the "database"
-portion of the URL.  Note that the format of a SQLAlchemy url is::
+portion of the URL.  Note that the format of an SQLAlchemy url is::
 
     driver://user:pass@host/database