Index: openacs-4/packages/acs-lang/tcl/lang-catalog-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/tcl/lang-catalog-procs.tcl,v
diff -u -r1.60.2.2 -r1.60.2.3
--- openacs-4/packages/acs-lang/tcl/lang-catalog-procs.tcl	12 Apr 2019 21:19:13 -0000	1.60.2.2
+++ openacs-4/packages/acs-lang/tcl/lang-catalog-procs.tcl	10 Aug 2019 15:10:51 -0000	1.60.2.3
@@ -657,7 +657,7 @@
     There are three sets of keys, file, db, and base keys. For each key in
     the union of these keys there are three messages that can exist: the file message, the db message, and the base message. The
     base message serves as the base for the merge. We will distinguish all the different permutations
-    of each of the three messages existing or not, and all permutations of the messages being different from eachother.
+    of each of the three messages existing or not, and all permutations of the messages being different from each other.
     We don't distinguish how two messages are different, only whether they are different or not.
     In total that gives us 14 cases (permutations) to consider.
     </p>
Index: openacs-4/packages/acs-lang/tcl/lang-message-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/tcl/lang-message-procs.tcl,v
diff -u -r1.68.2.4 -r1.68.2.5
--- openacs-4/packages/acs-lang/tcl/lang-message-procs.tcl	5 Apr 2019 12:50:54 -0000	1.68.2.4
+++ openacs-4/packages/acs-lang/tcl/lang-message-procs.tcl	10 Aug 2019 15:10:51 -0000	1.68.2.5
@@ -761,7 +761,7 @@
                               identifier for each locale. All keys belong to a certain
                               package and should be prefixed with the package key of that package
                               on the format package_key.message_key (the dot is reserved for separating
-                              the package key, the rest of the key should contain only alpha-numeric
+                              the package key, the rest of the key should contain only alphanumeric
                               characters and underscores). If the key does not belong to
                               any particular package it should not contain a dot. A lookup
                               is always attempted with the exact key given to this proc.
Index: openacs-4/packages/acs-lang/tcl/localization-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/tcl/localization-procs.tcl,v
diff -u -r1.29.2.4 -r1.29.2.5
--- openacs-4/packages/acs-lang/tcl/localization-procs.tcl	1 Jul 2019 16:43:43 -0000	1.29.2.4
+++ openacs-4/packages/acs-lang/tcl/localization-procs.tcl	10 Aug 2019 15:10:51 -0000	1.29.2.5
@@ -21,7 +21,7 @@
 } {
     Converts a number to its canonical
     representation by stripping everything but the
-    decimal separator and triming left 0's so it
+    decimal separator and trimming left 0's so it
     won't be octal. It can process the following types of numbers:
     <ul>
     <li>Just digits (allows leading zeros).
@@ -350,7 +350,7 @@
     fmt
     locale
 } {
-    Compiles ISO 14652 LC_TIME style formatting string to variable substitions and proc calls.
+    Compiles ISO 14652 LC_TIME style formatting string to variable substitutions and proc calls.
 
     @param fmt             An ISO 14652 LC_TIME style formatting string.
     @param locale          Locale identifier must be in the locale database
Index: openacs-4/packages/acs-lang/www/doc/i18n-design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-design.adp,v
diff -u -r1.7.2.1 -r1.7.2.2
--- openacs-4/packages/acs-lang/www/doc/i18n-design.adp	11 Mar 2019 08:43:27 -0000	1.7.2.1
+++ openacs-4/packages/acs-lang/www/doc/i18n-design.adp	10 Aug 2019 15:10:51 -0000	1.7.2.2
@@ -101,7 +101,7 @@
 The request processor should use the ad_locale API to figure out
 the preferred locale for a request (perhaps combining user
 preference with subsite defaults in some way). It will make this
-information accesible via the <kbd>ad_conn</kbd>
+information accessible via the <kbd>ad_conn</kbd>
  function:
 <pre><strong>ad_conn locale</strong></pre>
 <h4>Character Sets and Encodings</h4>
@@ -307,7 +307,7 @@
 English.
 <p>This default can be overridden by setting the AOLserver init
 parameter for the MIME type of <kbd>.tcl</kbd> files to include an
-explcit character set. If an explicit MIME type is not found,
+explicit character set. If an explicit MIME type is not found,
 <kbd>ns_encodingfortype</kbd> will default to the AOLserver init
 parameter value <kbd>DefaultCharset</kbd> if it is set.</p>
 <p>Example AOLserver .ini configuration file to set default script
@@ -432,7 +432,7 @@
 </pre>
 
 In the example above, if the catalog file was loaded from the
-bboard package, all of the keys would be prefixed autmatically with
+bboard package, all of the keys would be prefixed automatically with
 "<code>bboard.</code>
 ".
 <h4>Loading A Message Catalog At Package Init Time</h4>
@@ -507,7 +507,7 @@
 translated once at template compile time, rather than dynamically
 every time the page is run. This will be unneccessaru and will be
 deprecated once we have implemented <em>effective locale</em> based
-cacheing for templates.</li>
+caching for templates.</li>
 </ul>
 Example 1: Display the text string <em>Hello</em> on an ADP page
 (i.e. do nothing special):
Index: openacs-4/packages/acs-lang/www/doc/i18n-design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-lang/www/doc/i18n-design.html,v
diff -u -r1.8 -r1.8.2.1
--- openacs-4/packages/acs-lang/www/doc/i18n-design.html	18 Apr 2018 08:07:33 -0000	1.8
+++ openacs-4/packages/acs-lang/www/doc/i18n-design.html	10 Aug 2019 15:10:51 -0000	1.8.2.1
@@ -139,7 +139,7 @@
 
 The request processor should use the ad_locale API to figure out the
 preferred locale for a request (perhaps combining user preference with
-subsite defaults in some way). It will make this information accesible
+subsite defaults in some way). It will make this information accessible
 via the <kbd>ad_conn</kbd> function:
 
 <pre>
@@ -228,7 +228,7 @@
 
 <h4>Caching multilingual ADP Templates</h4> Message catalog lookups
 can be potentially expensive, if many of them are done in a page. The
-templating system can already precompile and and cache adp pages.
+templating system can already precompile and cache adp pages.
 This works fine for a page in a specific language such as
 <kbd>foo.en.adp</kbd>, but we need to modify the caching mechanism if we
 want to use a single template file to target multiple languages.
@@ -431,7 +431,7 @@
 <p>
 This default can be
 overridden by setting the AOLserver init parameter for the MIME type
-of <kbd>.tcl</kbd> files to include an explcit character set. If an explicit
+of <kbd>.tcl</kbd> files to include an explicit character set. If an explicit
 MIME type is not found, <kbd>ns_encodingfortype</kbd> will default to the
 AOLserver init parameter value <kbd>DefaultCharset</kbd> if it is set.
 <p>
@@ -575,7 +575,7 @@
 
 
 In the example above, if the catalog file was loaded from the bboard
-package, all of the keys would be prefixed autmatically with "<code>bboard.</code>".
+package, all of the keys would be prefixed automatically with "<code>bboard.</code>".
 
 <h4>Loading A Message Catalog At Package Init Time</h4>
 
@@ -649,7 +649,7 @@
     <li><code>type</code> specifies the context in which the translation is made. If omitted,
     type is user which means that the translation is provided in the user's preferred language.
     <li><code>static</code> specifies that this tag should be translated once at template compile time, rather than dynamically every time the page is run. This will be unneccessaru and will be deprecated once we
-have implemented <em>effective locale</em> based cacheing for templates.
+have implemented <em>effective locale</em> based caching for templates.
  </ul>
     Example 1: Display the text string <em>Hello</em> on an ADP page (i.e. do nothing special):
     <pre>
Index: openacs-4/packages/acs-authentication/acs-authentication.info
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/acs-authentication.info,v
diff -u -r1.43.2.2 -r1.43.2.3
--- openacs-4/packages/acs-authentication/acs-authentication.info	10 Apr 2019 20:40:20 -0000	1.43.2.2
+++ openacs-4/packages/acs-authentication/acs-authentication.info	10 Aug 2019 15:15:49 -0000	1.43.2.3
@@ -30,7 +30,7 @@
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="AcknowledgementFileName"  default="{acs_root_dir}/batch-sync-ack-{authority}-{ansi_date}.xml" description="Full file path to where we should drop the acknowledgement file for batch syncs. You can use these special values: {acs_root_di
 r} will get replaced with the root directory for this OpenACS installation, e.g. '/var/lib/aolserver/service0' (no trailing slash). {ansi_date} will get replaced with today's date in ANSI format, e.g. '2003-10-29'. {authority} will get replaced with the short_name of the authority, e.g. 'rz_pam'." section_name="Batch Synchronization"/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="KeepBatchLogDays"  default="0" description="The number of days to keep the log for a batch user synchronization job around. Say 0 if you want to keep the log forever." section_name="Batch Synchronization"/>
-            <parameter scope="instance" datatype="number"  min_n_values="1"  max_n_values="1"  name="MaxConsecutiveFailedLoginAttempts"  default="0" description="Enables the tracking of consecutive failed login attempts per subsite and to slowdown brute force attacks. After reaching this threshold every further login attempt from is automatically rejected for a period of MaxConsecutiveFailedLoginAttemptsLockoutTime seconds . 0 for infinte attempts. " section_name="security"/>
+            <parameter scope="instance" datatype="number"  min_n_values="1"  max_n_values="1"  name="MaxConsecutiveFailedLoginAttempts"  default="0" description="Enables the tracking of consecutive failed login attempts per subsite and to slowdown brute force attacks. After reaching this threshold every further login attempt from is automatically rejected for a period of MaxConsecutiveFailedLoginAttemptsLockoutTime seconds . 0 for infinite attempts. " section_name="security"/>
             <parameter scope="instance" datatype="number"  min_n_values="1"  max_n_values="1"  name="MaxConsecutiveFailedLoginAttemptsLockoutTime"  default="21600" description="Timespan in seconds for which every login attempt is rejected after the limit set by MaxConsecutiveFailedLoginAttempts has been reached. This parameter is only in effect if MaxConsecutiveFailedLoginAttempts is greater than zero. " section_name="security"/>
             <parameter datatype="string"  min_n_values="1"  max_n_values="1"  name="RegisterAuthority"  default="local" description="The short name of the authority in which users are registered. Is best set in the Authentication admin UI."/>
             <parameter datatype="number"  min_n_values="1"  max_n_values="1"  name="SyncAddUsersToDotLrnP"  default="0" description="Should we add users to .LRN? This requires .LRN to be installed, and has serious performance implications." section_name="Batch Synchronization"/>
Index: openacs-4/packages/acs-authentication/tcl/apm-callback-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/tcl/apm-callback-procs.tcl,v
diff -u -r1.21.2.1 -r1.21.2.2
--- openacs-4/packages/acs-authentication/tcl/apm-callback-procs.tcl	10 Apr 2019 21:41:00 -0000	1.21.2.1
+++ openacs-4/packages/acs-authentication/tcl/apm-callback-procs.tcl	10 Aug 2019 15:15:49 -0000	1.21.2.2
@@ -256,15 +256,15 @@
             CanChangePassword {
                 description {
                     Return whether the user can change his/her password through this implementation.
-                    The value is not supposed to depend on the username and should be cachable.
+                    The value is not supposed to depend on the username and should be cacheable.
                 }
                 input {
                     parameters:string,multiple
                 }
                 output {
                     changeable_p:boolean
                 }
-                iscachable_p "t"
+                iscacheable_p "t"
             }
             ChangePassword {
                 description {
@@ -285,15 +285,15 @@
             CanRetrievePassword {
                 description {
                     Return whether the user can retrieve his/her password through this implementation.
-                    The value is not supposed to depend on the username and should be cachable.
+                    The value is not supposed to depend on the username and should be cacheable.
                 }
                 input {
                     parameters:string,multiple
                 }
                 output {
                     retrievable_p:boolean
                 }
-                iscachable_p "t"
+                iscacheable_p "t"
             }
             RetrievePassword {
                 description {
@@ -314,15 +314,15 @@
             CanResetPassword {
                 description {
                     Return whether the user can reset his/her password through this implementation.
-                    The value is not supposed to depend on the username and should be cachable.
+                    The value is not supposed to depend on the username and should be cacheable.
                 }
                 input {
                     parameters:string,multiple
                 }
                 output {
                     resettable_p:boolean
                 }
-                iscachable_p "t"
+                iscacheable_p "t"
             }
             ResetPassword {
                 description {
Index: openacs-4/packages/acs-authentication/tcl/sync-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/tcl/sync-procs.tcl,v
diff -u -r1.44.2.1 -r1.44.2.2
--- openacs-4/packages/acs-authentication/tcl/sync-procs.tcl	13 Mar 2019 10:04:53 -0000	1.44.2.1
+++ openacs-4/packages/acs-authentication/tcl/sync-procs.tcl	10 Aug 2019 15:15:49 -0000	1.44.2.2
@@ -522,7 +522,7 @@
     # but these will issue an exception below.
     #
     # TODO: using a different error-code could make the code saver, by
-    # just ingnoring such cases.
+    # just ignoring such cases.
     #
     set elms [list]
     ad_try  {
Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.html,v
diff -u -r1.3 -r1.3.2.1
--- openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	5 Aug 2018 10:34:17 -0000	1.3
+++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	10 Aug 2019 15:15:49 -0000	1.3.2.1
@@ -37,7 +37,7 @@
 <p>Definition: SC = <a href="http://cvs.openacs.org/cvs/*checkout*/openacs-4/packages/acs-service-contract/www/doc/index.html?rev=1.2">service-contract</a></p>
 <p class="style2">&nbsp;</p>
 <p class="style2">Authorities</p>
-<p>acs-authentication can have multiple authorities, each one represent an specific configuration of authenticatication. For instance, in your openacs installation you can have users related to different authorities, some of them might authenticate locally since they are external or invited, others belongs to your corporate network and already have users, so might authenticate against LDAP and others in your own work office might use PAM for authentication because your local system authentication. Plus you might define an specific implementation (using the set of SC) to connect to your client DB, which is in another DB, and allow your clients login to certain parts of your website. Then, this is right way to handle all those set of users, that already might have an account in another place and you just want them to authenticate against that external system.<br>
+<p>acs-authentication can have multiple authorities, each one represent a specific configuration of authenticatication. For instance, in your openacs installation you can have users related to different authorities, some of them might authenticate locally since they are external or invited, others belongs to your corporate network and already have users, so might authenticate against LDAP and others in your own work office might use PAM for authentication because your local system authentication. Plus you might define a specific implementation (using the set of SC) to connect to your client DB, which is in another DB, and allow your clients login to certain parts of your website. Then, this is right way to handle all those set of users, that already might have an account in another place and you just want them to authenticate against that external system.<br>
 </p>
 <p>The idea is: <strong>each user belongs to a given authority, and just one </strong>.  </p>
 <p><strong>To add an authority</strong> in your installation go to /acs-admin/auth/ and click on &quot;Create new authority&quot;.</p>
Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp,v
diff -u -r1.4 -r1.4.2.1
--- openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp	8 Feb 2019 13:00:50 -0000	1.4
+++ openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp	10 Aug 2019 15:15:49 -0000	1.4.2.1
@@ -11,7 +11,7 @@
 		    <div class="sect1" lang="en">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="ext-auth-pam-install" id="ext-auth-pam-install"></a>Using
-Pluggable Authentication Modules (PAM) with OpenACS</h2></div></div></div><p>OpenACS supports PAM authetication via the ns_pam module in
+Pluggable Authentication Modules (PAM) with OpenACS</h2></div></div></div><p>OpenACS supports PAM authentication via the ns_pam module in
 AOLserver.</p><div class="orderedlist"><ol type="1">
 <li>
 <p>
Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html,v
diff -u -r1.6 -r1.6.2.1
--- openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html	7 Aug 2017 23:47:46 -0000	1.6
+++ openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html	10 Aug 2019 15:15:49 -0000	1.6.2.1
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Using Pluggable Authentication Modules (PAM) with OpenACS</title><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="home" href="index.html" title="External Authentication"><link rel="up" href="ext-auth-install.html" title="Installation"><link rel="previous" href="ext-auth-install.html" title="Installation"><link rel="next" href="ext-auth-ldap-install.html" title="Using LDAP/Active Directory with OpenACS"><link rel="stylesheet" href="openacs.css" type="text/css"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" border="0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="ext-auth-install.html">Prev</a> </td><th width="60%" align="center">Installation</th><td width="20%" align="right"> <a accesskey="n" href="ext-auth-ldap-install.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ext-auth-pam-install"></a>Using Pluggable Authentication Modules (PAM) with OpenACS</h2></div></div></div><p>OpenACS supports PAM authetication via the ns_pam module in AOLserver.</p><div class="orderedlist"><ol type="1"><li><p><strong>Add PAM support to AOLserver. </strong>OpenACS supports PAM support via the PAM AOLserver
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Using Pluggable Authentication Modules (PAM) with OpenACS</title><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><link rel="home" href="index.html" title="External Authentication"><link rel="up" href="ext-auth-install.html" title="Installation"><link rel="previous" href="ext-auth-install.html" title="Installation"><link rel="next" href="ext-auth-ldap-install.html" title="Using LDAP/Active Directory with OpenACS"><link rel="stylesheet" href="openacs.css" type="text/css"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" border="0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="ext-auth-install.html">Prev</a> </td><th width="60%" align="center">Installation</th><td width="20%" align="right"> <a accesskey="n" href="ext-auth-ldap-install.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ext-auth-pam-install"></a>Using Pluggable Authentication Modules (PAM) with OpenACS</h2></div></div></div><p>OpenACS supports PAM authentication via the ns_pam module in AOLserver.</p><div class="orderedlist"><ol type="1"><li><p><strong>Add PAM support to AOLserver. </strong>OpenACS supports PAM support via the PAM AOLserver
         module.  PAM is system of modular support, and can provide
         local (unix password), RADIUS, LDAP (<a href="http://www.tldp.org/HOWTO/archived/LDAP-Implementation-HOWTO/pamnss.html" target="_top">more
         information</a>), and other forms of
Index: openacs-4/packages/acs-authentication/www/doc/xml/install.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/xml/install.xml,v
diff -u -r1.6 -r1.6.2.1
--- openacs-4/packages/acs-authentication/www/doc/xml/install.xml	7 Aug 2017 23:47:46 -0000	1.6
+++ openacs-4/packages/acs-authentication/www/doc/xml/install.xml	10 Aug 2019 15:15:49 -0000	1.6.2.1
@@ -14,7 +14,7 @@
 
     <sect1 id="ext-auth-pam-install">
       <title>Using Pluggable Authentication Modules (PAM) with OpenACS</title>
-      <para>OpenACS supports PAM authetication via the ns_pam module in AOLserver.</para>
+      <para>OpenACS supports PAM authentication via the ns_pam module in AOLserver.</para>
       <orderedlist>
         <listitem>
           <formalpara>
@@ -190,7 +190,7 @@
     <para>You do not want to make users remember yet another password and username. If you can avoid it you do not want to store their passwords either. This document should help you set your system up so your users can seamlessly log in to your OpenACS instance using the password they are accustomed to using for other things at your institution.</para></formalpara>
     <formalpara>
     <title>Background</title>
-     <para>The original OpenACS LDAP implementation (which has been depreciated by this package) treated the LDAP server as another data store similar to Oracle or Postgresql. It opened a connection using a privileged account and read or stored an encrypted password for the user in question. This password was independent of the user's operating system or network account, and had to be synchronized if you wanted the same password for OpenACS.</para>
+     <para>The original OpenACS LDAP implementation (which has been deprecated by this package) treated the LDAP server as another data store similar to Oracle or Postgresql. It opened a connection using a privileged account and read or stored an encrypted password for the user in question. This password was independent of the user's operating system or network account, and had to be synchronized if you wanted the same password for OpenACS.</para>
      <para>Save their passwords? Sync passwords? Deal with forgotten password requests? No Thanks. Using ldap bind, you can delegate authentication completely to LDAP. This way you can let the IT department (if you are lucky) worry about password storage/synchronization/etc. The bind operation takes a username and password and returns a true of false depending on whether they match up. This document takes the 'bind' approach so that your users LDAP/AD password (or whatever else you use) can be used to login to OpenACS.</para></formalpara>
     <formalpara>
      <title>Note on Account Creation</title>