fix doc warnings

Change-Id: I38e465ef1902584c3242bb06ed5ed18a8c018285

diff --git a/doc/build/changelog/migration_14.rst b/doc/build/changelog/migration_14.rst
index 1c588f018ed00d79a0ba7eac2a1a51df3ce79998..ac6cb6a5354d7951d06b6a973f3e8f171d179c09 100644 (file)
--- a/doc/build/changelog/migration_14.rst
+++ b/doc/build/changelog/migration_14.rst
@@ -2359,7 +2359,7 @@ to be more noticeable.
 
 :ticket:`1763`
 
-.. _change_8879
+.. _change_8879:
 
 Column loaders such as ``deferred()``, ``with_expression()`` only take effect when indicated on the outermost, full entity query
 --------------------------------------------------------------------------------------------------------------------------------

diff --git a/doc/build/changelog/unreleased_14/9075.rst b/doc/build/changelog/unreleased_14/9075.rst
index 0d96be77088c089f5e7e707d96c0af853cad33ab..3263fa30be13f2394e5fc3fb087ae1f05e9e4a9d 100644 (file)
--- a/doc/build/changelog/unreleased_14/9075.rst
+++ b/doc/build/changelog/unreleased_14/9075.rst
@@ -5,14 +5,14 @@
 
     Fixed bug / regression where using :func:`.bindparam()` with the same name
     as a column in the :meth:`.Update.values` method of :class:`.Update`, as
-    well as the :meth:`.Insert.values` method of :class:`.Insert` in 2.0 only,
-    would in some cases silently fail to honor the SQL expression in which the
-    parameter were presented, replacing the expression with a new parameter of
-    the same name and discarding any other elements of the SQL expression, such
-    as SQL functions, etc. The specific case would be statements that were
-    constructed against ORM entities rather than plain :class:`.Table`
-    instances, but would occur if the statement were invoked with a
-    :class:`.Session` or a :class:`.Connection`.
+    well as the :meth:`_sql.Insert.values` method of :class:`_sql.Insert` in
+    2.0 only, would in some cases silently fail to honor the SQL expression in
+    which the parameter were presented, replacing the expression with a new
+    parameter of the same name and discarding any other elements of the SQL
+    expression, such as SQL functions, etc. The specific case would be
+    statements that were constructed against ORM entities rather than plain
+    :class:`.Table` instances, but would occur if the statement were invoked
+    with a :class:`.Session` or a :class:`.Connection`.
 
     :class:`.Update` part of the issue was present in both 2.0 and 1.4 and is
     backported to 1.4.