summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorhobbs <hobbs>2007-09-10 22:59:05 (GMT)
committerhobbs <hobbs>2007-09-10 22:59:05 (GMT)
commitcee6e473efdc4c78d561ac2a1774a54855438450 (patch)
tree0bfa05aa3cbcd1fde539232dd73868908df8b3c3
parent290f79c9005e4406f4e00249319730e87fb479bd (diff)
downloadtk-cee6e473efdc4c78d561ac2a1774a54855438450.zip
tk-cee6e473efdc4c78d561ac2a1774a54855438450.tar.gz
tk-cee6e473efdc4c78d561ac2a1774a54855438450.tar.bz2
typo corrections [Bug 1788682]
-rw-r--r--ChangeLog4
-rw-r--r--unix/README6
2 files changed, 7 insertions, 3 deletions
diff --git a/ChangeLog b/ChangeLog
index 724f9f2..11e3805 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2007-09-10 Jeff Hobbs <jeffh@ActiveState.com>
+
+ * unix/README: typo corrections [Bug 1788682]
+
2007-09-10 Don Porter <dgp@users.sourceforge.net>
* generic/tkConsole.c: Revise all Tcl_InitStubs() calls to restore
diff --git a/unix/README b/unix/README
index ce63e0e..543948d 100644
--- a/unix/README
+++ b/unix/README
@@ -20,7 +20,7 @@ SGI, as well as PCs running Linux, BSDI, and SCO UNIX. To compile for
a PC running Windows, see the README file in the directory ../win. To
compile for MacOSX, see the README file in the directory ../macosx.
-RCS: @(#) $Id: README,v 1.22 2005/12/03 00:41:48 das Exp $
+RCS: @(#) $Id: README,v 1.23 2007/09/10 22:59:06 hobbs Exp $
How To Compile And Install Tk:
------------------------------
@@ -100,7 +100,7 @@ How To Compile And Install Tk:
(g) Type "make install" to install Tk's binaries and script files in
standard places. You'll need write permission on the installation
- directoryies to do this. The installation directories are
+ directories to do this. The installation directories are
determined by the "configure" script and may be specified with
the --prefix and --exec-prefix options to "configure". See the
Makefile for information on what directories were chosen; you
@@ -135,7 +135,7 @@ processed. If any errors occur, you'll see a much more substantial
printout for each error. In order to avoid false error reports, be sure
to run the tests with an empty resource database (e.g., remove your
.Xdefaults file or delete any entries starting with *). Also, don't
-try to do anything else with your display or keyboard whlie the tests
+try to do anything else with your display or keyboard while the tests
are running, or you may get false violations. See the README file in
the "tests" directory for more information on the test suite.