Add security implications and update example.

Author: ZeroIntensity

peps/pep-0788.rst

@@ -406,6 +406,11 @@ This PEP specifies a breaking change with the removal of all the
 ``PyGILState`` APIs from the public headers of the non-limited C API in 10
 years (Python 3.25).
 
+Security Implications
+=====================
+
+This PEP has no known security implications.
+
 How to Teach This
 =================
 
@@ -426,6 +431,12 @@ Ideally, they could be reused in the documentation.
 Single-threaded example
 ***********************
 
+This example shows acquiring a lock in a Python method.
+
+If this were to be called from a daemon thread, then the interpreter could
+hang the thread while reattaching the thread state, leaving us with the lock
+held. Any future finalizer that wanted to acquire the lock would be deadlocked!
+
 .. code-block:: C
 
     static PyObject *
@@ -440,13 +451,12 @@ Single-threaded example
 
         Py_BEGIN_ALLOW_THREADS;
         acquire_some_lock();
-        /* If this were to be a daemon thread, then the interpreter could
-           hang the thread while reattaching the thread state, leaving us
-           with the lock held. Any future finalizer that wanted to acquire the
-           lock would be deadlocked!
-         */
         Py_END_ALLOW_THREADS;
 
+        /* Do something with the lock */
+        // ...
+
+        release_some_lock();
         PyThreadState_Release();
         Py_RETURN_NONE;
     }