Remove the rest of reference theft.

Author: ZeroIntensity

peps/pep-0788.rst

@@ -460,9 +460,6 @@ Strong Interpreter References
 
     Acquire a strong reference to the current interpreter.
 
-    This function is generally meant to be used in tandem with
-    :c:func:`PyThreadState_Ensure`.
-
     This function cannot fail, other than with a fatal error when the caller
     doesn't hold an :term:`attached thread state`.
 
@@ -485,9 +482,6 @@ Strong Interpreter References
 
     Duplicate a strong reference to an interpreter.
 
-    This function is generally meant to be used in tandem with
-    :c:func:`PyThreadState_Ensure`.
-
     This function cannot fail, and the caller doesn't need to hold an
     :term:`attached thread state`.
 
@@ -614,10 +608,6 @@ replace :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release`.
     subsequent calls to :c:func:`PyGILState_Ensure` in this thread, but
     :c:func:`PyGILState_Ensure` will *not* make the thread daemon again.
 
-    The reference to the interpreter *ref* is stolen by this function.
-    Use :c:func:`PyInterpreterRef_Dup` if the reference is intended to be
-    kept.
-
     Return zero on success, and non-zero with the old attached thread state
     restored (which may have been ``NULL``).
 
@@ -632,9 +622,7 @@ replace :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release`.
 
     This function cannot fail, but may hang the thread if the
     restored :term:`attached thread state` was daemon and the interpreter
-    was finalized. If you're running in a thread where that could be an issue,
-    call :c:func:`PyThreadState_SetDaemon` before :c:func:`PyThreadState_Ensure`
-    at your own discretion.
+    was finalized.
 
 ``threading`` Shutdown and Behavior
 -----------------------------------