fix various typos; thanks, George Yoshida!

(closes SF patch #952047)

diff --git a/Doc/lib/libcode.tex b/Doc/lib/libcode.tex
index 7bde19b614e16489b656072595dc192aaae58eec..dc4c717ad8a4273fe4448f63f59d19ee9d5f1ae5 100644 (file)
--- a/Doc/lib/libcode.tex
+++ b/Doc/lib/libcode.tex
@@ -61,7 +61,7 @@ Returns a code object (the same as \code{compile(\var{source},
 valid; \code{None} if the command is incomplete; raises
 \exception{SyntaxError} if the command is complete and contains a
 syntax error, or raises \exception{OverflowError} or
-\exception{ValueError} if the command cotains an invalid literal.
+\exception{ValueError} if the command contains an invalid literal.
 \end{funcdesc}
 
 

diff --git a/Doc/lib/libinspect.tex b/Doc/lib/libinspect.tex
index e7f4c29619466392087aea07a8d74a02a9a6b97c..68ae67b36e321335e87bba554da09fbce175c185 100644 (file)
--- a/Doc/lib/libinspect.tex
+++ b/Doc/lib/libinspect.tex
@@ -120,7 +120,7 @@ Note:
 \begin{funcdesc}{getmodulename}{path}
   Return the name of the module named by the file \var{path}, without
   including the names of enclosing packages.  This uses the same
-  algortihm as the interpreter uses when searching for modules.  If
+  algorithm as the interpreter uses when searching for modules.  If
   the name cannot be matched according to the interpreter's rules,
   \code{None} is returned.
 \end{funcdesc}

diff --git a/Doc/lib/libregex.tex b/Doc/lib/libregex.tex
index 93c389adc2a05a85c38f80f1d8a665fe8933ca1a..0982f815196efd033f69252090e97f7bd920cd14 100644 (file)
--- a/Doc/lib/libregex.tex
+++ b/Doc/lib/libregex.tex
@@ -44,7 +44,7 @@ regular expression represented as a string literal, you have to
 E.g.\  to extract \LaTeX\ \samp{\e section\{\textrm{\ldots}\}} headers
 from a document, you can use this pattern:
 \code{'[\e ]section\{\e (.*\e )\}'}.  \emph{Another exception:}
-the escape sequece \samp{\e b} is significant in string literals
+the escape sequence \samp{\e b} is significant in string literals
 (where it means the ASCII bell character) as well as in Emacs regular
 expressions (where it stands for a word boundary), so in order to
 search for a word boundary, you should use the pattern \code{'\e \e b'}.

diff --git a/Doc/lib/liburllib2.tex b/Doc/lib/liburllib2.tex
index ae25e53499432931b7f2916f31d0d0a77bf17db9..23996455638ccb5bffb975666f47fd02d59c56b4 100644 (file)
--- a/Doc/lib/liburllib2.tex
+++ b/Doc/lib/liburllib2.tex
@@ -496,7 +496,7 @@ These methods are available on \class{HTTPPasswordMgr} and
 \class{HTTPPasswordMgrWithDefaultRealm} objects.
 
 \begin{methoddesc}[HTTPPasswordMgr]{add_password}{realm, uri, user, passwd}
-\var{uri} can be either a single URI, or a sequene of URIs. \var{realm},
+\var{uri} can be either a single URI, or a sequence of URIs. \var{realm},
 \var{user} and \var{passwd} must be strings. This causes
 \code{(\var{user}, \var{passwd})} to be used as authentication tokens
 when authentication for \var{realm} and a super-URI of any of the

diff --git a/Doc/lib/libxmlrpclib.tex b/Doc/lib/libxmlrpclib.tex
index a285c16117e296a02183b7c25f8fad9a0a269db7..957a25b46b2d0cb95c3814fa7887423a6c6f0b6a 100644 (file)
--- a/Doc/lib/libxmlrpclib.tex
+++ b/Doc/lib/libxmlrpclib.tex
@@ -190,7 +190,7 @@ It also supports certain of Python's built-in operators through
 \subsection{Binary Objects \label{binary-objects}}
 
 This class may initialized from string data (which may include NULs).
-The primary acess to the content of a \class{Binary} object is
+The primary access to the content of a \class{Binary} object is
 provided by an attribute:
 
 \begin{memberdesc}[Binary]{data}

diff --git a/Doc/lib/xmlsaxutils.tex b/Doc/lib/xmlsaxutils.tex
index b4c98ff5d270528076fd9615bd423b3be3ec7e05..64221f59519b52cf6d425d61c9ad1b31f6f95c93 100644 (file)
--- a/Doc/lib/xmlsaxutils.tex
+++ b/Doc/lib/xmlsaxutils.tex
@@ -41,7 +41,7 @@ either in direct use, or as base classes.
   content of \var{data}, attempting to avoid encoding any quote
   characters in the string.  If both single- and double-quote
   characters are already in \var{data}, the double-quote characters
-  will be encoded and \var{data} will be wrapped in doule-quotes.  The
+  will be encoded and \var{data} will be wrapped in double-quotes.  The
   resulting string can be used directly as an attribute value:
 
 \begin{verbatim}