Index: openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp,v
diff -u -r1.1.2.10 -r1.1.2.11
--- openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp	21 Jun 2016 07:44:35 -0000	1.1.2.10
+++ openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp	23 Jun 2016 08:32:45 -0000	1.1.2.11
@@ -18,18 +18,18 @@
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="idp140641349548960" id="idp140641349548960"></a>Setting Permission on an OpenACS
-package</h3></div></div></div><p>After you've installed and mounted your package, you can
+package</h3></div></div></div><p>After you&#39;ve installed and mounted your package, you can
 configure each instance to act as you would like.</p><p>This is done from the Applications page. Log in, go to the Admin
 or Control Panel, click on the subsite the application is in, and
-click on Applications. If you click on the 'Permissions' link, you
-will see and be able to set the permissions for that
+click on Applications. If you click on the 'Permissions'
+link, you will see and be able to set the permissions for that
 application.</p><p>Each application may have different behavior for what Read
 Create Write and Admin permissions mean, but generally the
 permissions are straightforward. If you find the behavior is not
 what you expect after setting permissions, you can post a bug in
-the OpenACS bugtracker.</p><p>'The Public' refers to users to the website who are not logged
-in. 'Registered Users' are people who have registered for the
-site.</p>
+the OpenACS bugtracker.</p><p>'The Public' refers to users to the website who are not
+logged in. 'Registered Users' are people who have
+registered for the site.</p>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"