PEP 685: Restore citations as originally intended

pep-0685.rst

@@ -66,10 +66,10 @@ docstring, which *does* specify that all non-alphanumeric characters
 (which would include ``-`` and ``.``) are normalized and collapsed.
 
 For pip 22, its
-`"extra normalisation behaviour is quite convoluted and erratic" <pip-erratic_>`__,
+"extra normalisation behaviour is quite convoluted and erratic" [pip-erratic]_
 and so its use is not considered.
 
-.. _pip-erratic: https://discuss.python.org/t/7614/10
+.. [pip-erratic] Tzu-ping Chung on Python Discourse <https://discuss.python.org/t/7614/10
 
 
 Specification
@@ -110,7 +110,7 @@ Backwards Compatibility
 Moving to :pep:`503` normalization and :pep:`508` name acceptance
 allows for all preexisting, valid names to continue to be valid.
 
-Based on `research looking at a collection of wheels on PyPI <pypi-results_>`__,
+Based on research looking at a collection of wheels on PyPI [pypi-results]_,
 the risk of extra name clashes is limited to 73 instances when considering
 all extras names on PyPI, valid or not (not just those within a single package)
 while *only* looking at valid names leads to only 3 clashes:
@@ -122,7 +122,7 @@ while *only* looking at valid names leads to only 3 clashes:
 By requiring tools writing core metadata to only record the normalized name,
 the issue of preexisting, invalid extra names should diminish over time.
 
-.. _pypi-results: https://discuss.python.org/t/14141/17
+.. [pypi-results] Paul Moore on Python Discourse https://discuss.python.org/t/14141/17
 
 
 Security Implications
@@ -171,6 +171,12 @@ it became clear that standardizing **all** naming on :pep:`508` and
 while causing minimal backwards compatibility issues.
 
 
+Open Issues
+===========
+
+N/A
+
+
 Copyright
 =========