Index: openacs-4/packages/acs-lang/www/doc/i18n-requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-requirements.adp,v
diff -u -N -r1.3 -r1.4
--- openacs-4/packages/acs-lang/www/doc/i18n-requirements.adp	29 Oct 2017 11:33:10 -0000	1.3
+++ openacs-4/packages/acs-lang/www/doc/i18n-requirements.adp	29 Dec 2017 10:51:45 -0000	1.4
@@ -198,7 +198,7 @@
 grouped with respect to a module name or package path.</p><p>
 <strong>40.30</strong> The API for lookup of a message will take
 a locale and message key as arguments, and return the appropriate
-translation of that message for the specifed locale.</p><p>
+translation of that message for the specified locale.</p><p>
 <strong>40.40</strong> The API for lookup of a message will
 accept an optional default string which can be used if the message
 key is not found in the catalog. This lets the developer get code
@@ -318,7 +318,7 @@
 created (one per locale or language)
 <p>
 <strong>70.10</strong> For a given page request, the system must
-be able to select an approprate locale-specific template file to
+be able to select an appropriate locale-specific template file to
 use. The request locale is computed as per (see requirement
 20.0).</p><p><font color="#080EFF"><em>Design note: this would probably be
 implemented by suffixing the locale or a locale abbreviation to the
Index: openacs-4/packages/acs-lang/www/doc/i18n-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-requirements.html,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/acs-lang/www/doc/i18n-requirements.html	29 Oct 2017 11:33:10 -0000	1.4
+++ openacs-4/packages/acs-lang/www/doc/i18n-requirements.html	29 Dec 2017 10:51:45 -0000	1.5
@@ -228,7 +228,7 @@
 respect to a module name or package path.</p>
 <p><strong>40.30</strong> The API for lookup of a message will take a locale
 and message key as arguments, and return the appropriate
-translation of that message for the specifed locale.</p>
+translation of that message for the specified locale.</p>
 <p><strong>40.40</strong> The API for lookup of a message will accept an
 optional default string which can be used if the message key is not
 found in the catalog. This lets the developer get code working and
@@ -345,7 +345,7 @@
 create multiple locale-specific template files may be created (one
 per locale or language) 
 <p><strong>70.10</strong> For a given page request, the system must be able
-to select an approprate locale-specific template file to use. The
+to select an appropriate locale-specific template file to use. The
 request locale is computed as per (see requirement 20.0).</p>
 <p><font color="#080EFF"><em>Design note: this would probably be
 implemented by suffixing the locale or a locale abbreviation to the