Index: openacs-4/packages/acs-templating/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/requirements.html,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/acs-templating/www/doc/requirements.html	27 Oct 2014 16:40:14 -0000	1.2
+++ openacs-4/packages/acs-templating/www/doc/requirements.html	7 Aug 2017 23:48:02 -0000	1.3
@@ -21,7 +21,7 @@
       The following is a requirements document for the ACS Templating
       System version 0.5.  It has also been called Karl's Templates, the
       Dynamic Publishing System (DPS), and Stencil. The official package
-      name for the system is now <code><b>acs-templating</b></code>.
+      name for the system is now <code><strong>acs-templating</strong></code>.
 
     <a name="vision"></a>
       <h3>II. Vision Statement</h3>
@@ -80,19 +80,19 @@
       The template system is designed to be used by two classes of
       users: programmers and designers. In bulding a web site,
       programmers are generally responsible for defining and
-      implementing the <i>application logic</i> of the site, while
+      implementing the <em>application logic</em> of the site, while
       designers are more responsible for the
-      <i>presentation</i>. Generally speaking, the application logic
+      <em>presentation</em>. Generally speaking, the application logic
       generates data for the presentation to display to the user. The
       template system must provide mechanisms that supports both of
       these tasks and allows the designer and programmer to work
-      seperately, but for their work to be combined at runtime into
+      separately, but for their work to be combined at runtime into
       something that the user sees as a single page.
     </p>
     <p>
-      Thus, pages are naturally split into two parts. The <i>logic
-	part</i> executes application logic and generates data, and the
-      <i>presentation</i> part that specifies the layout of the page
+      Thus, pages are naturally split into two parts. The <em>logic
+	part</em> executes application logic and generates data, and the
+      <em>presentation</em> part that specifies the layout of the page
       and so on.
     </p>
     <p>
@@ -102,8 +102,8 @@
       <li>
 	A notation and API for the programmer specify the application
 	logic and to generate the data to be displayed. In ACS, we
-	call the data that we wish to display a <i>data source</i> or
-	<i>page property</i>. Application logic is driven by the
+	call the data that we wish to display a <em>data source</em> or
+	<em>page property</em>. Application logic is driven by the
 	inputs the page gathers from the user request (e.g. the HTTP
 	request), and the computation that the page must perform on
 	this input. This computation will generally create and
@@ -224,8 +224,8 @@
 	    <strong>10.10.2 Use of Components</strong>
 	    <p>
 	      To speed development and ensure consistency of design, template
-	      authors are encouraged to assemble pages from distinct <i>component
-		templates</i> that may be recycled in different contexts. One typical
+	      authors are encouraged to assemble pages from distinct <em>component
+		templates</em> that may be recycled in different contexts. One typical
 	      practice is to build a "master" template for an entire section of
 	      a site, with a common header, footer and sidebar layout. For each
 	      page request, the "content" template is incorporated dynamically
@@ -255,9 +255,9 @@
 	      specific data being presented. For example, when presenting a list
 	      of library books that a user has checked out, the designer might
 	      want to highlight the overdue ones in red. For this, designers
-	      must have the ability to write simple program logic (<i>Note: We
+	      must have the ability to write simple program logic (<em>Note: We
 		run the risk of inventing our own language here, we must be
-		careful</i>).
+		careful</em>).
 	    </p>
 
 	  </li>
@@ -384,10 +384,10 @@
 
     <h3>VII. Revision History</h3>
 
-    <table cellpadding=2 cellspacing=2 width=90% bgcolor=#efefef>
-    <tr bgcolor=#e0e0e0>
-    <th width=10%>Document Revision #</th>
-    <th width=50%>Action Taken, Notes</th>
+    <table cellpadding="2" cellspacing="2" width="90%" bgcolor="#efefef">
+    <tr bgcolor="#e0e0e0">
+    <th width="10%">Document Revision #</th>
+    <th width="50%">Action Taken, Notes</th>
     <th>When?</th>
     <th>By Whom?</th>
     </tr>