strerror_r: fix OpenBSD behavior on out-of-range

[pspp] / doc / manywarnings.texi

diff --git a/doc/manywarnings.texi b/doc/manywarnings.texi
index 2ad807e7509ef1d0b892eecab8bc138fcb3d5c92..cb2cf295ef6db27eeb71ea20dcef41f5b47e1aa0 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:
@@ -18,18 +18,18 @@ nw="$nw -Wtraditional"          # All compilers nowadays support ANSI C
 nw="$nw -Wconversion"           # These warnings usually don't point to mistakes.
 nw="$nw -Wsign-conversion"      # Likewise.
 # Enable all GCC warnings not in this list.
-gl_MANYWARN_COMPLEMENT[warnings], [$warnings], [$nw])
+gl_MANYWARN_COMPLEMENT([warnings], [$warnings], [$nw])
 for w in $warnings; do
   gl_WARN_ADD([$w])
 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