[3.12] gh-123207: Clarify the documentation for the mro lookup for super() (GH-123417...

(cherry picked from commit 327463aef173a1cb9659bccbecfff4530bbe6bbf)

Co-authored-by: Pieter Eendebak <pieter.eendebak@gmail.com>

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index f4fca35944c11c5abc40b7f51831928bc2324ecb..51b6a2f294187a43ff973c2e0a2f3c1d4e08c81f 100644 (file)
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1885,10 +1885,10 @@ are always available.  They are listed here in alphabetical order.
    ``D -> B -> C -> A -> object`` and the value of *type* is ``B``,
    then :func:`super` searches ``C -> A -> object``.
 
-   The :attr:`~class.__mro__` attribute of the *object_or_type* lists the method
-   resolution search order used by both :func:`getattr` and :func:`super`.  The
-   attribute is dynamic and can change whenever the inheritance hierarchy is
-   updated.
+   The :attr:`~class.__mro__` attribute of the class corresponding to
+   *object_or_type* lists the method resolution search order used by both
+   :func:`getattr` and :func:`super`.  The attribute is dynamic and can change
+   whenever the inheritance hierarchy is updated.
 
    If the second argument is omitted, the super object returned is unbound.  If
    the second argument is an object, ``isinstance(obj, type)`` must be true.  If