changelog fix

Change-Id: I50b42d61fbfc728f77d15411e41b04df9e0dd766

diff --git a/doc/build/changelog/unreleased_20/10459.rst b/doc/build/changelog/unreleased_20/10459.rst
index 8c2cb0d47ce374bd16d2a8b479812fd72464c423..97553ba7332d9ad94087ad0109e7df3b7032fa83 100644 (file)
--- 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