fix a bunch of spelling errors

(closes SF patch #1104868)

6 files changed, 6 insertions, 6 deletions

diff --git a/Doc/lib/libdatetime.tex b/Doc/lib/libdatetime.tex
index c3fb890..cbda4c4 100644
--- a/Doc/lib/libdatetime.tex
+++ b/Doc/lib/libdatetime.tex
@@ -23,7 +23,7 @@ zone, daylight saving time, or other kind of algorithmic or political
 time adjustment.  Whether a naive \class{datetime} object represents
 Coordinated Universal Time (UTC), local time, or time in some other
 timezone is purely up to the program, just like it's up to the program
-whether a particular number represents meters, miles, or mass.  Naive
+whether a particular number represents metres, miles, or mass.  Naive
 \class{datetime} objects are easy to understand and to work with, at
 the cost of ignoring some aspects of reality.
 
diff --git a/Doc/lib/libmmap.tex b/Doc/lib/libmmap.tex
index 0334147..d0fbf88 100644
--- a/Doc/lib/libmmap.tex
+++ b/Doc/lib/libmmap.tex
@@ -35,7 +35,7 @@ mapping.  The initial memory values for all three access types are
 taken from the specified file.  Assignment to an
 \constant{ACCESS_READ} memory map raises a \exception{TypeError}
 exception.  Assignment to an \constant{ACCESS_WRITE} memory map
-affects both memory and the underlying file.  Assigment to an
+affects both memory and the underlying file.  Assignment to an
 \constant{ACCESS_COPY} memory map affects memory but does not update
 the underlying file.
 
diff --git a/Doc/lib/libos.tex b/Doc/lib/libos.tex
index 6304346..6065725 100644
--- a/Doc/lib/libos.tex
+++ b/Doc/lib/libos.tex
@@ -639,7 +639,7 @@ Availability: Windows.
 \begin{datadesc}{SEEK_SET}
 \dataline{SEEK_CUR}
 \dataline{SEEK_END}
-Parameteters to the \function{lseek()} function.
+Parameters to the \function{lseek()} function.
 Their values are 0, 1, and 2, respectively.
 Availability: Windows, Macintosh, \UNIX.
 \versionadded{2.5}
diff --git a/Doc/lib/libstdwin.tex b/Doc/lib/libstdwin.tex
index 5170222..84aad2f 100644
--- a/Doc/lib/libstdwin.tex
+++ b/Doc/lib/libstdwin.tex
@@ -114,7 +114,7 @@ Return the screen size in pixels.
 \end{funcdesc}
 
 \begin{funcdesc}{getscrmm}{}
-Return the screen size in millimeters.
+Return the screen size in millimetres.
 \end{funcdesc}
 
 \begin{funcdesc}{fetchcolor}{colorname}
diff --git a/Doc/lib/libxmlrpclib.tex b/Doc/lib/libxmlrpclib.tex
index bc5ae10..6430a2b 100644
--- a/Doc/lib/libxmlrpclib.tex
+++ b/Doc/lib/libxmlrpclib.tex
@@ -5,7 +5,7 @@
 \moduleauthor{Fredrik Lundh}{fredrik@pythonware.com}
 \sectionauthor{Eric S. Raymond}{esr@snark.thyrsus.com}
 
-% Not everyting is documented yet.  It might be good to describe 
+% Not everything is documented yet.  It might be good to describe 
 % Marshaller, Unmarshaller, getparser, dumps, loads, and Transport.
 
 \versionadded{2.2}
diff --git a/Doc/lib/tkinter.tex b/Doc/lib/tkinter.tex
index 6a60982..f944eab 100644
--- a/Doc/lib/tkinter.tex
+++ b/Doc/lib/tkinter.tex
@@ -731,7 +731,7 @@ Ousterhout's book.
 Screen distances can be specified in either pixels or absolute
 distances.  Pixels are given as numbers and absolute distances as
 strings, with the trailing character denoting units: \code{c}
-for centimeters, \code{i} for inches, \code{m} for millimeters,
+for centimetres, \code{i} for inches, \code{m} for millimetres,
 \code{p} for printer's points.  For example, 3.5 inches is expressed
 as \code{"3.5i"}.