#11997: merge with 3.1.

diff --cc Doc/c-api/init.rst
index e50c417d3668d947160d7ae80604b25985e8b644,b2fa3ee6e10bd0d0df0c969c4436d163a87b322b..1806867e5e190acbd420ab73e92655d6ed821c8f
--- 1/Doc/c-api/init.rst
--- 2/Doc/c-api/init.rst
+++ b/Doc/c-api/init.rst
@@@ -882,11 -866,11 +882,11 @@@ instances or classes between sub-interp
  by such objects may affect the wrong (sub-)interpreter's dictionary of loaded
  modules.
  
 -Also note that combining this functionality with :cfunc:`PyGILState_\*` APIs
 +Also note that combining this functionality with :c:func:`PyGILState_\*` APIs
- is delicate, become these APIs assume a bijection between Python thread states
+ is delicate, because these APIs assume a bijection between Python thread states
  and OS-level threads, an assumption broken by the presence of sub-interpreters.
  It is highly recommended that you don't switch sub-interpreters between a pair
 -of matching :cfunc:`PyGILState_Ensure` and :cfunc:`PyGILState_Release` calls.
 +of matching :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release` calls.
  Furthermore, extensions (such as :mod:`ctypes`) using these APIs to allow calling
  of Python code from non-Python created threads will probably be broken when using
  sub-interpreters.