Fix Sphinx errors.

Author: ZeroIntensity

Doc/c-api/refcounting.rst

@@ -25,7 +25,7 @@ of Python objects.
 
    .. note::
 
-      On :term:`free-threaded build`s of Python, returning 1
+      On :term:`free-threaded builds <free-threaded build>` of Python, returning 1
       isn't sufficient to determine if it's safe to treat *o* as having no
       access by other threads. Use :c:func:`PyUnstable_Object_IsUniquelyReferenced`
       for that instead.

Doc/glossary.rst

@@ -160,7 +160,7 @@ Glossary
       On most builds of Python, having an attached thread state implies that the
       caller holds the :term:`GIL` for the current interpreter, so only
       one OS thread can have an attached thread state at a given moment. In
-      :term:`free-threaded builds <free-threaded builds>` of Python, threads can
+      :term:`free-threaded builds <free-threaded build>` of Python, threads can
       concurrently hold an attached thread state, allowing for true parallelism of
       the bytecode interpreter.
 

Doc/using/configure.rst

@@ -421,7 +421,7 @@ General Options
       :no-typesetting:
 
    Enables support for running Python without the :term:`global interpreter
-   lock` (GIL): :term:`free-threading build`.
+   lock` (GIL): :term:`free-threaded build`.
 
    Defines the ``Py_GIL_DISABLED`` macro and adds ``"t"`` to
    :data:`sys.abiflags`.