From: Andrew M. Kuchling <amk@amk.ca>
Date: Sat, 29 Jul 2006 21:30:21 +0000 (+0000)
Subject: Fix case for 'Unix'
X-Git-Tag: v2.5b3~64
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2d5c8e3bb1325d8cdefa27ddbbbf10a84160c8a9;p=thirdparty%2FPython%2Fcpython.git

Fix case for 'Unix'
---

diff --git a/Doc/lib/libcsv.tex b/Doc/lib/libcsv.tex
index e6008151d682..a9f490dc8872 100644
--- a/Doc/lib/libcsv.tex
+++ b/Doc/lib/libcsv.tex
@@ -76,7 +76,7 @@ If literal newlines are important within a field, users need to read their
 file in a way that preserves the newlines. The behavior before 2.5 would
 introduce spurious characters into quoted fields, with no way for the user
 to control that behavior. The previous behavior caused considerable
-problems, particularly on platforms that did not use the unix line ending
+problems, particularly on platforms that did not use the Unix line ending
 conventions, or with files that originated on those platforms --- users were
 finding mysterious newlines where they didn't expect them]{2.5}
 
diff --git a/Doc/lib/tkinter.tex b/Doc/lib/tkinter.tex
index 405f041f6c95..0cc8d58d9825 100644
--- a/Doc/lib/tkinter.tex
+++ b/Doc/lib/tkinter.tex
@@ -319,7 +319,7 @@ the name of a widget.
 \item[\var{options} ]
 configure the widget's appearance and in some cases, its
 behavior.  The options come in the form of a list of flags and values.
-Flags are proceeded by a `-', like unix shell command flags, and
+Flags are proceeded by a `-', like Unix shell command flags, and
 values are put in quotes if they are more than one word.
 \end{description}