PEP 101: Update/create links and revise outdated text

peps/pep-0101.rst

@@ -639,7 +639,7 @@ permissions.
   The script will also sign any remaining files that were not
   signed with Sigstore until this point. Again, if this happens,
   do use your ``@python.org`` address for this process. More info:
-  https://www.python.org/download/sigstore/
+  https://www.python.org/downloads/metadata/sigstore/
 
 - In case the CDN already cached a version of the Downloads page
   without the files present, you can invalidate the cache using::
@@ -648,8 +648,8 @@ permissions.
 
 - If this is a **final** release:
 
-  - Add the new version to the *Python Documentation by Version*
-    page ``https://www.python.org/doc/versions/`` and
+  - Add the new version to the `"Python documentation by version"
+    page <https://www.python.org/doc/versions/>`__ and
     remove the current version from any 'in development' section.
 
   - For 3.X.Y, edit all the previous X.Y releases' page(s) to
@@ -666,21 +666,14 @@ permissions.
       Note: Python 3.x.(y-1) has been superseded by
       `Python 3.x.y </download/releases/3.x.y/>`_.
 
-  - Update the "Current Pre-release Testing Versions web page".
-
-    There's a page that lists all the currently-in-testing versions
-    of Python:
-
-    * https://www.python.org/download/pre-releases/
-
-    Every time you make a release, one way or another you'll
-    have to update this page:
+  - Update the `"Current pre-release testing versions" page
+    <https://www.python.org/download/pre-releases/>`__.
 
     - If you're releasing a version before *3.x.0*,
-      you should add it to this page, removing the previous pre-release
+      add it to this page, removing the previous pre-release
       of version *3.x* as needed.
 
-    - If you're releasing *3.x.0 final*, you need to remove the pre-release
+    - If you're releasing *3.x.0 final*, remove the pre-release
       version from this page.
 
     This is in the "Pages" category on the Django-based website, and finding
@@ -690,15 +683,13 @@ permissions.
     page itself.  So you can simply follow the link above, click on the
     "Edit this page" link, and make your changes as needed.  How convenient!
 
-  - If appropriate, update the "Python Documentation by Version" page:
-
-    * https://www.python.org/doc/versions/
+  - If appropriate, update the `"Python documentation by version" page
+    <https://www.python.org/doc/versions/>`__.
 
     This lists all releases of Python by version number and links to their
-    static (not built daily) online documentation.  There's a list at the
-    bottom of in-development versions, which is where all alphas/betas/RCs
-    should go.  And yes you should be able to click on the link above then
-    press the shiny, exciting "Edit this page" button.
+    static (not built daily) online documentation.  There's a link at the
+    bottom to the in-development version.
+    And yes you can press the shiny, exciting "Edit this page" button.
 
 - Write the announcement on `discuss.python.org`_.  This is the
   fuzzy bit because not much can be automated.  You can use an earlier
@@ -844,7 +835,7 @@ else does them.  Some of those tasks include:
 
   * mailing lists (python-dev, python-list, python-announcements)
 
-  * Python Dev blog
+  * `Python Insider blog <https://blog.python.org>`_
 
 - Enjoy your retirement and bask in the glow of a job well done!