documentation fixes

Change-Id: I1f2e8376ce86886a9b35fa48cb7a78ca1735095c

diff --git a/docs/build/conf.py b/docs/build/conf.py
index 45995b3c37dc21ab699cb78d8d00da87ed79431f..75d91edc02a19c1c34184687a8e27bf30a4d2fc5 100644 (file)
--- a/docs/build/conf.py
+++ b/docs/build/conf.py
@@ -249,6 +249,6 @@ latex_documents = [
 autoclass_content = "both"
 
 intersphinx_mapping = {
-    "sqla": ("http://www.sqlalchemy.org/docs/", None),
+    "sqla": ("https://docs.sqlalchemy.org/en/latest/", None),
     "python": ("http://docs.python.org/", None),
 }

diff --git a/docs/build/cookbook.rst b/docs/build/cookbook.rst
index 4277ad1c91f067f0189e7269d82c963494e8689f..611b4548f2652e5fdea96e7c1b48f7b5efb450ef 100644 (file)
--- a/docs/build/cookbook.rst
+++ b/docs/build/cookbook.rst
@@ -827,6 +827,7 @@ schema or another.
             __table_args__ = {
                 "schema": None
             }
+
    ..
 
 2. The :paramref:`.EnvironmentContext.configure.include_schemas` flag must

diff --git a/docs/build/unreleased/748.rst b/docs/build/unreleased/748.rst
index 9e20003f7713606b7f5a7e178a026db3df88150b..b4ee377cf4eb21abf455fef5fdaf49f344e8ee8b 100644 (file)
--- a/docs/build/unreleased/748.rst
+++ b/docs/build/unreleased/748.rst
@@ -1,6 +1,6 @@
 .. change::
-    :tags: change
-    :tickets: 711
+    :tags: changed
+    :tickets: 748
 
     Alembic 1.5.0 now supports **Python 2.7 and Python 3.6 and above**, as well
     as **SQLAlchemy 1.3.0 and above**.  Support is removed for Python 3

diff --git a/docs/build/unreleased/autocommit.rst b/docs/build/unreleased/autocommit.rst
index 39d6098537d4a5f2bce555422e33bb9cec3dd277..61ba5be91f7f2ef4247888bab9c1f0de2de1f7f8 100644 (file)
--- a/docs/build/unreleased/autocommit.rst
+++ b/docs/build/unreleased/autocommit.rst
@@ -1,21 +1,21 @@
 .. change::
-       :tags: change, environment
+    :tags: changed, environment
 
-       To accommodate SQLAlchemy 1.4 and 2.0, the migration model now no longer
-       assumes that the SQLAlchemy Connection will autocommit an individual
-       operation.   This essentially means that for databases that use
-       non-transactional DDL (pysqlite current driver behavior, MySQL), there is
-       still a BEGIN/COMMIT block that will surround each individual migration.
-       Databases that support transactional DDL should continue to have the
-       same flow, either per migration or per-entire run, depending on the
-       value of the :paramref:`.Environment.configure.transaction_per_migration`
-       flag.
+    To accommodate SQLAlchemy 1.4 and 2.0, the migration model now no longer
+    assumes that the SQLAlchemy Connection will autocommit an individual
+    operation.   This essentially means that for databases that use
+    non-transactional DDL (pysqlite current driver behavior, MySQL), there is
+    still a BEGIN/COMMIT block that will surround each individual migration.
+    Databases that support transactional DDL should continue to have the
+    same flow, either per migration or per-entire run, depending on the
+    value of the :paramref:`.Environment.configure.transaction_per_migration`
+    flag.
 
 
 .. change::
-       :tags: change, environment
+    :tags: changed, environment
 
-       It now raises a :class:`.CommandError` if a ``sqlalchemy.engine.Engine``
-       is passed to the :meth:`.MigrationContext.configure` method instead of
-       a ``sqlalchemy.engine.Connection`` object.  Previously, this would
-       be a warning only.
\ No newline at end of file
+    A :class:`.CommandError` is raised if a ``sqlalchemy.engine.Engine`` is
+    passed to the :meth:`.MigrationContext.configure` method instead of a
+    ``sqlalchemy.engine.Connection`` object.  Previously, this would be a
+    warning only.
\ No newline at end of file