Change some usage of 'global interpreter lock'

Author: ZeroIntensity

Doc/c-api/init.rst

@@ -1262,7 +1262,7 @@ with sub-interpreters:
 .. c:function:: PyGILState_STATE PyGILState_Ensure()
 
    Ensure that the current thread is ready to call the Python C API regardless
-   of the current state of Python, or of the global interpreter lock.This may
+   of the current state of Python, or of the :term:`current thread state`. This may
    be called as many times as desired by a thread as long as each call is
    matched with a call to :c:func:`PyGILState_Release`. In general, other
    thread-related APIs may be used between :c:func:`PyGILState_Ensure` and
@@ -1924,16 +1924,16 @@ pointer and a void pointer argument.
    both these conditions met:
 
    * on a :term:`bytecode` boundary;
-   * with the main thread holding the :term:`global interpreter lock`
+   * with the main thread holding an :term:`attached thread state`
      (*func* can therefore use the full C API).
 
    *func* must return ``0`` on success, or ``-1`` on failure with an exception
    set.  *func* won't be interrupted to perform another asynchronous
    notification recursively, but it can still be interrupted to switch
-   threads if the global interpreter lock is released.
+   threads if the :term:`thread state <attached thread state>` is detached.
 
    This function doesn't need a current thread state to run, and it doesn't
-   need the global interpreter lock.
+   need an :term:`attached thread state`.
 
    To call this function in a subinterpreter, the caller must have an
    :term:`attached thread state`. Otherwise, the function *func* can be scheduled to

Doc/glossary.rst

@@ -649,9 +649,9 @@ Glossary
       multi-threaded applications and makes it easier to use multi-core CPUs
       efficiently. For more details, see :pep:`703`.
 
-      In Python's C API, a function might declare that it requires (or doesn't require)
-      the GIL to be held in order to use it. This refers to having an active
-      :term:`thread state` for the current thread.
+      In prior versions of Python's C API, a function might declare that it
+      requires the GIL to be held in order to use it. This refers to having an
+      :term:`attached thread state`.
 
    hash-based pyc
       A bytecode cache file that uses the hash rather than the last-modified