Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp,v
diff -u -r1.1.2.13 -r1.1.2.14
--- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp	6 Jan 2017 09:18:41 -0000	1.1.2.13
+++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp	21 Apr 2017 15:07:52 -0000	1.1.2.14
@@ -224,7 +224,7 @@
 </tr><tr class="seglistitem">
 <td class="seg">EXT-AUTH-08</td><td class="seg">A</td><td class="seg">Automation of batch Synchronization</td>
 </tr><tr class="seglistitem">
-<td class="seg">EXT-AUTH-15</td><td class="seg">B</td><td class="seg">On-demand syncronization</td>
+<td class="seg">EXT-AUTH-15</td><td class="seg">B</td><td class="seg">On-demand synchronization</td>
 </tr>
 </tbody>
 </table></div><p>Regardless of the login method, the user needs to have a row in
@@ -374,7 +374,7 @@
 site configured to expire people&#39;s login after e.g. 2, 4, or 8
 hours.</p><p>The other advantage is that we can still offer certain
 functionality to you, even when your login is not trusted. For
-example, we could let you browse publically available forums, and
+example, we could let you browse publicly available forums, and
 only when you want to post do you need to log in. This makes it
 even more feasible to have a more secure login expiration
 setting.</p><p>By default, <code class="literal">auth::require_login</code>