Index: openacs-4/packages/acs-core-docs/www/requirements-template.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/requirements-template.html,v
diff -u -N -r1.49.2.12 -r1.49.2.13
--- openacs-4/packages/acs-core-docs/www/requirements-template.html	19 Nov 2016 09:21:55 -0000	1.49.2.12
+++ openacs-4/packages/acs-core-docs/www/requirements-template.html	6 Jan 2017 09:18:42 -0000	1.49.2.13
@@ -17,15 +17,15 @@
       <span class="emphasis"><em>Very broadly, describe how the system meets a need of a business,
 	group, the OpenACS as a whole, etc.  Make sure that technical and
 	non-technical readers alike would understand what the system would do
-	and why it&#39;s useful.  Whenever applicable, you should explicitly state
+	and why it's useful.  Whenever applicable, you should explicitly state
 	what the business value of the system is. </em></span>
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-system-app-overview"></a>System/Application Overview</h3></div></div></div><p>
       <span class="emphasis"><em>Discuss the high-level breakdown of the components that make up
 	the system.  You can go by functional areas, by the main transactions
 	the system allows, etc. </em></span> 
     </p><p>
       <span class="emphasis"><em>You should also state the context and dependencies of the system
-	here, e.g. if it&#39;s an application-level package for OpenACS 4, briefly
+	here, e.g. if it's an application-level package for OpenACS 4, briefly
 	describe how it uses kernel services, like permissions or subsites. </em></span>
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-cases"></a>Use-cases and User-scenarios</h3></div></div></div><p>
       <span class="emphasis"><em>Determine the types or classes of users who would use the
@@ -34,18 +34,18 @@
 	take, and how the system would support them.</em></span>  
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-competitive-analysis"></a>Optional: Competitive Analysis</h3></div></div></div><p>
       <span class="emphasis"><em>Describe other systems or services that are comparable to what
-	you&#39;re building.  If applicable, say why your implementation will be
+	you're building.  If applicable, say why your implementation will be
 	superior, where it will match the competition, and where/why it will
 	lack existing best-of-breed capabilities.  This section is also in the
 	Design doc, so write about it where you deem most appropriate.</em></span>
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-links"></a>Related Links</h3></div></div></div><p>Include all pertinent links to supporting and related material,
-      such as: </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> System/Package "coversheet" - where all documentation for this software is linked off of</p></li><li class="listitem"><p> Design document</p></li><li class="listitem"><p> Developer&#39;s guide</p></li><li class="listitem"><p> User&#39;s guide</p></li><li class="listitem"><p> Other-cool-system-related-to-this-one document</p></li><li class="listitem"><p> Test plan </p></li><li class="listitem"><p> Competitive system(s)</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-requirements"></a>Requirements</h3></div></div></div><p>
+      such as: </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> System/Package "coversheet" - where all documentation for this software is linked off of</p></li><li class="listitem"><p> Design document</p></li><li class="listitem"><p> Developer's guide</p></li><li class="listitem"><p> User's guide</p></li><li class="listitem"><p> Other-cool-system-related-to-this-one document</p></li><li class="listitem"><p> Test plan </p></li><li class="listitem"><p> Competitive system(s)</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="yourpackage-requirements-requirements"></a>Requirements</h3></div></div></div><p>
       <span class="emphasis"><em>The main course of the document, requirements. Break up the
 	requirements sections (A, B, C, etc.) as needed.  Within each section,
 	create a list denominated with unique identifiers that reflect any
 	functional hierarchy present, e.g. 20.5.13. - for the first number,
 	leave generous gaps on the first writing of requirements (e.g. 1, 10,
-	20, 30, 40, etc.) because you&#39;ll want to leave room for any missing
+	20, 30, 40, etc.) because you'll want to leave room for any missing
 	key requirements that may arise.  </em></span>
     </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><span class="strong"><strong>10.0 A Common Solution</strong></span></p><p>
 	  Programmers and designers should only have to learn a single