Patch #1080684: typo repair. Thanks George Yoshida!

- Doc/lib/libbase64.tex
s/algorith/algorithm

- Doc/lib/libpickle.tex
s/interchangable/interchangeable

- Doc/lib/libxmlrpclib.tex
s/{_cmp__}/{__cmp__}

leading underscore needs to be double, not single.

- Doc/ref/ref6.tex
0/1 => False/True

diff --git a/Doc/lib/libbase64.tex b/Doc/lib/libbase64.tex
index b51f8c820bc7c18a046c09e08ec85c97f7acdac6..747d8374fc9fc2d3698f1f0dfa18d09c48f15858 100644 (file)
--- a/Doc/lib/libbase64.tex
+++ b/Doc/lib/libbase64.tex
@@ -12,7 +12,7 @@ This module provides data encoding and decoding as specified in
 \rfc{3548}.  This standard defines the Base16, Base32, and Base64
 algorithms for encoding and decoding arbitrary binary strings into
 text strings that can be safely sent by email, used as parts of URLs,
-or included as part of an HTTP POST request.  The encoding algorith is
+or included as part of an HTTP POST request.  The encoding algorithm is
 not the same as the \program{uuencode} program.
 
 There are two interfaces provided by this module.  The modern

diff --git a/Doc/lib/libpickle.tex b/Doc/lib/libpickle.tex
index 4013432a91ff9b24ce17ec8cb3e97d530e092d75..cf526a069f0e6f3abf14ffa3ed78d3426defac75 100644 (file)
--- a/Doc/lib/libpickle.tex
+++ b/Doc/lib/libpickle.tex
@@ -825,7 +825,7 @@ data streams.}
 
 There are additional minor differences in API between \module{cPickle}
 and \module{pickle}, however for most applications, they are
-interchangable.  More documentation is provided in the
+interchangeable.  More documentation is provided in the
 \module{pickle} module documentation, which
 includes a list of the documented differences.
 

diff --git a/Doc/lib/libxmlrpclib.tex b/Doc/lib/libxmlrpclib.tex
index 207839e407b02aed65683b106d743854437a7a1e..298a03dde73a1cf057d75094c8e86238923caa33 100644 (file)
--- a/Doc/lib/libxmlrpclib.tex
+++ b/Doc/lib/libxmlrpclib.tex
@@ -184,7 +184,7 @@ Write the XML-RPC encoding of this DateTime item to the out stream object.
 \end{methoddesc}
 
 It also supports certain of Python's built-in operators through 
-\method{_cmp__} and \method{__repr__} methods.
+\method{__cmp__} and \method{__repr__} methods.
 
 
 \subsection{Binary Objects \label{binary-objects}}
@@ -211,7 +211,7 @@ stream object.
 \end{methoddesc}
 
 It also supports certain of Python's built-in operators through a
-\method{_cmp__()} method.
+\method{__cmp__()} method.
 
 
 \subsection{Fault Objects \label{fault-objects}}

diff --git a/Doc/ref/ref6.tex b/Doc/ref/ref6.tex
index 153ddf7743d1befaea33837bc3780b1f2d7463e5..8a2a6655ace297ba9d3682979bff1cc78a3f8c70 100644 (file)
--- a/Doc/ref/ref6.tex
+++ b/Doc/ref/ref6.tex
@@ -84,11 +84,12 @@ if __debug__:
 These equivalences assume that \code{__debug__}\ttindex{__debug__} and
 \exception{AssertionError}\exindex{AssertionError} refer to the built-in
 variables with those names.  In the current implementation, the
-built-in variable \code{__debug__} is 1 under normal circumstances, 0
-when optimization is requested (command line option -O).  The current
-code generator emits no code for an assert statement when optimization
-is requested at compile time.  Note that it is unnecessary to include
-the source code for the expression that failed in the error message;
+built-in variable \code{__debug__} is \code{True} under normal
+circumstances, \code{False} when optimization is requested (command line
+option -O).  The current code generator emits no code for an assert
+statement when optimization is requested at compile time.  Note that it
+is unnecessary to include the source code for the expression that failed
+in the error message;
 it will be displayed as part of the stack trace.
 
 Assignments to \code{__debug__} are illegal.  The value for the