Index: openacs-4/packages/acs-core-docs/www/permissions.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions.adp,v
diff -u -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/acs-core-docs/www/permissions.adp	26 Aug 2020 07:46:25 -0000	1.4.2.2
+++ openacs-4/packages/acs-core-docs/www/permissions.adp	5 Jan 2021 17:33:40 -0000	1.4.2.3
@@ -109,7 +109,7 @@
 explicitly require admin privileges. No substitutions.</p><p>To give a user permission to perform a particular operation on a
 particular object you call <code class="computeroutput">acs_permission.grant_permission</code> like
 this:</p><pre class="programlisting">
-# sql code
+# SQL code
     acs_permission.grant_permission (
       object_id =&gt; some_object_id,
       grantee_id =&gt; some_party_id,
@@ -119,7 +119,7 @@
 </pre><p>Using just these mechanisms is enough for developers and
 administrators to effectively define access control for every
 object in a system.</p><p>Explicitly defining permissions to every object individually
-would become very tedious. OpenACS provides a object contexts as a
+would become very tedious. OpenACS provides object contexts as a
 means for controlling permissions of a large group of objects at
 the same time.</p>
 </div><div class="sect2">
@@ -206,4 +206,4 @@
 Pages"
 			homeLink="index" homeLabel="Home" 
 			upLink="dev-guide" upLabel="Up"> 
-		    
\ No newline at end of file
+