Fix a bunch of typos in documentation, docstrings and comments.

(From SF patch #810751)

6 files changed, 6 insertions, 6 deletions

diff --git a/Doc/ext/newtypes.tex b/Doc/ext/newtypes.tex
index 230db9e..743cb5a 100644
--- a/Doc/ext/newtypes.tex
+++ b/Doc/ext/newtypes.tex
@@ -685,7 +685,7 @@ when objects are involved in cycles.  For example, consider:
 In this example, we create a list that contains itself. When we delete
 it, it still has a reference from itself. It's reference count doesn't
 drop to zero.  Fortunately, Python's cyclic-garbage collector will
-eventually figure out that that the list is garbage and free it.
+eventually figure out that the list is garbage and free it.
 
 In the second version of the \class{Noddy} example, we allowed any
 kind of object to be stored in the \member{first} or \member{last}
diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex
index f36ebfa..4d62094 100644
--- a/Doc/lib/libprofile.tex
+++ b/Doc/lib/libprofile.tex
@@ -407,7 +407,7 @@ identifying the basis of a sort (example: \code{'time'} or
 \code{'name'}).
 
 When more than one key is provided, then additional keys are used as
-secondary criteria when the there is equality in all keys selected
+secondary criteria when there is equality in all keys selected
 before them.  For example, \samp{sort_stats('name', 'file')} will sort
 all the entries according to their function name, and resolve all ties
 (identical function names) by sorting by file name.
diff --git a/Doc/lib/libregex.tex b/Doc/lib/libregex.tex
index bd86db5..93c389a 100644
--- a/Doc/lib/libregex.tex
+++ b/Doc/lib/libregex.tex
@@ -247,7 +247,7 @@ expressions.)
   \code{match()} and \code{search()}.  (Already compiled expression
   objects are not affected.)  The argument is an integer which is the
   OR of several flag bits.  The return value is the previous value of
-  the syntax flags.  Names for the flags are defined in the standard 
+  the syntax flags.  Names for the flags are defined in the standard
   module \code{regex_syntax}\refstmodindex{regex_syntax}; read the
   file \file{regex_syntax.py} for more information.
 \end{funcdesc}
diff --git a/Doc/ref/ref6.tex b/Doc/ref/ref6.tex
index 4e966bf..e3b4427 100644
--- a/Doc/ref/ref6.tex
+++ b/Doc/ref/ref6.tex
@@ -149,7 +149,7 @@ target.
 
 \item
 If the target list is a comma-separated list of targets: The object
-must be a sequence with the same number of items as the there are
+must be a sequence with the same number of items as there are
 targets in the target list, and the items are assigned, from left to
 right, to the corresponding targets.  (This rule is relaxed as of
 Python 1.5; in earlier versions, the object had to be a tuple.  Since
diff --git a/Doc/texinputs/python.sty b/Doc/texinputs/python.sty
index 85fe52f..d8071ee 100644
--- a/Doc/texinputs/python.sty
+++ b/Doc/texinputs/python.sty
@@ -1,5 +1,5 @@
 %
-% python.sty for the Python docummentation  [works only with with Latex2e]
+% python.sty for the Python docummentation  [works only with Latex2e]
 %
 
 \NeedsTeXFormat{LaTeX2e}[1995/12/01]
diff --git a/Doc/whatsnew/whatsnew20.tex b/Doc/whatsnew/whatsnew20.tex
index 86d54d7..1728e1a 100644
--- a/Doc/whatsnew/whatsnew20.tex
+++ b/Doc/whatsnew/whatsnew20.tex
@@ -1000,7 +1000,7 @@ every starting and end tag encountered by the parser, the
 \method{characters()} method is called for every chunk of character
 data, and so forth.
 
-The advantage of the event-driven approach is that that the whole
+The advantage of the event-driven approach is that the whole
 document doesn't have to be resident in memory at any one time, which
 matters if you are processing really huge documents.  However, writing
 the SAX handler class can get very complicated if you're trying to