Use a less wordy phrase for detaching.

Author: ZeroIntensity

Doc/c-api/init.rst

@@ -1033,11 +1033,11 @@ to be released to attach their thread state, allowing true multi-core parallelis
 
 .. note::
    Calling system I/O functions is the most common use case for detaching
-   the :term:`thread state`, but it can also be useful before calling
+   the :term:`thread state <attached thread state>`, but it can also be useful before calling
    long-running computations which don't need access to Python objects, such
    as compression or cryptographic functions operating over memory buffers.
    For example, the standard :mod:`zlib` and :mod:`hashlib` modules detach the
-   :term:`attached thread state` when compressing or hashing data.
+   :term:`thread state <attached thread state>` when compressing or hashing data.
 
 
 .. _gilstate:
@@ -2394,7 +2394,7 @@ The C-API provides a basic mutual exclusion lock.
 
    Lock mutex *m*.  If another thread has already locked it, the calling
    thread will block until the mutex is unlocked.  While blocked, the thread
-   will temporarily detach the :term:`attached thread state` if one exists.
+   will temporarily detach the :term:`thread state <attached thread state>` if one exists.
 
    .. versionadded:: 3.13
 

Doc/extending/newtypes_tutorial.rst

@@ -404,7 +404,7 @@ But this would be risky.  Our type doesn't restrict the type of the
 ``first`` member, so it could be any kind of object.  It could have a
 destructor that causes code to be executed that tries to access the
 ``first`` member; or that destructor could detach the
-:term:`attached thread state` and let arbitrary code run in other
+:term:`thread state <attached thread state>` and let arbitrary code run in other
 threads that accesses and modifies our object.
 
 To be paranoid and protect ourselves against this possibility, we almost
@@ -414,7 +414,7 @@ don't we have to do this?
 * when we absolutely know that the reference count is greater than 1;
 
 * when we know that deallocation of the object [#]_ will neither detach
-  the :term:`attached thread state` nor cause any calls back into our type's code;
+  the :term:`thread state <attached thread state>` nor cause any calls back into our type's code;
 
 * when decrementing a reference count in a :c:member:`~PyTypeObject.tp_dealloc`
   handler on a type which doesn't support cyclic garbage collection [#]_.