From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 12 Oct 2023 20:36:57 +0000 (-0400)
Subject: changelog fix
X-Git-Tag: rel_2_0_22~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=489f059853539fb6185d0613c68e21f205a3ec79;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

changelog fix

Change-Id: I50b42d61fbfc728f77d15411e41b04df9e0dd766
---

diff --git a/doc/build/changelog/unreleased_20/10459.rst b/doc/build/changelog/unreleased_20/10459.rst
index 8c2cb0d47c..97553ba733 100644
--- a/doc/build/changelog/unreleased_20/10459.rst
+++ b/doc/build/changelog/unreleased_20/10459.rst
@@ -9,9 +9,9 @@
     internally when the returned values were not actually hashable. The
     behavior is repaired to test the objects as they are received for
     hashability in this case, raising an informative error message if not. Note
-    that for values of "known unhashability", such as when the :class:`.JSON`
-    or :class:`.ARRAY` types are used directly, an informative error message
-    was already raised.
+    that for values of "known unhashability", such as when the
+    :class:`_types.JSON` or :class:`_types.ARRAY` types are used directly, an
+    informative error message was already raised.
 
     The "hashabiltiy testing" fix here is applied to legacy :class:`.Query` as
     well, however in the legacy case, :meth:`_engine.Result.unique` is used for