Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp,v
diff -u -r1.1.2.2 -r1.1.2.3
--- openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp	13 Jul 2023 12:44:56 -0000	1.1.2.2
+++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp	30 Jul 2024 18:05:34 -0000	1.1.2.3
@@ -47,7 +47,7 @@
 user/password)</li><li>Password Management (where to update passwords)</li><li>Account Registration (where to create new accounts)</li><li>On-Demand Sync (to get user info from the source in real
 time)</li>
 </ul>
-<p>Those configurations simply will perform the tcl proc that is
+<p>Those configurations simply will perform the Tcl proc that is
 defined in the SC above described for the given SC implementation
 that you choose. In other words:</p>
 <ul>
@@ -79,7 +79,7 @@
 under Security section. If username is used for logging, it will
 ask for the authority to use, since username is unique by authority
 but not for the entire openacs installation (can exists several
-identic usernames but each one belongs to a different
+identical usernames but each one belongs to a different
 authority).</p>
 <p class="style2"> </p>
 <p class="style2"><strong>acs-authentication defines a set of SC to
@@ -116,7 +116,7 @@
 <ol>
 <li>The user enters the email/user &amp; password</li><li>It will search the user in the users table and return the
 authority_id</li><li>With that authority_id it will find the respective SC
-implementation <em>which contains the adequate tcl proc for the
+implementation <em>which contains the adequate Tcl proc for the
 authentication process</em>
 </li><li>That proc will check the identity of the user based on the
 password (right now could be locally, pam or ldap authenticated,