Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml,v
diff -u -N -r1.17 -r1.18
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml	11 Dec 2010 23:36:32 -0000	1.17
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml	7 Aug 2017 23:47:54 -0000	1.18
@@ -272,7 +272,7 @@
 <para>
 The first row represents an entry in User 123's personal address book,
 the second row represents an entry in User Group 456's shared address
-book, and the third row represents an entry in the site's public
+book, and the third row represents an entry in the site&#39;s public
 address book. In this way, the scoping columns identify the security context in
 which a given object belongs, where each context is <emphasis>either</emphasis> a
 person <emphasis>or</emphasis> a group of people <emphasis>or</emphasis> the general public
@@ -310,7 +310,7 @@
 forum. Then, suppose we grant every user in the system read-access to
 this forum. By default, they will automatically have read-access to
 the new message we just inserted, since the system automatically
-checks permissions on the message's context. To allow the creator of
+checks permissions on the message&#39;s context. To allow the creator of
 the message to change the message after it has been posted we grant
 the user write-access on the message, and we are done.
 </para>