Add clarification for 'modern versions'

Author: ZeroIntensity

peps/pep-0788.rst

@@ -183,14 +183,14 @@ created by the authors of this PEP:
     omit ``PyGILState_Ensure`` in fresh threads.
 
 In reality, :c:func:`PyGILState_Ensure` doesn't just "acquire the GIL" in
-modern versions. It attaches a :term:`thread state` for the current
-thread--*that's* what lets a thread invoke the C API. On with-GIL builds,
-holding an :term:`attached thread state` implies holding the GIL, so only one
-thread can have one at a time. Free-threaded builds achieve the effect of
-multi-core parallism while remaining backwards-compatible by simply removing
-that limitation: threads still need a thread state (and thus need to call
-:c:func:`PyGILState_Ensure`), but they don't need to wait on one another to
-do so.
+modern versions (that being since 3.12). It attaches a :term:`thread state`
+for the current thread--*that's* what lets a thread invoke the C API. On
+with-GIL builds, holding an :term:`attached thread state` implies holding the
+GIL, so only one thread can have one at a time. Free-threaded builds achieve
+the effect of multi-core parallism while remaining backwards-compatible by
+simply removing that limitation: threads still need a thread state (and thus
+need to call :c:func:`PyGILState_Ensure`), but they don't need to wait on one
+another to do so.
 
 Subinterpreters don't work with :c:func:`PyGILState_Ensure`
 -----------------------------------------------------------