Stupid trailing spaces

Author: ZeroIntensity

peps/pep-0788.rst

@@ -111,15 +111,15 @@ Generally, this pattern would look something like this:
 
 This comes with a hidden problem. If the target interpreter is finalizing, the
 current thread will hang! Or, if the target interpreter has been completely
-deleted, then attaching will likely result in a crash. 
+deleted, then attaching will likely result in a crash.
 
 There are currently a few workarounds for this:
 
 1. Leak resources to prevent the need to invoke Python.
 2. Protect against finalization using an :mod:`atexit` callback.
 
 Ideally, finalization should not be a footgun when working with
-Python's C API. 
+Python's C API.
 
 
 Locks in native extensions can be unusable during finalization
@@ -374,10 +374,10 @@ replace :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release`.
 
     It is OK to call this function if the thread already has an
     attached thread state, as long as there is a subsequent call to
-    :c:func:`PyThreadState_Release` that matches this one. 
+    :c:func:`PyThreadState_Release` that matches this one.
 
     Nested calls to this function will only sometimes create a new
-    :term:`thread state`. 
+    thread state.
 
     First, this function checks if an attached thread state is present.
     If there is, this function then checks if the interpreter of that