INN commit: trunk (doc/pod/tdx-util.pod innd/README)

[INN Commit]

    Date: Monday, January 4, 2010 @ 11:49:14
  Author: iulius
Revision: 8879

Typo:  "correspondance" -> "correspondence".

Modified:
  trunk/doc/pod/tdx-util.pod
  trunk/innd/README

----------------------+
 doc/pod/tdx-util.pod |    4 ++--
 innd/README          |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Modified: doc/pod/tdx-util.pod
===================================================================
--- doc/pod/tdx-util.pod	2009-12-31 09:25:42 UTC (rev 8878)
+++ doc/pod/tdx-util.pod	2010-01-04 19:49:14 UTC (rev 8879)
@@ -62,7 +62,7 @@
 Audit the entire overview database for problems.  This runs the internal
 consistency checks built into the tradindexed overview implementation,
 checking such things as the validity and reachability of all group index
-entries, the format of the individual overview entries, the correspondance
+entries, the format of the individual overview entries, the correspondence
 of index entries to overview data, and similar such things.  No changes
 will be made to the database, but problems will be reported to standard
 error.
@@ -94,7 +94,7 @@
 detected where possible. This runs the internal consistency checks built
 into the tradindexed overview implementation, checking such things as the
 validity and reachability of all group index entries, the format of the
-individual overview entries, the correspondance of index entries to
+individual overview entries, the correspondence of index entries to
 overview data, and similar such things.  The strategy used when fixing
 problems is to throw away data that's unrecoverable, so be warned that
 using this option may result in inaccessible articles if their overview

Modified: innd/README
===================================================================
--- innd/README	2009-12-31 09:25:42 UTC (rev 8878)
+++ innd/README	2010-01-04 19:49:14 UTC (rev 8879)
@@ -54,7 +54,7 @@
 
     CHANreadloop is the main processing loop of innd.  As long as innd is
     running, it will be inside that function.  The core channel code
-    maintains a table of channels, which have a one-to-one correspondance
+    maintains a table of channels, which have a one-to-one correspondence
     with open file descriptors, and three file descriptor sets.  Each
     channel is generally in one of the three sets (reading, writing, or
     sleeping) at any given time.  The states should generally be