Fix pre-commit lint.

Author: ZeroIntensity

Doc/c-api/init.rst

@@ -1248,9 +1248,9 @@ code, or when embedding the Python interpreter:
 
    Set the :term:`current thread state` to *tstate*, and return
    the old value.
-   
+
    If there is an :term:`attached thread state` for the current
-   thread, it will be detached. Upon returning from this function, 
+   thread, it will be detached. Upon returning from this function,
    *tstate* will become :term:`attached <attached thread state>` instead
    if it's not ``NULL``. If it is ``NULL``, then the :term:`current thread state`
    will be ``NULL``.

Doc/glossary.rst

@@ -145,7 +145,7 @@ Glossary
       block, and then re-attached when :c:macro:`Py_END_ALLOW_THREADS` is reached.
 
       On most builds of Python, having an attached thread state means that the
-      caller holds the :term:`GIL` for the current interpreter.    
+      caller holds the :term:`GIL` for the current interpreter.
 
    attribute
       A value associated with an object which is usually referenced by name
@@ -353,7 +353,7 @@ Glossary
       A per-thread :c:data:`PyThreadState` pointer for the current thread.
       The pointer might be ``NULL``, in which case Python code should not
       get executed.
-      
+
       If the current thread state is non-``NULL``, then the :term:`thread state`
       that it points to is considered to be :term:`attached <attached thread state>`.