summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Doc/lib/libdecimal.tex2
-rw-r--r--Doc/lib/libhashlib.tex2
-rw-r--r--Doc/lib/libpipes.tex2
-rw-r--r--Doc/lib/tkinter.tex2
4 files changed, 4 insertions, 4 deletions
diff --git a/Doc/lib/libdecimal.tex b/Doc/lib/libdecimal.tex
index c7e66d9..092f038 100644
--- a/Doc/lib/libdecimal.tex
+++ b/Doc/lib/libdecimal.tex
@@ -1180,7 +1180,7 @@ have the same value at various precisions. Is there a way to transform them to
a single recognizable canonical value?
A. The \method{normalize()} method maps all equivalent values to a single
-representive:
+representative:
\begin{verbatim}
>>> values = map(Decimal, '200 200.000 2E2 .02E+4'.split())
diff --git a/Doc/lib/libhashlib.tex b/Doc/lib/libhashlib.tex
index 829849f..e9d0b57 100644
--- a/Doc/lib/libhashlib.tex
+++ b/Doc/lib/libhashlib.tex
@@ -15,7 +15,7 @@ This module implements a common interface to many different secure hash and
message digest algorithms. Included are the FIPS secure hash algorithms SHA1,
SHA224, SHA256, SHA384, and SHA512 (defined in FIPS 180-2) as well as RSA's MD5
algorithm (defined in Internet \rfc{1321}).
-The terms secure hash and message digest are interchangable. Older
+The terms secure hash and message digest are interchangeable. Older
algorithms were called message digests. The modern term is secure hash.
\warning{Some algorithms have known hash collision weaknesses, see the FAQ at the end.}
diff --git a/Doc/lib/libpipes.tex b/Doc/lib/libpipes.tex
index 4e6ea53..1815e09 100644
--- a/Doc/lib/libpipes.tex
+++ b/Doc/lib/libpipes.tex
@@ -8,7 +8,7 @@
The \module{pipes} module defines a class to abstract the concept of
-a \emph{pipeline} --- a sequence of convertors from one file to
+a \emph{pipeline} --- a sequence of converters from one file to
another.
Because the module uses \program{/bin/sh} command lines, a \POSIX{} or
diff --git a/Doc/lib/tkinter.tex b/Doc/lib/tkinter.tex
index f223ff6..405f041 100644
--- a/Doc/lib/tkinter.tex
+++ b/Doc/lib/tkinter.tex
@@ -476,7 +476,7 @@ Tk man pages for the widget in question.
Note that the man pages list "STANDARD OPTIONS" and "WIDGET SPECIFIC
OPTIONS" for each widget. The former is a list of options that are
common to many widgets, the latter are the options that are
-ideosyncratic to that particular widget. The Standard Options are
+idiosyncratic to that particular widget. The Standard Options are
documented on the \manpage{options}{3} man page.
No distinction between standard and widget-specific options is made in