Rewrite a sentence to be more in line with the rest of the documentation with
regard to person and audience.
diff --git a/Doc/c-api/init.rst b/Doc/c-api/init.rst
index e62bab6..281432b 100644
--- a/Doc/c-api/init.rst
+++ b/Doc/c-api/init.rst
@@ -492,13 +492,13 @@
global variable). Conversely, when acquiring the lock and restoring the thread
state, the lock must be acquired before storing the thread state pointer.
-Why am I going on with so much detail about this? Because when threads are
-created from C, they don't have the global interpreter lock, nor is there a
-thread state data structure for them. Such threads must bootstrap themselves
-into existence, by first creating a thread state data structure, then acquiring
-the lock, and finally storing their thread state pointer, before they can start
-using the Python/C API. When they are done, they should reset the thread state
-pointer, release the lock, and finally free their thread state data structure.
+It is important to note that when threads are created from C, they don't have
+the global interpreter lock, nor is there a thread state data structure for
+them. Such threads must bootstrap themselves into existence, by first
+creating a thread state data structure, then acquiring the lock, and finally
+storing their thread state pointer, before they can start using the Python/C
+API. When they are done, they should reset the thread state pointer, release
+the lock, and finally free their thread state data structure.
Beginning with version 2.3, threads can now take advantage of the
:cfunc:`PyGILState_\*` functions to do all of the above automatically. The