From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Wed, 7 Sep 2022 00:49:15 +0000 (-0400)
Subject: changelog fixes
X-Git-Tag: rel_1_4_41~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1ce530c0b25bc8a7d09b97bf300aba55d2603892;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

changelog fixes

Change-Id: Ie0217dfea32d08abf7934950b1e1b381e612bb56
---

diff --git a/doc/build/changelog/unreleased_14/8446.rst b/doc/build/changelog/unreleased_14/8446.rst
index 9f4cdfddd6..7366315a93 100644
--- a/doc/build/changelog/unreleased_14/8446.rst
+++ b/doc/build/changelog/unreleased_14/8446.rst
@@ -1,5 +1,5 @@
 .. change::
-    :tags: bug, ext
+    :tags: bug, orm
     :tickets: 8446
 
     Fixed issue in :mod:`sqlalchemy.ext.mutable` extension where collection
diff --git a/doc/build/changelog/unreleased_14/8456.rst b/doc/build/changelog/unreleased_14/8456.rst
index ca769fd342..6f0e846510 100644
--- a/doc/build/changelog/unreleased_14/8456.rst
+++ b/doc/build/changelog/unreleased_14/8456.rst
@@ -6,7 +6,7 @@
     query placed as a subquery within an enclosing query for that same entity
     would fail to render the JOIN correctly for the inner query. The issue
     manifested in two different ways prior and subsequent to version 1.4.18
-    (related issue #6595), in one case rendering JOIN twice, in the other
-    losing the JOIN entirely. To resolve, the conditions under which
+    (related issue :ticket:`6595`), in one case rendering JOIN twice, in the
+    other losing the JOIN entirely. To resolve, the conditions under which
     "polymorphic loading" are applied have been scaled back to not be invoked
     for simple joined inheritance queries.
diff --git a/doc/build/changelog/unreleased_14/8475.rst b/doc/build/changelog/unreleased_14/8475.rst
index 22fc3f2dd6..bec64c6a4a 100644
--- a/doc/build/changelog/unreleased_14/8475.rst
+++ b/doc/build/changelog/unreleased_14/8475.rst
@@ -3,6 +3,6 @@
     :tickets: 8475
 
     Fixed regression caused by the fix for :ticket:`8231` released in 1.4.40
-    where connection would fail if the user does not have permission to query
-    the dm_exec_sessions or dm_pdw_nodes_exec_sessions system view when trying
-    to determine the current transaction isolation level.
+    where connection would fail if the user did not have permission to query
+    the ``dm_exec_sessions`` or ``dm_pdw_nodes_exec_sessions`` system views
+    when trying to determine the current transaction isolation level.