Re-wording

Author: giampaolo

Doc/library/subprocess.rst

@@ -803,17 +803,20 @@ Instances of the :class:`Popen` class have the following methods:
 
    .. note::
 
-      When ``timeout`` is not ``None``, an efficient event-driven mechanism
-      waits for process termination when available:
+      When ``timeout`` is not ``None`` and the platform supports it, an
+      efficient event-driven mechanism is used to wait for process termination:
 
       - Linux ≥= 5.3 uses :func:`os.pidfd_open` + :func:`select.poll`
       - macOS and other BSD variants use :func:`select.kqueue` +
         ``KQ_FILTER_PROC`` + ``KQ_NOTE_EXIT``
       - Windows uses ``WaitForSingleObject``
 
       If none of these mechanisms are available, the function falls back to a
-      busy loop (non-blocking call and short sleeps). Use the :mod:`asyncio`
-      module for an asynchronous wait: see
+      busy loop (non-blocking call and short sleeps).
+
+   .. note::
+
+      Use the :mod:`asyncio` module for an asynchronous wait: see
       :class:`asyncio.create_subprocess_exec`.
 
    .. versionchanged:: 3.3

Doc/whatsnew/3.15.rst

@@ -739,13 +739,14 @@ ssl
 subprocess
 ----------
 
-* :meth:`subprocess.Popen.wait`: when ``timeout`` is not ``None``, an efficient
-  event-driven mechanism now waits for process termination, if available:
+* :meth:`subprocess.Popen.wait`: when ``timeout`` is not ``None`` and the
+  platform supports it, an efficient event-driven mechanism is used to wait for
+  process termination:
 
   - Linux ≥= 5.3 uses :func:`os.pidfd_open` + :func:`select.poll`
   - macOS and other BSD variants use :func:`select.kqueue` + ``KQ_FILTER_PROC``
     + ``KQ_NOTE_EXIT``
-  - Windows keep using ``WaitForSingleObject`` (unchanged)
+  - Windows keeps using ``WaitForSingleObject`` (unchanged)
 
   If none of these mechanisms are available, the function falls back to the
   traditional busy loop (non-blocking call and short sleeps).