diff --git a/Doc/library/urllib.parse.rst b/Doc/library/urllib.parse.rst
index 037d4c41c0f..6a143c5fe57 100644
--- a/Doc/library/urllib.parse.rst
+++ b/Doc/library/urllib.parse.rst
@@ -281,7 +281,7 @@ or on combining URL components into a URL string.
    .. versionchanged:: 3.2
       Result is a structured object rather than a simple 2-tuple.
 
-:: _parsing-ascii-encoded-bytes:
+.. _parsing-ascii-encoded-bytes:
 
 Parsing ASCII Encoded Bytes
 ---------------------------
diff --git a/Doc/whatsnew/3.2.rst b/Doc/whatsnew/3.2.rst
index b510f447e71..e846a0fe25a 100644
--- a/Doc/whatsnew/3.2.rst
+++ b/Doc/whatsnew/3.2.rst
@@ -1887,7 +1887,7 @@ string, then the *safe*, *encoding*, and *error* parameters are sent to
              encoding='latin-1')
     'type=telenovela&name=%BFD%F3nde+Est%E1+Elisa%3F'
 
-As detailed in :ref:`parsing-ascii-encoded-bytes` , all the :mod:`urllib.parse`
+As detailed in :ref:`parsing-ascii-encoded-bytes`, all the :mod:`urllib.parse`
 functions now accept ASCII-encoded byte strings as input, so long as they are
 not mixed with regular strings.  If ASCII-encoded byte strings are given as
 parameters, the return types will also be an ASCII-encoded byte strings: