Meta: Apply further reviewer suggestions on reorganized text

Co-authored-by: Adam Turner <[email protected]>

Author: CAM-Gerlach

CONTRIBUTING.rst

@@ -25,7 +25,7 @@ In general, most non-Draft/Active PEPs are considered to be historical
 documents rather than living specifications or documentation. Major changes to
 their core content usually require a new PEP, while smaller modifications may
 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.
+<https://peps.python.org/pep-0001/#pep-maintenance>`__ for more.
 
 Copyediting and proofreading Draft and Active PEPs (including fixing spelling
 and formatting issues) is welcomed (subject to review by the PEP authors),
@@ -36,20 +36,14 @@ 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
 PR here. For example, you could contact the PEP author(s), propose your idea in
-a discussion venue appropriate to the PEP (such as `Typing-SIG
-<https://mail.python.org/archives/list/[email protected]/>`__ for static
-typing, or `Packaging Discourse <https://discuss.python.org/c/packaging/>`__
-for packaging), or `open an issue <https://github.com/python/peps/issues>`__.
-
+a discussion venue appropriate to the PEP's topic, or
+`open an issue here <https://github.com/python/peps/issues>`__.
 
 Commit messages and PR titles
 -----------------------------
 
 When adding or modifying a PEP, please include the PEP number in the commit
 summary and pull request title. For example, ``PEP NNN: <summary of changes>``.
-Likewise, prefix rendering infrastructure changes with ``Infra:``, linting
-alterations with ``Lint:`` and other non-PEP meta changes, such as updates to
-the Readme/Contributing Guide, issue/PR template, etc., with ``Meta:``.
 
 
 Sign the CLA

pep-0001.txt

@@ -457,7 +457,7 @@ if they are never meant to be completed.  E.g. :pep:`1` (this PEP).
 PEP Maintenance
 ---------------
 
-In general, PEPs are no longer substantially modified after they have reached
+In general, PEPs are not substantially modified after they have reached
 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,