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.36.2.1 -r1.36.2.2
--- openacs-4/packages/acs-core-docs/www/permissions-requirements.html	2 Mar 2019 19:30:05 -0000	1.36.2.1
+++ openacs-4/packages/acs-core-docs/www/permissions-requirements.html	1 Aug 2024 08:03:41 -0000	1.36.2.2
@@ -24,7 +24,7 @@
 row based on the information in that row.</p><p>Problems resulting from this piecemeal approach to permissions and access
 control were many, the two major ones being inconsistency, and
 repeated/redundant code. Thus the drive in OpenACS 4 to provide a unified,
-consistent permissions system that both programmers and administrators can
+consistent permission system that both programmers and administrators can
 readily use.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="permissions-requirements-system-overview"></a>System Overview</h3></div></div></div><p>The OpenACS 4 Permissions system has two main pieces: first, an API for
 developers to readily handle access control in their applications. The second
 piece of the system is a UI meant primarily for (subsite) administrators to