Index: openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml,v diff -u -r1.8.2.1 -r1.8.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml 5 Oct 2019 13:43:47 -0000 1.8.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml 5 Feb 2024 15:35:07 -0000 1.8.2.2 @@ -75,7 +75,7 @@ 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. @@ -247,7 +247,7 @@ There are three essential areas in which all transactions in the -permissions system fall: +permission system fall: Modification of methods and privileges @@ -308,7 +308,7 @@ API -The API to the permissions system consists of a few well-known tables, +The API to the permission system consists of a few well-known tables, plus a pair of PL/SQL procedures and a pair of Tcl functions. Tables @@ -384,7 +384,7 @@ User Interface -All users of the permissions system are the same at the user-interface +All users of the permission system are the same at the user-interface level. If you have the administer_privileges method permission on an object, then you may edit privileges for that object with the UI. @@ -412,7 +412,7 @@ Configuration/Parameters -There are no configuration options for the permissions system. +There are no configuration options for the permission system.