diff -r 87dcd948dc74 Doc/library/time.rst
--- a/Doc/library/time.rst	Wed Feb 29 16:21:25 2012 -0800
+++ b/Doc/library/time.rst	Thu Mar 01 13:06:54 2012 +0100
@@ -63,10 +63,10 @@
   systems, the clock "ticks" only 50 or 100 times a second.
 
 * On the other hand, the precision of :func:`time` and :func:`sleep` is better
-  than their Unix equivalents: times are expressed as floating point numbers,
+  than their Unix equivalents: times are expressed as floating-point numbers,
   :func:`time` returns the most accurate time available (using Unix
   :c:func:`gettimeofday` where available), and :func:`sleep` will accept a time
-  with a nonzero fraction (Unix :c:func:`select` is used to implement this, where
+  with a non-zero fraction (Unix :c:func:`select` is used to implement this, where
   available).
 
 * The time value as returned by :func:`gmtime`, :func:`localtime`, and
@@ -126,13 +126,13 @@
       single: processor time
       single: benchmarking
 
-   On Unix, return the current processor time as a floating point number expressed
+   On Unix, return the current processor time as a floating-point number expressed
    in seconds.  The precision, and in fact the very definition of the meaning of
    "processor time", depends on that of the C function of the same name, but in any
    case, this is the function to use for benchmarking Python or timing algorithms.
 
    On Windows, this function returns wall-clock seconds elapsed since the first
-   call to this function, as a floating point number, based on the Win32 function
+   call to this function, as a floating-point number, based on the Win32 function
    :c:func:`QueryPerformanceCounter`. The resolution is typically better than one
    microsecond.
 
@@ -219,7 +219,7 @@
    This is the inverse function of :func:`localtime`.  Its argument is the
    :class:`struct_time` or full 9-tuple (since the dst flag is needed; use ``-1``
    as the dst flag if it is unknown) which expresses the time in *local* time, not
-   UTC.  It returns a floating point number, for compatibility with :func:`time`.
+   UTC.  It returns a floating-point number, for compatibility with :func:`time`.
    If the input value cannot be represented as a valid time, either
    :exc:`OverflowError` or :exc:`ValueError` will be raised (which depends on
    whether the invalid value is caught by Python or the underlying C libraries).
@@ -238,7 +238,7 @@
 .. function:: sleep(secs)
 
    Suspend execution for the given number of seconds.  The argument may be a
-   floating point number to indicate a more precise sleep time. The actual
+   floating-point number to indicate a more precise sleep time. The actual
    suspension time may be less than that requested because any caught signal will
    terminate the :func:`sleep` following execution of that signal's catching
    routine.  Also, the suspension time may be longer than requested by an arbitrary
@@ -443,8 +443,8 @@
 
 .. function:: time()
 
-   Return the time as a floating point number expressed in seconds since the epoch,
-   in UTC.  Note that even though the time is always returned as a floating point
+   Return the time as a floating-point number expressed in seconds since the epoch,
+   in UTC.  Note that even though the time is always returned as a floating-point
    number, not all systems provide time with a better precision than 1 second.
    While this function normally returns non-decreasing values, it can return a
    lower value than a previous call if the system clock has been set back between