Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html,v
diff -u -r1.40.2.11 -r1.40.2.12
--- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html	23 Jun 2016 08:32:45 -0000	1.40.2.11
+++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html	3 Oct 2016 09:17:51 -0000	1.40.2.12
@@ -310,7 +310,7 @@
 nice real-time collaboration feature frequently requested by
 members of the community. This is particularly interesting when
 integrated with a chat or instant messaging service like
-Jabber.</p><p>What I'm concretely suggesting is that we keep a record of
+Jabber.</p><p>What I&#39;m concretely suggesting is that we keep a record of
 which authenticated users have requested pags on the site in the
 last x minutes (typically about 5), and thus are considered to be
 currently online. There&#39;s nothing more to it. This lets us display
@@ -340,7 +340,7 @@
 Authenticating against multiple servers simultaneously</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%"><tr><th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th></tr><thead><tr><th>EXT-AUTH-36</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">EXT-AUTH-36</td><td class="seg">A</td><td class="seg">Authenticate against multiple servers</td></tr></tbody></table></div><p>Both OKI and OpenACS supports a form of stacking, where you
 can be logged into multiple authorities at the same time. This is
 useful if, for example, you need to get login tokens such as
-Kerberos tickets for access to shared resources.</p><p>I can see the value in this, but for simplicity&#39;s sake, I'm
+Kerberos tickets for access to shared resources.</p><p>I can see the value in this, but for simplicity&#39;s sake, I&#39;m
 in favor of keeping this use-case out of the loop until we have
 someone with a real requirement who could help us guide
 development.</p><p>For now, OpenACS is still more of an integrated suite, it
@@ -358,7 +358,7 @@
           PAM level, so we don&#39;t have to write them all ourselves. The
           downside is that we can&#39;t do things like account creation, password
           management, real-time account synchronization, etc., not supported
-          by PAM (I'm not entirely sure what is and is not
+          by PAM (I&#39;m not entirely sure what is and is not
           supported).</p></li><li class="listitem"><p>RADIUS</p></li><li class="listitem"><p>LDAP</p></li></ul></div><div class="sect4"><div class="titlepage"><div><div><h5 class="title"><a name="RADIU"></a>RADIUS</h5></div></div></div><p>RADIUS is a simple username/password-type authentication
 server.</p><p>It also supports sending a challenge to which the user must
 respond with the proper answer (e.g. mother&#39;s maiden name, or could