Fix typos in manual.

* doc/manywarnings.texi, doc/gnulib-intro.texi: Fix typos.

Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>

diff --git a/ChangeLog b/ChangeLog
index f6ed8158c47e907e9c2e4070ad22a06bddd0bfb2..6ff32bca16bdb6ca84f63b6b2eb1c69b3befa596 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2008-12-07  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       * doc/manywarnings.texi, doc/gnulib-intro.texi: Fix typos.
+
 2008-12-06  Bruno Haible  <bruno@clisp.org>
 
        * lib/c-stack.h (c_stack_action): Clarify possible side effects.

diff --git a/doc/gnulib-intro.texi b/doc/gnulib-intro.texi
index fa282a4b29512b39135700a9121176782def052d..a10ebeb92f4647b63feb234fb788027ec709b360 100644 (file)
--- a/doc/gnulib-intro.texi
+++ b/doc/gnulib-intro.texi
@@ -16,7 +16,7 @@ maintain.
 
 @item
 Security: Gnulib provides functions that are immune against vulnerabilities
-that plagues the uses of the corresponding commonplace functions. For
+that plague the uses of the corresponding commonplace functions. For
 example, @code{asprintf}, @code{canonicalize_file_name} are not affected
 by buffer sizing problems that affect @code{sprintf}, @code{realpath}.
 @code{openat} does not have the race conditions that @code{open} has. Etc.

diff --git a/doc/manywarnings.texi b/doc/manywarnings.texi
index 2ad807e7509ef1d0b892eecab8bc138fcb3d5c92..d3edf1fb524cb4894981e125772a246036b2f06d 100644 (file)
--- a/doc/manywarnings.texi
+++ b/doc/manywarnings.texi
@@ -3,7 +3,7 @@
 
 The @code{manywarnings} module allows you to enable as many GCC warnings as
 possible for your package. The purpose is to protect against introducing new
-code that triggers warning that weren't already triggered by the existing code
+code that triggers warnings that weren't already triggered by the existing code
 base.
 
 An example use of the module is as follows:
@@ -25,11 +25,11 @@ done
 @end smallexample
 
 This module is meant to be used by developers who are not very experienced
-regarding the various GCC warning option. In the beginning you will set the
+regarding the various GCC warning options. In the beginning you will set the
 list of undesired warnings (@samp{nw} in the example above) to empty, and
 compile the package with all possible warnings enabled. The GCC option
 @code{-fdiagnostics-show-option}, available in GCC 4.1 or newer, helps
-understanding which warnings is originated from which option. Then you will
+understanding which warnings originated from which option. Then you will
 go through the list of warnings. You will likely deactivate warnings that
 occur often and don't point to mistakes in the code, by adding them to the
 @samp{nw} variable, then reconfiguring and recompiling. When warnings point