fix most sphinx warnings (1.4)

still can't figure out the warnings with some of the older
changelog files.

this cherry-picks the sphinx fixes from 1.4 and additionally
fixes a small number of new issues in the 2.0 docs. However,
2.0 has many more errors to fix, primarily from the removal
of the legacy tutorials left behind a lot of labels that need
to be re-linked to the new tutorial.

Fixes: #7946
Change-Id: Id657ab23008eed0b133fed65b2f9ea75a626215c
(cherry picked from commit 9b55a423459236ca8a2ced713c9e93999dd18922)

2 files changed, 8 insertions, 9 deletions

diff --git a/lib/sqlalchemy/sql/schema.py b/lib/sqlalchemy/sql/schema.py
index 472979952..598bacc59 100644
--- a/lib/sqlalchemy/sql/schema.py
+++ b/lib/sqlalchemy/sql/schema.py
@@ -1450,7 +1450,7 @@ class Column(DialectKWArgs, SchemaItem, ColumnClause[_T]):
             value automatically for this column, which will be accessible
             after the statement is invoked via the
             :attr:`.CursorResult.inserted_primary_key` attribute upon the
-            :class:`.Result` object.   This also applies towards use of the
+            :class:`_result.Result` object.   This also applies towards use of the
             ORM when ORM-mapped objects are persisted to the database,
             indicating that a new integer primary key will be available to
             become part of the :term:`identity key` for that object.  This
@@ -1497,9 +1497,9 @@ class Column(DialectKWArgs, SchemaItem, ColumnClause[_T]):
                 Column('id', ForeignKey('other.id'),
                             primary_key=True, autoincrement='ignore_fk')
 
-            It is typically not desirable to have "autoincrement" enabled on a
-            column that refers to another via foreign key, as such a column is
-            required to refer to a value that originates from elsewhere.
+          It is typically not desirable to have "autoincrement" enabled on a
+          column that refers to another via foreign key, as such a column is
+          required to refer to a value that originates from elsewhere.
 
           The setting has these effects on columns that meet the
           above criteria:
@@ -1537,9 +1537,9 @@ class Column(DialectKWArgs, SchemaItem, ColumnClause[_T]):
             using a method specific to the database driver in use:
 
             * MySQL, SQLite - calling upon ``cursor.lastrowid()``
-             (see
-             `https://www.python.org/dev/peps/pep-0249/#lastrowid
-             <https://www.python.org/dev/peps/pep-0249/#lastrowid>`_)
+              (see
+              `https://www.python.org/dev/peps/pep-0249/#lastrowid
+              <https://www.python.org/dev/peps/pep-0249/#lastrowid>`_)
             * PostgreSQL, SQL Server, Oracle - use RETURNING or an equivalent
               construct when rendering an INSERT statement, and then retrieving
               the newly generated primary key values after execution
@@ -1564,7 +1564,6 @@ class Column(DialectKWArgs, SchemaItem, ColumnClause[_T]):
             "fast insertmany" feature.  Such features are very new and
             may not yet be well covered in documentation.
 
-
         :param default: A scalar, Python callable, or
             :class:`_expression.ColumnElement` expression representing the
             *default value* for this column, which will be invoked upon insert
diff --git a/lib/sqlalchemy/sql/selectable.py b/lib/sqlalchemy/sql/selectable.py
index fd98f17e3..733def377 100644
--- a/lib/sqlalchemy/sql/selectable.py
+++ b/lib/sqlalchemy/sql/selectable.py
@@ -1078,7 +1078,7 @@ class SelectLabelStyle(Enum):
 
     Below, all column names are given a label so that the two same-named
     columns ``columna`` are disambiguated as ``table1_columna`` and
-    ``table2_columna`::
+    ``table2_columna``::
 
         >>> from sqlalchemy import table, column, select, true, LABEL_STYLE_TABLENAME_PLUS_COL
         >>> table1 = table("table1", column("columna"), column("columnb"))