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

[orsenthil]

https://github.com/python/cpython/commit/8d47f92d46a92a5931b8f3dcb4a484df672fc4de
commit: 8d47f92d46a92a5931b8f3dcb4a484df672fc4de
branch: 3.9
author: Miss Islington (bot) <31488909+miss-islington at users.noreply.github.com>
committer: orsenthil <skumaran at gatech.edu>
date: 2021-04-28T18:13:12-07:00
summary:

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

(cherry picked from commit 69a733bda34d413d3ad545ef3132240e5d2a7c0c)

Co-authored-by: Andre Delfino <adelfino at gmail.com>

Co-authored-by: Andre Delfino <adelfino at gmail.com>

files:
M Doc/library/functions.rst

diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst
index ef51782205b45..3a222b1e67975 100644
--- a/Doc/library/functions.rst
+++ b/Doc/library/functions.rst
@@ -1631,7 +1631,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).