Meta: Further revise PEP change guidance to reflect current reality

Author: CAM-Gerlach

CONTRIBUTING.rst

@@ -28,9 +28,10 @@ or may not be appropriate, depending on the PEP's status. See `PEP 1
 <https://www.python.org/dev/peps/pep-0001/#pep-maintenance>`__ for more.
 
 Copyediting and proofreading Draft and Active PEPs (including fixing spelling
-and formatting issues) is welcomed, and can be done via pull request to this
-repo, though we generally advise against PRs that simply mass-correct minor
-typos on older PEPs which don't significantly impair meaning and understanding.
+and formatting issues) is welcomed (subject to review by the PEP authors),
+and can be done via pull request to this repo, though we generally advise
+against PRs that simply mass-correct minor typos on older PEPs which don't
+significantly impair meaning and understanding.
 Substantive content changes should first be proposed on PEP discussion threads.
 
 If you're still unsure, we encourage you to reach out first before opening a

pep-0001.txt

@@ -458,15 +458,15 @@ PEP Maintenance
 ---------------
 
 In general, PEPs are no longer substantially modified after they have reached
-the Final, Rejected or Superseded state. Once a PEP has been completed,
-it is considered to be a historical document rather than living specifications.
+the Accepted, Final, Rejected or Superseded state. Once resolution is reached,
+a PEP is considered a historical document rather than a living specification.
 Formal documentation of the expected behavior should be maintained elsewhere,
 such as the `Language Reference`_ for core features, the `Library Reference`_
 for standard library modules or the `PyPA Specifications`_ for packaging.
 
 If changes based on implementation experience and user feedback are made to
-Standards track PEPs while in the Accepted or Provisional state, they
-should be noted in the PEP, such that the PEP accurately describes the state of
+Standards track PEPs while in the Provisional or (with SC approval) Accepted
+state, they should be noted in the PEP, such that the PEP accurately describes
 the implementation at the point where it is marked Final.
 
 Active Informational and Process PEPs may be updated over time to reflect
@@ -475,8 +475,9 @@ followed in these cases will depend on the nature and purpose of the PEP
 being updated. Substantive changes to governance PEPs must be reviewed by the
 Steering Council (by opening a `Steering Council issue`_).
 
-Draft PEPs are freely open for discussion and proposed modification until
-submitted to the Steering Council or PEP-Delegate for review and resolution.
+Draft PEPs are freely open for discussion and proposed modification,
+at the discretion of the authors, until submitted to the
+Steering Council or PEP-Delegate for review and resolution.
 Substantive content changes should generally be first proposed on
 the PEP's discussion thread listed in its ``Discussions-To`` header.
 Occasionally, a Deferred or even a Withdrawn PEP may be resurrected