doc: Fix doubled up word in "Sources" chapter, plus some tiny improvements.

Signed-off-by: Benno Schulenberg <bensberg@justemail.net>

diff --git a/gettext-tools/doc/ChangeLog b/gettext-tools/doc/ChangeLog
index c27758d2abde269d45db22c57f549d038bf5cc1d..95740891a784037451a5eb9ee28593ba651b5d97 100644 (file)
--- a/gettext-tools/doc/ChangeLog
+++ b/gettext-tools/doc/ChangeLog
@@ -1,3 +1,7 @@
+2014-01-12  Benno Schulenberg <bensberg@justemail.net>  (tiny change)
+
+       * gettext.texi (c-format Flag): Wording fixes.
+
 2013-12-17  Daiki Ueno  <ueno@gnu.org>
 
        * gettext.texi (Installers): Fix wording.

diff --git a/gettext-tools/doc/gettext.texi b/gettext-tools/doc/gettext.texi
index d87315886d39db36c6392e5364700e4d117bd10b..9e2ac3925ed22bcfa0187016305167c74e9e4bd8 100644 (file)
--- a/gettext-tools/doc/gettext.texi
+++ b/gettext-tools/doc/gettext.texi
@@ -2469,13 +2469,13 @@ is changed but of course the arguments in the @code{printf} don't have.
 This will most probably lead to problems because now the length of the
 string is regarded as the address.
 
-To prevent errors at runtime caused by translations the @code{msgfmt}
+To prevent errors at runtime caused by translations, the @code{msgfmt}
 tool can check statically whether the arguments in the original and the
 translation string match in type and number.  If this is not the case
 and the @samp{-c} option has been passed to @code{msgfmt}, @code{msgfmt}
-will give an error and refuse to produce a MO file.  Thus consequent
+will give an error and refuse to produce a MO file.  Thus consistent
 use of @samp{msgfmt -c} will catch the error, so that it cannot cause
-cause problems at runtime.
+problems at runtime.
 
 @noindent
 If the word order in the above German translation would be correct one
@@ -2488,12 +2488,12 @@ would have to write
 @noindent
 The routines in @code{msgfmt} know about this special notation.
 
-Because not all strings in a program must be format strings it is not
+Because not all strings in a program will be format strings, it is not
 useful for @code{msgfmt} to test all the strings in the @file{.po} file.
 This might cause problems because the string might contain what looks
 like a format specifier, but the string is not used in @code{printf}.
 
-Therefore the @code{xgettext} adds a special tag to those messages it
+Therefore @code{xgettext} adds a special tag to those messages it
 thinks might be a format string.  There is no absolute rule for this,
 only a heuristic.  In the @file{.po} file the entry is marked using the
 @code{c-format} flag in the @code{#,} comment line (@pxref{PO Files}).