Index: openacs-4/packages/acs-core-docs/www/subsites-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites-requirements.html,v
diff -u -r1.34.2.3 -r1.34.2.4
--- openacs-4/packages/acs-core-docs/www/subsites-requirements.html	19 Nov 2016 09:21:55 -0000	1.34.2.3
+++ openacs-4/packages/acs-core-docs/www/subsites-requirements.html	6 Jan 2017 09:18:42 -0000	1.34.2.4
@@ -31,7 +31,7 @@
 forum messages associated with the current package instance. Joe is happy to
 realize that parameter::get is already smart enough to return configuration
 parameters for the current package instance, and so he has to do no extra
-work to tailor configuration parameters to the current subsite.</p><p>Jane Admin maintains www.company.com. She learns of Joe&#39;s work and
+work to tailor configuration parameters to the current subsite.</p><p>Jane Admin maintains www.company.com. She learns of Joe's work and
 would like to set up individual forums for the Boston and Austin offices of
 her company. The first thing she does is use the APM to install the new
 forum package.</p><p>Next, Jane uses the Subsite UI to create subsites for the Boston and
@@ -40,13 +40,13 @@
 http://www.company.com/offices/boston/forum, and similarly for the Austin
 office. At this point, the Boston and Austin office admins can customize the
 configurations for each of their forums, or they can just use the
-defaults.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-links"></a>Related Links</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a class="xref" href="subsites-design.html" title="Subsites Design Document">OpenACS 4 Subsites Design Document</a></p></li><li class="listitem"><p>Test plan (Not available yet)</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-api"></a>Requirements: Programmer&#39;s API</h3></div></div></div><p>A subsite API is required for programmers to ensure their packages are
+defaults.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-links"></a>Related Links</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a class="xref" href="subsites-design.html" title="Subsites Design Document">OpenACS 4 Subsites Design Document</a></p></li><li class="listitem"><p>Test plan (Not available yet)</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-api"></a>Requirements: Programmer's API</h3></div></div></div><p>A subsite API is required for programmers to ensure their packages are
 subsite-aware. The following functions should be sufficient for this:</p><p><span class="strong"><strong>10.10.0 Package creation</strong></span></p><p>The system must provide an API call to create a package, and it must be
 possible for the context (to which the package belongs) to be specified.</p><p><span class="strong"><strong>10.20.0 Package deletion</strong></span></p><p>The system must provide an API call to delete a package and all related
-objects in the subsite&#39;s context.</p><p><span class="strong"><strong>10.30.0 Object&#39;s package information</strong></span></p><p>Given an object ID, the system must provide an API call to determine the
+objects in the subsite's context.</p><p><span class="strong"><strong>10.30.0 Object's package information</strong></span></p><p>Given an object ID, the system must provide an API call to determine the
 package (ID) to which the object belongs.</p><p><span class="strong"><strong>10.40.0 URL from package</strong></span></p><p>Given a package (ID), the system must provide an API call to return the
-canonical URL for that package.</p><p><span class="strong"><strong>10.50.0 Main subsite&#39;s package_id</strong></span></p><p>The system must provide an API call to return a package ID corresponding
-to the main subsite&#39;s package ID (the degenerate subsite).</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-ui"></a>Requirements: The User Interface</h3></div></div></div><p><span class="strong"><strong>The Programmer&#39;s User Interface</strong></span></p><p>There is no programmer&#39;s UI, other than the API described above.</p><p><span class="strong"><strong>The Administrator&#39;s User Interface</strong></span></p><p>The UI for administrators is a set of HTML pages that are used to drive
+canonical URL for that package.</p><p><span class="strong"><strong>10.50.0 Main subsite's package_id</strong></span></p><p>The system must provide an API call to return a package ID corresponding
+to the main subsite's package ID (the degenerate subsite).</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="subsites-requirements-ui"></a>Requirements: The User Interface</h3></div></div></div><p><span class="strong"><strong>The Programmer's User Interface</strong></span></p><p>There is no programmer's UI, other than the API described above.</p><p><span class="strong"><strong>The Administrator's User Interface</strong></span></p><p>The UI for administrators is a set of HTML pages that are used to drive
 the underlying API for package instance management (i.e. adding, removing, or
 altering packages). It is restricted to administrators of the current subsite
 such that administrators can only manage their own subsites. Of course,