infinitely -> unbounded

Author: ZeroIntensity

peps/pep-0788.rst

@@ -18,7 +18,7 @@ In Python, threads are able to interact with an interpreter (e.g., invoke the
 bytecode loop) through an :term:`attached thread state`. On with-GIL builds,
 only one thread can hold an attached thread state at once, which means that
 the thread holds the :term:`GIL`. On free-threaded builds, there can be
-infinitely many thread states attached, allowing for parallelism (because
+an unbounded number of thread states attached, allowing for parallelism (because
 multiple threads can invoke the interpreter at once).
 
 With that in mind, attachment of thread states is a bit problematic in the C API.