PEP 799: Small clarifications about new sampling profiler

Author: pablogsal

peps/pep-0799.rst

@@ -34,11 +34,13 @@ optimizations, such as those introduced by :pep:`659`. Moreover, ``cProfile`` on
 main thread, making it less useful in modern concurrent Python programs. Confusingly, the naming
 of these modules implies that ``profile`` is canonical, when in fact it is largely obsolete.
 
-With Python 3.15, a new sampling profiler was introduced under ``profile.sample``. Known as
-**tachyon**, this tool uses statistical sampling to infer performance characteristics, which
-introduces much lower overhead and works better with the modern Python interpreter. It also supports
-multiple threads, async functions, and attaching to running processes. Despite these strengths,
-the placement of tachyon under ``profile.sample`` is misleading and obscures its importance.
+With Python 3.15, a new sampling profiler was introduced under
+``profile.sample``. Known as **tachyon**, this tool uses statistical sampling
+to infer performance characteristics, which introduces **zero overhead
+profiling** and works better with the modern Python interpreter. It also
+supports **multiple threads, async functions, free threading builds and
+attaching to running processes**. Despite these strengths, the placement of
+tachyon under ``profile.sample`` is misleading and obscures its importance.
 
 Currently, the organization of profiling tools lacks a consistent, discoverable structure.
 The proposed reorganization is meant to guide users more effectively toward appropriate tools,