Patch #808362: Fix typos.

loewis · loewis · commit 7bdc484c97eb · 2003-09-20T11:09:28.000Z
diff --git a/Doc/lib/libtimeit.tex b/Doc/lib/libtimeit.tex
@@ -122,7 +122,7 @@ \subsection{Command Line Interface}
 \function{time.time()}'s granularity is 1/60th of a second; on \UNIX,
 \function{time.clock()} has 1/100th of a second granularity and
 \function{time.time()} is much more precise.  On either platform, the
-default timer functions measures wall clock time, not the CPU time.
+default timer functions measure wall clock time, not the CPU time.
 This means that other processes running on the same computer may
 interfere with the timing.  The best thing to do when accurate timing
 is necessary is to repeat the timing a few times and use the best
diff --git a/Doc/lib/libunittest.tex b/Doc/lib/libunittest.tex
@@ -769,7 +769,7 @@ \subsection{TestResult Objects
 
 
 The following methods of the \class{TestResult} class are used to
-maintain the internal data structures, and mmay be extended in
+maintain the internal data structures, and may be extended in
 subclasses to support additional reporting requirements.  This is
 particularly useful in building tools which support interactive
 reporting while tests are being run.
diff --git a/Lib/timeit.py b/Lib/timeit.py
@@ -33,7 +33,7 @@
 clock() has microsecond granularity but time()'s granularity is 1/60th
 of a second; on Unix, clock() has 1/100th of a second granularity and
 time() is much more precise.  On either platform, the default timer
-functions measures wall clock time, not the CPU time.  This means that
+functions measure wall clock time, not the CPU time.  This means that
 other processes running on the same computer may interfere with the
 timing.  The best thing to do when accurate timing is necessary is to
 repeat the timing a few times and use the best time.  The -r option is
