--- nls-doc.diff.orig	2009-03-15 12:53:06.000000000 +0100
+++ nls-doc.diff	2009-03-15 16:06:38.000000000 +0100
@@ -22,17 +22,17 @@
 +	</authorgroup>
 +      </sect1info>
 +
-+      <title>Localized messages with POSIX.1 Native Language Support (NLS)</title>
++      <title>Localized Messages with POSIX.1 Native Language Support (NLS)</title>
 +
 +      <para>Beyond the basic I18N functions, like supporting various input
 +	encodings or supporting national conventions, such as the different
-+	decimal	separators, at a higher level of I18N, we can localize the
-+	messages written to the output by our program.  A common way of doing
-+	this is using the POSIX.1 NLS functions, which are provided as a part
++	decimal	separators, at a higher level of I18N, it is possible to localize the
++	messages written to the output by the various programs.  A common way of doing
++	this is using the POSIX.1 NLS functions which are provided as a part
 +	of the &os; base system.</para>
 +
 +      <sect2 id="nls-catalogs">
-+	<title>Organizing localized messages into catalog files</title>
++	<title>Organizing Localized Messages into Catalog Files</title>
 +
 +	<para>POSIX.1 NLS is based on catalog files, which contain the
 +	  localized messages in the desired encoding.  The messages are
@@ -43,38 +43,38 @@
 +	  Hungarian messages for ISO8859-2 encoding should be stored in a file
 +	  called <filename>hu_HU.ISO8859-2</filename>.</para>
 +
-+	<para>These catalog files are usual text files that contain the
-+	  numbered mesages.  It is possible to write comments by starting
-+	  the line with a $ sign.  Set boundaries are also separated by
++	<para>These catalog files are common text files that contain the
++	  numbered messages.  It is possible to write comments by starting
++	  the line with a <literal>$</literal> sign.  Set boundaries are also separated by
 +	  special comments, where the keyword <literal>set</literal> must
-+	  directly follow the $ sign.  The <literal>set</literal> keyword
++	  directly follow the <literal>$</literal> sign.  The <literal>set</literal> keyword
 +	  is then followed by the set number.  For example:</para>
 +
 +	<programlisting>$set 1</programlisting>
 +
 +	<para>The actual message entries start with the message number and
-+	  are then followed by the localized message.  The well-known
-+	  &man.printf.3; modifiers are accepted:</para>
++	  followed by the localized message.  The well-known
++	  modifiers from &man.printf.3; are accepted:</para>
 +
 +	<programlisting>15 "File not found: %s\n"</programlisting>
 +
 +	<para>The language catalog files have to be compiled into a binary
 +	  form before they can be opened from the program.  This conversion
 +	  is done with the &man.gencat.1; utility.  Its first argument is the
-+	  filename of the compiled catalog and the further arguments are the
-+	  input catalogs.  You can also organize the localized messages into
-+	  more catalog files and then process all of them with
++	  filename of the compiled catalog and its further arguments are the
++	  input catalogs.  The localized messages can also be organized into
++	  more catalog files and then all of them can be processed with
 +	  &man.gencat.1;.</para>
 +      </sect2>
 +
 +      <sect2 id="nls-using">
-+	<title>Using the catalog files from the source code</title>
++	<title>Using the Catalog Files from the Source Code</title>
 +
-+	<para>The usage of the catalog files is very simple.  To use
++	<para>Using the catalog files is simple.  To use
 +	  the related functions, <filename
 +	    class="headerfile">nl_types.h</filename> must be included.  Before
-+	  using a catalog, you have to open it with &man.catopen.3;.
-+	  It has two arguments, the first one is the name of the
++	  using a catalog, it has to be opened with &man.catopen.3;.
++	  The function takes two arguments.  The first parameter is the name of the
 +	  installed and compiled catalog.  Usually, the name of the
 +	  program is used, such as <application>grep</application>.
 +	  This name will be used when looking for the compiled
@@ -91,7 +91,7 @@
 +	<itemizedlist>
 +	  <listitem>
 +	    <para><literal>NL_CAT_LOCALE</literal>, which means that
-+	      the used catalog file will be based on the
++	      the used catalog file will be based on
 +	      <envar>LC_MESSAGES</envar>.</para>
 +	  </listitem>
 +	  <listitem>
@@ -100,29 +100,29 @@
 +	      the proper catalog.</para>
 +	</itemizedlist>
 +
-+	<para>The &man.catopen.3; call return with a catalog identifier of
-+	  type <literal>nl_catd</literal>.  For possible returned error
-+	  codes, please refer to the manual page.</para>
++	<para>The &man.catopen.3; call returns a catalog identifier of
++	  type <literal>nl_catd</literal>.  Please refer to the manual page for a list of possible returned error
++	  codes.</para>
 +
 +	<para>After opening a catalog &man.catgets.3; can be used to retrieve
 +	  a message.  The first parameter is the catalog identifier returned
 +	  by &man.catopen.3;, the second one is the number of the set, the
-+	  third one is the number of the message and the fourth one is a
-+	  fallback message, which will be returned if the requested message
++	  third one is the number of the messages, and the fourth one is a
++	  fallback message which will be returned if the requested message
 +	  cannot be retrieved from the catalog file.</para>
 +
 +	<para>After using the catalog file, it must be closed by calling
-+	  &man.catclose.3;, which has one argument, the catalog id.</para>
++	  &man.catclose.3; which has one argument, the catalog id.</para>
 +      </sect2>
 +
 +      <sect2 id="nls-example">
-+	<title>A practical example</title>
++	<title>A Practical Example</title>
 +
-+	<para>The following example will demonstrate an easy solution to
++	<para>The following example will demonstrate an easy solution on how to
 +	  use NLS catalogs in a flexible way.</para>
 +
-+	<para>We need to put these lines to a common header file of
-+	  the program, which is included into all source files, where
++	<para>The below lines need to be put into a common header file of
++	  the program which is included into all source files where
 +	  localized messages are necessary:</para>
 +
 +	<programlisting>
@@ -137,7 +137,7 @@
 +
 +extern char		*nlsstr[];</programlisting>
 +
-+	<para>Then put these lines to the global declaration part of the
++	<para>Next, put these lines into the global declaration part of the
 +	  main source file:</para>
 +
 +	<programlisting>
@@ -147,16 +147,16 @@
 +#endif
 +
 +/*
-+ * Default messags to use when NLS is disabled or no catalogue
++ * Default messages to use when NLS is disabled or no catalog
 + * is found.
 + */
 +char    *nlsstr[] = {
 +        "",
 +/* 1*/  "some random message",
-+/* 2*/  "some another message"
++/* 2*/  "some other message"
 +};</programlisting>
 +
-+	<para>And here comes the real code snippets, which open, read and
++	<para>Next come the real code snippets, which open, read, and
 +	  close the catalog:</para>
 +
 +	<programlisting>
@@ -176,25 +176,25 @@
 +      </sect2>
 +
 +      <sect2 id="nls-mk">
-+	<title>Making use of bsd.nls.mk</title>
++	<title>Making use of <filename>bsd.nls.mk</filename></title>
 +
-+	<para>Using the catalog files requires few repeatable steps,
++	<para>Using the catalog files requires a few repeatable steps,
 +	  such as compiling the catalogs and installing them to the
 +	  proper location.  In order to simplify this process even
 +	  more, <filename>bsd.nls.mk</filename> introduces some macros.
-+	  It is not needed to include <filename>bsd.nls.mk</filename>
++	  It is not necessary to include <filename>bsd.nls.mk</filename>
 +	  explicitly, it is pulled in from the common Makefiles,
 +	  such as <filename>bsd.prog.mk</filename> or
 +	  <filename>bsd.lib.mk</filename>.</para>
 +
 +	<para>Usually it is enough to define <makevar>NLSNAME</makevar>,
-+	  which should be the catalog name mentioned as the first
++	  which should have the catalog name mentioned as the first
 +	  argument of &man.catopen.3; and list the catalog files in
 +	  <makevar>NLS</makevar> without their <literal>.msg</literal>
 +	  extension.</para>
 +
 +	<para>For further information about <filename>bsd.nls.mk</filename>,
-+	  please refer to this file itself, it is short and easy to
++	  please refer to the file itself, it is short and easy to
 +	  understand.</para>
 +      </sect2>
 +    </sect1>
