--- critcl-tcllib.txt.bak	Thu Jul 24 18:45:04 2003
+++ critcl-tcllib.txt	Thu Aug 30 09:33:51 2007
@@ -23,3 +23,3 @@
 
-    There are four main possiblities:
+    There are four main possibilities:
        1) library-per-package
@@ -107,3 +107,3 @@
     for a single package. There is also a cost involved in loading
-    each dynamic libary as they have to be loaded from disk and
+    each dynamic library as they have to be loaded from disk and
     relocated in memory. Other concerns are the package namespace
--- dirlayout_install.txt.bak	Wed Apr 16 18:37:06 2003
+++ dirlayout_install.txt	Thu Aug 30 09:34:12 2007
@@ -37,3 +37,3 @@
                 between multiple releases. modules have no
-                version. This can be faked for mdules containing one
+                version. This can be faked for modules containing one
                 package, but not for the modules with more.
@@ -77,3 +77,3 @@
         This not only makes sense for easier handling of installation
-        and package indices, but also in the geater context of
+        and package indices, but also in the greater context of
         wrapping code for deployment.
--- indexing.txt.bak	Wed Apr 23 02:20:05 2003
+++ indexing.txt	Thu Aug 30 09:41:01 2007
@@ -7,3 +7,3 @@
 their pro and contra and makes a choice for Tcllib 1.4. A roadmap of
-changes in the future is made available as appendix.
+changes in the future is made available as an appendix.
 
@@ -29,3 +29,3 @@
 Note I:
-	Whether a solutions is actually applicable depends on external
+	Whether a solution is actually applicable depends on external
 	factors, like the chosen directory layout of an installed
@@ -88,3 +88,3 @@
                         the actual registration of packages, thus
-                        automatically inherits the correct contraints
+                        automatically inherits the correct constraints
                         on the registration of packages. No additional
@@ -187,3 +187,3 @@
                 [[6]]   In contrast to [i2/ad] and [i3/ag] repeated
-                        glob'bing for package index files is
+                        glob'ing for package index files is
                         avoided. This cuts down on costly FS accesses.
@@ -346,4 +346,4 @@
 causes only one index to be read and nothing else. This is followed by
-the all *d solutions, they read the subordinate indices, but do not
-need much globbing. The actual order in this group is difficult to
+the all *d solutions, which read the subordinate indices, but do not
+need much glob'ing. The actual order in this group is difficult to
 determine. I guess that the auto_path extending methods are slower
@@ -351,3 +351,3 @@
 the adding of all, as the latter looks for much more subdirectories.
-The next group oare the *g solutions as they their own globbing too
+The next group are the *g solutions as they perform their own glob'ing too
 beyond that done by the package mgmt.
@@ -385,3 +385,3 @@
 	Joe English strictly opposes any solution modifying the
-	auto_path, violoating his opinion that index scripts should
+	auto_path, violating his opinion that index scripts should
 	have no side-effects beyond registering a package.
@@ -395,3 +395,3 @@
 (Andreas), and a small discussion on the Tcl'ers chat between Don and
-me we took [i4/sd] for the main body of the idnex, and the header of
+me, we took [i4/sd] for the main body of the index, and the header of
 Don's code. Basically the chosen package index is a combination of
@@ -400,6 +400,6 @@
 This is still as easy to generate as [4/sd], the index is also only a
-bit more complex, and speed should be ok too.
+bit more complex, and speed should be okay too.
 
 Don convinced me that while extending auto_path is definitely bad in
-the long-term it is still ok for the short-term and release 1.4.
+the long-term it is still okay for the short-term and release 1.4.
 
--- installation.txt.bak	Wed Apr 16 18:37:06 2003
+++ installation.txt	Thu Aug 30 09:35:41 2007
@@ -37,3 +37,3 @@
 		between multiple releases. modules have no
-		version. This can be faked for mdules containing one
+		version. This can be faked for modules containing one
 		package, but not for the modules with more.
@@ -77,3 +77,3 @@
 	This not only makes sense for easier handling of installation
-	and package indices, but also in the geater context of
+	and package indices, but also in the greater context of
 	wrapping code for deployment.
--- devguide.html.bak	Wed Jan 23 00:29:12 2002
+++ devguide.html	Thu Aug 30 09:42:44 2007
@@ -35,3 +35,3 @@
       following that one. This is to allow the release manager to
-      create patch releases of existing releases distribung important
+      create patch releases of existing releases distributing important
       bugfixes as well.
