[doc] Be more clear on super() regarding multiple base classes methods (GH-21789)

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index 72441f0dbfa57c921f91de849279b5c8dd2ed2ec..7d8a669f9e16d4bc82c21541572c8d89b1ef8d25 100644 (file)
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1711,7 +1711,7 @@ are always available.  They are listed here in alphabetical order.
    not found in statically compiled languages or languages that only support
    single inheritance.  This makes it possible to implement "diamond diagrams"
    where multiple base classes implement the same method.  Good design dictates
-   that this method have the same calling signature in every case (because the
+   that such implementations have the same calling signature in every case (because the
    order of calls is determined at runtime, because that order adapts
    to changes in the class hierarchy, and because that order can include
    sibling classes that are unknown prior to runtime).