Index: openacs-4/packages/acs-core-docs/www/i18n-introduction.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-introduction.adp,v
diff -u -N -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/acs-core-docs/www/i18n-introduction.adp	26 Aug 2020 07:46:25 -0000	1.4.2.2
+++ openacs-4/packages/acs-core-docs/www/i18n-introduction.adp	5 Jan 2021 17:33:39 -0000	1.4.2.3
@@ -36,7 +36,7 @@
 and localized ADP files. For ADP pages which are mostly code,
 replacing the message text with message key placeholders is
 simpler. This approach also allows new translation in the database,
-without affecting the file system. For ADP pages which are static
+without affecting the filesystem. For ADP pages which are static
 and mostly text, it may be easier to create a new ADP page for each
 language. In this case, the pages are distinguished by a file
 naming convention.</p><div class="sect2">
@@ -118,7 +118,7 @@
 <li class="listitem"><p>Typical static key lookup: <code class="computeroutput">[_
 package_key.message_key]</code> - The message key and package key
 used here must be string literals, they can&#39;t result from
-variable evaluation.</p></li><li class="listitem"><p>Static key lookup with non-default locale: <code class="computeroutput">[lang::message::lookup $locale
+variable evaluation.</p></li><li class="listitem"><p>Static key lookup with nondefault locale: <code class="computeroutput">[lang::message::lookup $locale
 package_key.message_key]</code> - The message key and package key
 used here must be string literals, they can&#39;t result from
 variable evaluation.</p></li><li class="listitem"><p>Dynamic key lookup: <code class="computeroutput">[lang::util::localize