Fix misspelling

Fix misspelling using  http://github.com/lyda/misspell-check

5 files changed, 11 insertions, 9 deletions

diff --git a/CHANGES b/CHANGES
index 0df413a..452bcee 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,6 @@
 1.17 -> 2.0:
+    - devzero2000: fix misspelling
+      Fix misspelling using  http://github.com/lyda/misspell-check
     - devzero2000: quote AC_PREREQ in configure.ac
       for a old bug autoupdate don't do it before autoconf v2.66
       (http://lists.gnu.org/archive/html/autoconf-patches/2010-06/msg00014.html)
diff --git a/README b/README
index c66432d..fbdc0f2 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-This is the popt(3) command line option parsing library. While it is similiar
+This is the popt(3) command line option parsing library. While it is similar
 to getopt(3), it contains a number of enhancements, including:
 
 	1) popt is fully reentrant
diff --git a/lookup3.c b/lookup3.c
index 36f43e5..17313cf 100644
--- a/lookup3.c
+++ b/lookup3.c
@@ -275,7 +275,7 @@ uint32_t jlu32l(uint32_t h, const void *key, size_t size)
 	 * rest of the string.  Every machine with memory protection I've seen
 	 * does it on word boundaries, so is OK with this.  But VALGRIND will
 	 * still catch it and complain.  The masking trick does make the hash
-	 * noticably faster for short strings (like English words).
+	 * noticeably faster for short strings (like English words).
 	 */
 #ifndef VALGRIND
 
@@ -481,7 +481,7 @@ void jlu32lpair(const void *key, size_t size, uint32_t *pc, uint32_t *pb)
 	 * rest of the string.  Every machine with memory protection I've seen
 	 * does it on word boundaries, so is OK with this.  But VALGRIND will
 	 * still catch it and complain.  The masking trick does make the hash
-	 * noticably faster for short strings (like English words).
+	 * noticeably faster for short strings (like English words).
 	 */
 #ifndef VALGRIND
 
@@ -685,7 +685,7 @@ uint32_t jlu32b(uint32_t h, const void *key, size_t size)
 	 * rest of the string.  Every machine with memory protection I've seen
 	 * does it on word boundaries, so is OK with this.  But VALGRIND will
 	 * still catch it and complain.  The masking trick does make the hash
-	 * noticably faster for short strings (like English words).
+	 * noticeably faster for short strings (like English words).
 	 */
 #ifndef VALGRIND
 
diff --git a/popt.3 b/popt.3
index ddc82c1..f768199 100644
--- a/popt.3
+++ b/popt.3
@@ -210,7 +210,7 @@ If the \fIargInfo\fR value is bitwise or'd with \fBPOPT_ARGFLAG_DOC_HIDDEN\fR,
 the argument will not be shown in help output.
 .sp
 If the \fIargInfo\fR value is bitwise or'd with \fBPOPT_ARGFLAG_SHOW_DEFAULT\fR,
-the inital value of the arg will be shown in help output.
+the initial value of the arg will be shown in help output.
 .sp
 The final structure in the table should have all the pointer values set
 .RB "to " NULL " and all the arithmetic values set to 0, marking the "
@@ -233,7 +233,7 @@ automatic help generation is being used, the \fIdescrip\fR field should
 contain a overall description of the option table being included.
 .sp
 The other special option table entry type tells popt to call a function (a
-callback) when any option in that table is found. This is especially usefull
+callback) when any option in that table is found. This is especially useful
 when included option tables are being used, as the program which provides
 the top-level option table doesn't need to be aware of the other options
 which are provided by the included table. When a callback is set for
@@ -517,7 +517,7 @@ These two functions make popt error handling trivial for most
 applications. When an error is detected from most of the functions, 
 an error message is printed along with the error string from 
 .BR poptStrerror() ". When an error occurs during argument parsing, "
-code similiar to the following displays a useful error message:
+code similar to the following displays a useful error message:
 .sp
 .nf
 fprintf(stderr, "%s: %s\\n",
@@ -611,7 +611,7 @@ Although popt is usually used for parsing arguments already divided into
 .RI "an " argv "-style array, some programs need to parse strings that "
 are formatted identically to command lines. To facilitate this, popt 
 provides a function that parses a string into an array of strings, 
-using rules similiar to normal shell parsing.
+using rules similar to normal shell parsing.
 .sp
 .nf
 .B "#include <popt.h>"
diff --git a/popt.h b/popt.h
index f0a9c96..9d01747 100644
--- a/popt.h
+++ b/popt.h
@@ -426,7 +426,7 @@ int poptReadConfigFile(poptContext con, const char * fn)
 /** \ingroup popt
  * Read configuration file(s).
  * Colon separated files to read, looping over poptReadConfigFile().
- * Note that an '@' character preceeding a path in the list will
+ * Note that an '@' character preceding a path in the list will
  * also perform additional sanity checks on the file before reading.
  * @param con		context
  * @param paths		colon separated file name(s) to read