[3.13] gh-121905: Consistently use "floating-point" instead of "floating point" (GH-121907) (GH-122012)

(cherry picked from commit 1a0c7b9ba48a2dffb70bb0c7327abae1d3e87356)

1 files changed, 3 insertions, 3 deletions

diff --git a/Lib/threading.py b/Lib/threading.py
index 31ab77c..2dcdd0c 100644
--- a/Lib/threading.py
+++ b/Lib/threading.py
@@ -336,7 +336,7 @@ class Condition:
         awakened or timed out, it re-acquires the lock and returns.
 
         When the timeout argument is present and not None, it should be a
-        floating point number specifying a timeout for the operation in seconds
+        floating-point number specifying a timeout for the operation in seconds
         (or fractions thereof).
 
         When the underlying lock is an RLock, it is not released using its
@@ -646,7 +646,7 @@ class Event:
         the optional timeout occurs.
 
         When the timeout argument is present and not None, it should be a
-        floating point number specifying a timeout for the operation in seconds
+        floating-point number specifying a timeout for the operation in seconds
         (or fractions thereof).
 
         This method returns the internal flag on exit, so it will always return
@@ -1059,7 +1059,7 @@ class Thread:
         or until the optional timeout occurs.
 
         When the timeout argument is present and not None, it should be a
-        floating point number specifying a timeout for the operation in seconds
+        floating-point number specifying a timeout for the operation in seconds
         (or fractions thereof). As join() always returns None, you must call
         is_alive() after join() to decide whether a timeout happened -- if the
         thread is still alive, the join() call timed out.