Index: openacs-4/packages/acs-core-docs/www/permissions-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions-requirements.html,v
diff -u -r1.34.2.1 -r1.34.2.2
--- openacs-4/packages/acs-core-docs/www/permissions-requirements.html	9 Jun 2016 08:44:50 -0000	1.34.2.1
+++ openacs-4/packages/acs-core-docs/www/permissions-requirements.html	23 Jun 2016 08:32:45 -0000	1.34.2.2
@@ -13,7 +13,7 @@
 applications to handle permissions. Consolidating access control in such a
 manner reduces both cost and risk: cost, in that less code has to be written
 and maintained for dealing with recurring permissions situations; risk, in
-that we need not rely on any single programmer's diligence to ensure
+that we need not rely on any single programmer's diligence to ensure
 access control is implemented and enforced correctly.</p><p><span class="strong"><strong>Historical Motivations</strong></span></p><p>In earlier versions of the OpenACS, permissions and access control was handled
 on a module-by-module basis, often even on a page-by-page basis. For example,
 a typical module might allow any registered user to access its pages