Fix some long lines that sneaked in with the spelling fixes change

Change-Id: Icc6d8e564c9d31da2adc39d060e077c3d4811186

2 files changed, 4 insertions, 4 deletions

diff --git a/lib/sqlalchemy/orm/query.py b/lib/sqlalchemy/orm/query.py
index 80d596b4c..f86cb9085 100644
--- a/lib/sqlalchemy/orm/query.py
+++ b/lib/sqlalchemy/orm/query.py
@@ -2842,8 +2842,8 @@ class Query(object):
         approach to the use case of applying an :func:`.aliased` construct
         explicitly throughout a query.  Instead of referring to the
         :func:`.aliased` construct explicitly,
-        :meth:`.Query.select_entity_from` automatically *adapts* all occurrences
-        of the entity to the target selectable.
+        :meth:`.Query.select_entity_from` automatically *adapts* all
+        occurrences of the entity to the target selectable.
 
         Given a case for :func:`.aliased` such as selecting ``User``
         objects from a SELECT statement::
diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index 07c0017b9..8997e119f 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -4028,8 +4028,8 @@ 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 applied
-            to those constraints, or use the
+            :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.