Update peps/pep-0001.rst

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: warsaw

peps/pep-0001.rst

@@ -581,13 +581,16 @@ Each PEP should have the following parts/sections:
 13. Footnotes -- A collection of footnotes cited in the PEP, and
     a place to list non-inline hyperlink targets.
 
-14. Change History -- A summary of major changes the PEP has undergone, based on discussions and feedback.
-    Think of this as a "changelog" or "release notes" for the PEP.  In general, whenever you update the
-    ``Post-History`` header for major changes, add a new bullet item in newest-first (i.e. reverse
-    chronological) order, using the same ``DD-MMM-YYYY`` format, with sub-bullets summarizing the changes.
-    You can consider linking this to the same link as the ``Post-History`` link.  This isn't mandatory, so
-    it's left to the PEP author's discretion, but such a section can be helpful for those following along to
-    understand the evolution of your PEP.  Here is :pep:`an example <694#change-history>`.
+Change History -- A summary of major changes the PEP has undergone, based on
+    discussions and feedback. Think of this as a "changelog" or "release notes"
+    for the PEP.  In general, whenever you update the ``Post-History`` header
+    for major changes, add a new bullet item in newest-first (i.e. reverse
+    chronological) order, using the same ``DD-MMM-YYYY`` format, with
+    sub-bullets summarizing the changes. You can consider linking this to the
+    same link as the ``Post-History`` link.  This isn't mandatory, so it's left
+    to the PEP author's discretion, but such a section can be helpful for those
+    following along to understand the evolution of your PEP.  Here is :pep:`an
+    example <694#change-history>`.
 
 15. Copyright/license -- Each new PEP must be placed under a dual license of
     public domain and CC0-1.0-Universal_ (see this PEP for an example).