[Python-checkins] bpo-40045: Make "dunder" method documentation easier to locate (#19153)

[Javad Mokhtari]

https://github.com/python/cpython/commit/5f9c131c099d6675d1a9d0228497865488afd548
commit: 5f9c131c099d6675d1a9d0228497865488afd548
branch: master
author: Javad Mokhtari <javadmokhtari at outlook.com>
committer: GitHub <noreply at github.com>
date: 2020-03-27T16:02:51-03:00
summary:

bpo-40045: Make "dunder" method documentation easier to locate (#19153)

* issue 40045

* Update lexical_analysis.rst

Make "dunder" method documentation easier(GH-19153)

Co-authored-by: Joannah Nanjekye <33177550+nanjekyejoannah at users.noreply.github.com>

files:
M Doc/reference/lexical_analysis.rst

diff --git a/Doc/reference/lexical_analysis.rst b/Doc/reference/lexical_analysis.rst
index 7e912aabbc7fb..3f420817eefea 100644
--- a/Doc/reference/lexical_analysis.rst
+++ b/Doc/reference/lexical_analysis.rst
@@ -376,11 +376,11 @@ characters:
       information on this convention.
 
 ``__*__``
-   System-defined names. These names are defined by the interpreter and its
-   implementation (including the standard library).  Current system names are
-   discussed in the :ref:`specialnames` section and elsewhere.  More will likely
-   be defined in future versions of Python.  *Any* use of ``__*__`` names, in
-   any context, that does not follow explicitly documented use, is subject to
+   System-defined names, informally known as "dunder" names. These names are
+   defined by the interpreter and its implementation (including the standard library).
+   Current system names are discussed in the :ref:`specialnames` section and elsewhere.
+   More will likely be defined in future versions of Python.  *Any* use of ``__*__`` names,
+   in any context, that does not follow explicitly documented use, is subject to
    breakage without warning.
 
 ``__*``