diff --git a/peps/pep-0001.rst b/peps/pep-0001.rst
index 28c33f8d9af..75dd60a46ea 100644
--- a/peps/pep-0001.rst
+++ b/peps/pep-0001.rst
@@ -535,15 +535,21 @@ Each PEP should have the following parts/sections:
    to the PEP, those concerns should be explicitly written out to make
    sure reviewers of the PEP are aware of them.
 
-8. How to Teach This -- For a PEP that adds new functionality or changes
-   language behavior, it is helpful to include a section on how to
-   teach users, new and experienced, how to apply the PEP to their
-   work.
+8. Documentation Updates -- For a PEP that adds new functionality or changes
+   language behavior, it is helpful to include a section on what
+   documentation will need to be produced to inform users, new and experienced,
+   about the PEP.
 
-   This section may include key points and recommended documentation
+   Include key points and recommended documentation
    changes that would help users adopt a new feature or migrate their
    code to use a language change.
 
+   Track down and list out all the docs that need to be updated or created.
+
+   While PEP authors can write the documentation themselves, they can
+   also ask for further guidance on what docs are needed from
+   the Python Docs Editorial board and the Python Docs WG.
+
 9. Reference Implementation -- The reference implementation must be
    completed before any PEP is given status "Final", but it need not
    be completed before the PEP is accepted.  While there is merit