diff --git a/pep-0001.txt b/pep-0001.txt
index 882aaedfbbb..1d22c4252e6 100644
--- a/pep-0001.txt
+++ b/pep-0001.txt
@@ -123,10 +123,10 @@ Start with an idea for Python
 
 The PEP process begins with a new idea for Python.  It is highly
 recommended that a single PEP contain a single key proposal or new
-idea. Small enhancements or patches often don't need
-a PEP and can be injected into the Python development workflow with a
-patch submission to the Python `issue tracker`_. The more focused the
-PEP, the more successful it tends to be.  The PEP editors reserve the
+idea; the more focused the PEP, the more successful it tends to be.
+Most enhancements and bug fixes don't need a PEP and
+can be submitted directly to the `Python issue tracker`_.
+The PEP editors reserve the
 right to reject PEP proposals if they appear too unfocused or too
 broad.  If in doubt, split your PEP into several well-focused ones.
 
@@ -834,7 +834,7 @@ Footnotes
 
 .. _.github/CODEOWNERS: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
 
-.. _issue tracker: https://bugs.python.org/
+.. _Python issue tracker: https://github.com/python/cpython/issues
 
 .. _CC0-1.0-Universal: https://choosealicense.com/licenses/cc0-1.0/