typos

[Ralf Wildenhues]

Hello bug-gnu-gettext (and thus bug-gnu-utils ;-) readers,

the patches below fix some typos and spelling inconsistencies
(en_UK -> en_US) in the CVS Gettext documentation files.

Cheers,
Ralf

gettext-runtime/doc:
        * nls.texi, rt-gettext.texi, rt-ngettext.texi: Fix some typos.

gettext-runtime/libasprintf:
        * autosprintf.texi: Fix some typos.

gettext-tools/doc:
        * gettext.texi, msgattrib.texi, msgcat.texi, msgcomm.texi,
        msgfilter.texi, msgfmt.texi, xgettext.texi: Fix some typos.

Index: gettext-runtime/doc/nls.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-runtime/doc/nls.texi,v
retrieving revision 1.16
diff -u -r1.16 nls.texi
--- gettext-runtime/doc/nls.texi        20 Jul 2006 18:31:52 -0000      1.16
+++ gettext-runtime/doc/nls.texi        6 Aug 2006 19:39:05 -0000
@@ -76,7 +76,7 @@
 contained within this package, usually in the @file{intl/} subdirectory,
 so prior installation of the GNU @code{gettext} package is @emph{not}
 required.  Installers may use special options at configuration time for
-changing the default behaviour.  The commands:
+changing the default behavior.  The commands:
 
 @example
 ./configure --with-included-gettext
@@ -93,7 +93,7 @@
 will probably detect the previously built and installed @file{libintl.a}
 file and will decide to use this.  This might not be desirable.
 You should use the more recent version of the GNU @code{gettext}
-library.  I.e. if the file @file{intl/VERSION} shows that the library
+library.  I.e., if the file @file{intl/VERSION} shows that the library
 which comes with this package is more recent, you should use
 
 @example
@@ -211,7 +211,7 @@
 coordinator for all translator teams.
 
 The English team is special.  It works at improving and uniformizing
-the terminology in use.  Proven linguistic skill are praised
-more than programming skill, here.
+the terminology in use.  Proven linguistic skills are praised
+more than programming skills here.
 
 @node Available Packages
Index: gettext-runtime/doc/rt-gettext.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-runtime/doc/rt-gettext.texi,v
retrieving revision 1.2
diff -u -r1.2 rt-gettext.texi
--- gettext-runtime/doc/rt-gettext.texi 11 Jul 2004 13:16:41 -0000      1.2
+++ gettext-runtime/doc/rt-gettext.texi 6 Aug 2006 19:39:05 -0000
@@ -25,7 +25,7 @@
 with the @samp{echo} program or shell built-in.  The escape sequences
 @samp{\a}, @samp{\b}, @samp{\c}, @samp{\f}, @samp{\n}, @samp{\r}, @samp{\t},
 @samp{\v}, @samp{\\}, and @samp{\} followed by one to three octal digits, are
-interpreted like the SystemV @samp{echo} program does.
+interpreted like the System V @samp{echo} program does.
 
 @item -E
 @opindex address@hidden, @code{gettext} option}
Index: gettext-runtime/doc/rt-ngettext.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-runtime/doc/rt-ngettext.texi,v
retrieving revision 1.2
diff -u -r1.2 rt-ngettext.texi
--- gettext-runtime/doc/rt-ngettext.texi        11 Jul 2004 13:16:41 -0000      
1.2
+++ gettext-runtime/doc/rt-ngettext.texi        6 Aug 2006 19:39:05 -0000
@@ -24,7 +24,7 @@
 with the @samp{gettext} program.  The escape sequences
 @samp{\a}, @samp{\b}, @samp{\c}, @samp{\f}, @samp{\n}, @samp{\r}, @samp{\t},
 @samp{\v}, @samp{\\}, and @samp{\} followed by one to three octal digits, are
-interpreted like the SystemV @samp{echo} program does.
+interpreted like the System V @samp{echo} program does.
 
 @item -E
 @opindex address@hidden, @code{ngettext} option}
Index: gettext-runtime/libasprintf/autosprintf.texi
===================================================================
RCS file: 
/cvsroot/gettext/gettext/gettext-runtime/libasprintf/autosprintf.texi,v
retrieving revision 1.5
diff -u -r1.5 autosprintf.texi
--- gettext-runtime/libasprintf/autosprintf.texi        12 Apr 2006 15:02:09 
-0000      1.5
+++ gettext-runtime/libasprintf/autosprintf.texi        6 Aug 2006 19:39:06 
-0000
@@ -134,7 +134,7 @@
 
 An instance of class @code{autosprintf} just contains a string with the
 formatted output result. Such an instance is usually allocated as an
-automatic storage variable, i.e. on the stack, not with @code{new} on the
+automatic storage variable, i.e., on the stack, not with @code{new} on the
 heap.
 
 The constructor @code{autosprintf (const char *format, ...)} takes a format
Index: gettext-tools/doc/gettext.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/gettext.texi,v
retrieving revision 1.95
diff -u -r1.95 gettext.texi
--- gettext-tools/doc/gettext.texi      30 Jun 2006 14:28:20 -0000      1.95
+++ gettext-tools/doc/gettext.texi      6 Aug 2006 19:39:36 -0000
@@ -596,7 +596,7 @@
 of programs already internationalized, one gives the program all
 needed information so that it can adapt itself to handle its input
 and output in a fashion which is correct for some native language and
-cultural habits.  This is a particularisation process, by which generic
+cultural habits.  This is a particularization process, by which generic
 methods already implemented in an internationalized program are used
 in specific ways.  The programming environment puts several functions
 to the programmers disposal which allow this runtime configuration.
@@ -1653,7 +1653,7 @@
 @end example
 
 @noindent
-The ambiguity in this message makes it ununderstandable: Is the program
+The ambiguity in this message makes it incomprehensible: Is the program
 attempting to set something on fire? Does it mean "The given object does
 not match the template"? Does it mean "The template does not fit for any
 of the objects"?
@@ -1727,7 +1727,7 @@
 merge them if the two sentences are related to each other, because then it
 makes it easier for the translator to understand and translate both.  On
 the other hand, if one of the two messages is a stereotypic one, occurring
-in other places as well, you will do a favour to the translator by not
+in other places as well, you will do a favor to the translator by not
 merging the two.  (Identical messages occurring in several places are
 combined by xgettext, so the translator has to handle them once only.)
 
@@ -1751,7 +1751,7 @@
 
 @cindex string concatenation
 @cindex concatenation of strings
-Hardcoded string concatenation is sometimes used to construct English
+Hard-coded string concatenation is sometimes used to construct English
 strings:
 
 @example
@@ -1818,7 +1818,7 @@
 @cindex Java, string concatenation
 @cindex C#, string concatenation
 All this applies to other programming languages as well.  For example, in
-Java and C#, string contenation is very frequently used, because it is a
+Java and C#, string concatenation is very frequently used, because it is a
 compiler built-in operator.  Like in C, in Java, you would change
 
 @example
@@ -1935,7 +1935,7 @@
 translation in some language, for the package being internationalized.
 
 @emindex @code{etags}, using for marking strings
-The set of program sources, targetted by the PO mode commands describe
+The set of program sources, targeted by the PO mode commands describe
 here, should have an Emacs tags table constructed for your project,
 prior to using these PO file commands.  This is easy to do.  In any
 shell window, change the directory to the root of your project, then
@@ -2156,7 +2156,7 @@
 exists because the original code does not pass any parameters.
 
 @code{xgettext} of course could make a wrong decision the other way
-round, i.e. a string marked as a format string actually is not a format
+round, i.e., a string marked as a format string actually is not a format
 string.  In this case the @code{msgfmt} might give too many warnings and
 would prevent translating the @file{.po} file.  The method to prevent
 this wrong decision is similar to the one used above, only the comment
@@ -2287,7 +2287,7 @@
            manual, section Names.  Note this is actually a non-ASCII
            name: The first name is (with Unicode escapes)
            "Fran\u00e7ois" or (with HTML entities) "François".
-           Pronounciation is like "fraa-swa pee-nar".  */
+           Pronunciation is like "fraa-swa pee-nar".  */
         _("Francois Pinard"));
 @end group
 @end example
@@ -2309,7 +2309,7 @@
 #. manual, section Names.  Note this is actually a non-ASCII
 #. name: The first name is (with Unicode escapes)
 #. "Fran\u00e7ois" or (with HTML entities) "François".
-#. Pronounciation is like "fraa-swa pee-nar".
+#. Pronunciation is like "fraa-swa pee-nar".
 msgid "Francois Pinard"
 msgstr "\phi\rho\alpha\sigma\omicron\alpha \pi\iota\nu\alpha\rho"
        " (Francois Pinard)"
@@ -2323,7 +2323,7 @@
 has set up a POT file and translation domain consisting of program author
 names, with better facilities for the translator than those presented here.
 Namely, there the original name is written directly in Unicode (rather
-than with Unicode escapes or HTML entities), and the pronounciation is
+than with Unicode escapes or HTML entities), and the pronunciation is
 denoted using the International Phonetic Alphabet (see
 @url{http://www.wikipedia.org/wiki/International_Phonetic_Alphabet}).
 
@@ -2428,7 +2428,7 @@
 @end smallexample
 
 In other words, @code{dgettext} is used instead of @code{gettext}.
-Similary, the @code{dngettext} function should be used in place of the
+Similarly, the @code{dngettext} function should be used in place of the
 @code{ngettext} function.
 @end enumerate
 
@@ -2519,7 +2519,7 @@
 understood.
 @item Strings which make invalid assumptions about notation of date, time or
 money.
address@hidden Pluralisation problems.
address@hidden Pluralization problems.
 @item Incorrect English spelling.
 @item Incorrect formatting.
 @end itemize
@@ -3221,7 +3221,7 @@
 most other purposes, usually call for revision by the translator.
 Those may be produced by applying the program @code{msgmerge} to
 update an older translated PO files according to a new PO template
-file, when this tool hypothesises that some new @code{msgid} has
+file, when this tool hypothesizes that some new @code{msgid} has
 been modified only slightly out of an older one, and chooses to pair
 what it thinks to be the old translation for the new modified entry.
 The slight alteration in the original string (the @code{msgid} string)
@@ -3501,7 +3501,7 @@
 It is possible to arrange so, whenever editing an untranslated
 entry, the @address@hidden command be automatically executed.  If you set
 @code{po-auto-edit-with-msgid} to @code{t}, the translation gets
-initialised with the original string, in case none exists already.
+initialized with the original string, in case none exists already.
 The default value for @code{po-auto-edit-with-msgid} is @code{nil}.
 
 @emindex starting a string translation
@@ -3992,16 +3992,16 @@
 in that way that @code{msgid} fields should be written @emph{exactly}
 the same way.  It is possible to write @code{msgid} fields in various
 ways for representing the same string, different writing would break the
-proper behaviour of the auxiliary file commands of PO mode.  This is not
+proper behavior of the auxiliary file commands of PO mode.  This is not
 expected to be much a problem in practice, as most existing PO files have
 their @code{msgid} entries written by the same GNU @code{gettext} tools.
 
 @efindex address@hidden, PO Mode command}
 However, PO files initially created by PO mode itself, while marking
-strings in source files, are normalised differently.  So are PO
-files resulting of the the @samp{M-x normalize} command.  Until these
+strings in source files, are normalized differently.  So are PO
+files resulting of the @samp{M-x normalize} command.  Until these
 discrepancies between PO mode and other GNU @code{gettext} tools get
-fully resolved, the translator should stay aware of normalisation issues.
+fully resolved, the translator should stay aware of normalization issues.
 
 @node Compendium,  , Auxiliary, PO Mode
 @subsection Using Translation Compendia
@@ -4041,7 +4041,7 @@
 @end example
 
 By default, @code{msgcat} will accumulate divergent translations
-for the same string.  Those occurences will be marked as @code{fuzzy}
+for the same string.  Those occurrences will be marked as @code{fuzzy}
 and highly visible decorated; calling @code{msgcat} on
 @file{file1.po}:
 
@@ -4275,7 +4275,7 @@
 For the tasks for which a combination of @samp{msgattrib}, @samp{msgcat} etc.
 is not sufficient, a set of C functions is provided in a library, to make it
 possible to process PO files in your own programs.  When you use this library,
-you don't need to write routines to parse the PO file; instead, you retreive
+you don't need to write routines to parse the PO file; instead, you retrieve
 a pointer in memory to each of messages contained in the PO file.  Functions
 for writing PO files are not provided at this time.
 
@@ -4503,7 +4503,7 @@
 somewhat useless.  But the MO file format is general enough so other
 interfaces would be later possible, if for example, we ever want to
 implement wide characters right in MO files, where @key{NUL} bytes may
-accidently appear.  (No, we don't want to have wide characters in MO
+accidentally appear.  (No, we don't want to have wide characters in MO
 files.  They would make the file unnecessarily large, and the
 @samp{wchar_t} type being platform dependent, MO files would be
 platform dependent as well.)
@@ -4611,7 +4611,7 @@
 user can happily live with it.  But programmers hate it (at least I and
 some others address@hidden)
 
-But we must not forget one point: after all the trouble with transfering
+But we must not forget one point: after all the trouble with transferring
 the rights on Unix(tm) they at last came to X/Open, the very same who
 published this specification.  This leads me to making the prediction
 that this interface will be in future Unix standards (e.g. Spec1170) and
@@ -5158,7 +5158,7 @@
 
 The consequence of this is that application writers should not try to
 solve the problem in their code.  This would be localization since it is
-only usable for certain, hardcoded language environments.  Instead the
+only usable for certain, hard-coded language environments.  Instead the
 extended @code{gettext} interface should be used.
 
 These extra functions are taking instead of the one key string two
@@ -5223,7 +5223,7 @@
 Therefore the solution implemented is to allow the translator to specify
 the rules of how to select the plural form.  Since the formula varies
 with every language this is the only viable solution except for
-hardcoding the information in the code (which still would require the
+hard-coding the information in the code (which still would require the
 possibility of extensions to not prevent the use of new languages).
 
 @cindex specifying plural form in a PO file
@@ -6002,9 +6002,9 @@
 their program free, or want other kinds of freedom.  The simplest
 answer is ``normally not''.
 
-The @code{gettext-runtime} part of GNU @code{gettext}, i.e. the
+The @code{gettext-runtime} part of GNU @code{gettext}, i.e., the
 contents of @code{libintl}, is covered by the GNU Library General Public
-License.  The @code{gettext-tools} part of GNU @code{gettext}, i.e. the
+License.  The @code{gettext-tools} part of GNU @code{gettext}, i.e., the
 rest of the GNU @code{gettext} package, is covered by the GNU General
 Public License.
 
@@ -7175,7 +7175,7 @@
 @item
 When the package does not include the @code{intl/} subdirectory, and the
 libintl.h header (with its associated libintl library, if any) is not
-already installed on the system, it is preferrable that the package builds
+already installed on the system, it is preferable that the package builds
 without internationalization support, rather than to give a compilation
 error.
 @end itemize
@@ -7786,7 +7786,7 @@
 
 Note that the programmer should @emph{not} put this flag into the
 untranslated string.  (Putting the @samp{I} format directive flag into an
address@hidden string would lead to undefined behaviour on platforms without
address@hidden string would lead to undefined behavior on platforms without
 glibc when NLS is disabled.)
 
 @node objc-format, sh-format, c-format, Translators for other Languages
@@ -7912,9 +7912,9 @@
 @subsection Perl Format Strings
 
 There are two kinds format strings in Perl: those acceptable to the
-Perl built-in function @code{printf}, labelled as @samp{perl-format},
+Perl built-in function @code{printf}, labeled as @samp{perl-format},
 and those acceptable to the @code{libintl-perl} function @code{__x},
-labelled as @samp{perl-brace-format}.
+labeled as @samp{perl-brace-format}.
 
 Perl @code{printf} format strings are described in the @code{sprintf}
 section of @samp{man perlfunc}.
@@ -8406,7 +8406,7 @@
 locale's encoding, produce the dangerous @code{\x60} bytes.
 
 @item
-A translator could - voluntarily or inadvertantly - use backquotes
+A translator could - voluntarily or inadvertently - use backquotes
 @code{"`...`"} or dollar-parentheses @code{"$(...)"} in her translations.
 The enclosed strings would be executed as command lists by the shell.
 @end enumerate
@@ -9131,7 +9131,7 @@
 @noindent
 
 The @code{GetString} function returns a string's translation.  Note that this
-function returns null when a translation is missing (i.e. not even found in
+function returns null when a translation is missing (i.e., not even found in
 the fallback resource file).
 
 @item
@@ -9795,7 +9795,7 @@
 @end example
 
 The exact rule is: You can omit the surrounding quotes, when the hash
-key is a valid C (!) identifier, i. e. when it starts with an
+key is a valid C (!) identifier, i.e., when it starts with an
 underscore or an ASCII letter and is followed by an arbitrary number
 of underscores, ASCII letters or digits.  Other Unicode characters
 are @emph{not} allowed, regardless of the @code{use utf8} pragma.
@@ -10064,7 +10064,7 @@
 
 In Perl, parentheses around function arguments are mostly optional.
 @code{xgettext} will always assume that all
-recognized keywords (except for hashs and hash references) are names
+recognized keywords (except for hashes and hash references) are names
 of properly prototyped functions, and will (hopefully) only require
 parentheses where Perl itself requires them.  All constructs in the
 following example are therefore ok to use:
@@ -10158,7 +10158,7 @@
 @end group
 @end example
 
-Please do not forget, that the line breaks are real, i. e. they
+Please do not forget, that the line breaks are real, i.e., they
 translate into newline characters that will consequently show up in
 the resulting POT file.
 
@@ -10166,7 +10166,7 @@
 @subsubsection Bugs, Pitfalls, And Things That Do Not Work
 @cindex Perl pitfalls
 
-The foregoing sections should have proven that
+The foregoing sections should have proved that
 @code{xgettext} is quite smart in extracting translatable strings from
 Perl sources.  Yet, some more or less exotic constructs that could be
 expected to work, actually do not work.  
@@ -10580,7 +10580,7 @@
 time, Roland wanted to get GNU @code{libc} internationalized, and
 got Ulrich Drepper involved in that project.  Instead of starting
 from @code{glocale}, Ulrich rewrote something from scratch, but
-more conformant to the set of guidelines who emerged out of the
+more conforming to the set of guidelines who emerged out of the
 @code{glocale} effort.  Then, Ulrich got people from the previous
 forum to involve themselves into this new project, and the switch
 from @code{glocale} to what was first named @code{msgutils}, renamed
@@ -10641,7 +10641,7 @@
 
 Michael Gschwind (@file{mike@@vlsivie.tuwien.ac.at}) maintains a
 Frequently Asked Questions (FAQ) list, entitled @cite{Programming for
-Internationalisation}.  This FAQ discusses writing programs which
+Internationalization}.  This FAQ discusses writing programs which
 can handle different language conventions, character sets, etc.;
 and is applicable to all character set encodings, with particular
 emphasis on @w{ISO 8859-1}.  It is regularly published in Usenet
Index: gettext-tools/doc/msgattrib.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgattrib.texi,v
retrieving revision 1.4
diff -u -r1.4 msgattrib.texi
--- gettext-tools/doc/msgattrib.texi    3 Apr 2006 11:23:56 -0000       1.4
+++ gettext-tools/doc/msgattrib.texi    6 Aug 2006 19:39:36 -0000
@@ -72,7 +72,7 @@
 @ifnothtml
 `fuzzy'
 @end ifnothtml
-marked messages, remove all other messsages.
+marked messages, remove all other messages.
 
 @item --no-obsolete
 @opindex address@hidden, @code{msgattrib} option}
@@ -86,7 +86,7 @@
 
 @subsection Attribute manipulation
 
address@hidden modify message attrributes
address@hidden modify message attributes
 Attributes are modified after the message selection/removal has been
 performed.  If the @samp{--only-file} or @samp{--ignore-file} option is
 specified, the attribute modification is applied only to those messages
Index: gettext-tools/doc/msgcat.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgcat.texi,v
retrieving revision 1.3
diff -u -r1.3 msgcat.texi
--- gettext-tools/doc/msgcat.texi       22 Oct 2003 10:49:14 -0000      1.3
+++ gettext-tools/doc/msgcat.texi       6 Aug 2006 19:39:36 -0000
@@ -10,7 +10,7 @@
 It finds messages which are common to two or more of the specified PO files.
 By using the @code{--more-than} option, greater commonality may be requested
 before messages are printed.  Conversely, the @code{--less-than} option may be
-used to specify less commonality before messages are printed (i.e.
+used to specify less commonality before messages are printed (i.e.,
 @samp{--less-than=2} will only print the unique messages).  Translations,
 comments and extract comments will be cumulated, except that if
 @code{--use-first} is specified, they will be taken from the first PO file
Index: gettext-tools/doc/msgcomm.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgcomm.texi,v
retrieving revision 1.3
diff -u -r1.3 msgcomm.texi
--- gettext-tools/doc/msgcomm.texi      22 Oct 2003 10:49:15 -0000      1.3
+++ gettext-tools/doc/msgcomm.texi      6 Aug 2006 19:39:36 -0000
@@ -9,7 +9,7 @@
 of the specified PO files.
 By using the @code{--more-than} option, greater commonality may be requested
 before messages are printed.  Conversely, the @code{--less-than} option may be
-used to specify less commonality before messages are printed (i.e.
+used to specify less commonality before messages are printed (i.e.,
 @samp{--less-than=2} will only print the unique messages).  Translations,
 comments and extract comments will be preserved, but only from the first
 PO file to define them.  File positions from all PO files will be
Index: gettext-tools/doc/msgfilter.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgfilter.texi,v
retrieving revision 1.5
diff -u -r1.5 msgfilter.texi
--- gettext-tools/doc/msgfilter.texi    29 Mar 2006 11:31:35 -0000      1.5
+++ gettext-tools/doc/msgfilter.texi    6 Aug 2006 19:39:36 -0000
@@ -143,7 +143,7 @@
 
 @item --keep-header
 @opindex address@hidden, @code{msgfilter} option}
-Keep the header entry, i.e. the message with @samp{msgid ""}, unmodified,
+Keep the header entry, i.e., the message with @samp{msgid ""}, unmodified,
 instead of filtering it.  By default, the header entry is subject to
 filtering like any other message.
 
Index: gettext-tools/doc/msgfmt.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/msgfmt.texi,v
retrieving revision 1.7
diff -u -r1.7 msgfmt.texi
--- gettext-tools/doc/msgfmt.texi       22 Feb 2004 11:50:35 -0000      1.7
+++ gettext-tools/doc/msgfmt.texi       6 Aug 2006 19:39:36 -0000
@@ -80,7 +80,7 @@
 suffix @file{.mo} is added to the file name if it is not already
 present.
 
-We find this behaviour of Sun's implementation rather silly and so by
+We find this behavior of Sun's implementation rather silly and so by
 default this mode is @emph{not} selected.
 
 @end table
Index: gettext-tools/doc/xgettext.texi
===================================================================
RCS file: /cvsroot/gettext/gettext/gettext-tools/doc/xgettext.texi,v
retrieving revision 1.20
diff -u -r1.20 xgettext.texi
--- gettext-tools/doc/xgettext.texi     3 Apr 2006 11:20:33 -0000       1.20
+++ gettext-tools/doc/xgettext.texi     6 Aug 2006 19:39:37 -0000
@@ -147,7 +147,7 @@
 
 @cindex adding keywords, @code{xgettext}
 @cindex context, argument specification in @code{xgettext}
-If @var{keywordspec} is a C identifer @var{id}, @code{xgettext} looks
+If @var{keywordspec} is a C identifier @var{id}, @code{xgettext} looks
 for strings in the first argument of each call to the function or macro
 @var{id}.  If @var{keywordspec} is of the form
 @address@hidden:@var{argnum}}, @code{xgettext} looks for strings in the
@@ -264,7 +264,7 @@
 @samp{__attribute__ ((__format__ (__printf__, @var{arg}, ...)))} attached
 to @var{function} in a C source file.)
 For example, if you use the @samp{error} function from GNU libc, you can
-specify its behaviour through @code{--flag=error:3:c-format}.  The effect of
+specify its behavior through @code{--flag=error:3:c-format}.  The effect of
 this specification is that @code{xgettext} will mark as format strings all
 @code{gettext} invocations that occur as @var{arg}th argument of
 @var{function}.
@@ -449,7 +449,7 @@
 understood.
 @item Strings which make invalid assumptions about notation of date, time or
 money.
address@hidden Pluralisation problems.
address@hidden Pluralization problems.
 @item Incorrect English spelling.
 @item Incorrect formatting.
 @end itemize