Index: openacs-4/packages/acs-templating/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/design.adp,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/acs-templating/www/doc/design.adp	29 Oct 2017 11:33:10 -0000	1.4
+++ openacs-4/packages/acs-templating/www/doc/design.adp	29 Dec 2017 09:59:11 -0000	1.5
@@ -32,7 +32,7 @@
 substrate for all the functionally specific modules used on a site.
 The system should not make any assumptions about how pages should
 look or function. Designers should be able to change the default
-presentation of any module using a single metholodogy with minimal
+presentation of any module using a single methodology with minimal
 exposure to code.</p></li><li><p>
 <strong>Separation of code (Tcl, Java and SQL) and layout
 (HTML).</strong> Programmers should be able to specify the data
@@ -189,7 +189,7 @@
 <ol>
 <li>The request processor gets a url and maps it to a
 <code>.adp</code> or <code>.tcl</code> file. As both invoke the
-same handler, it doesn&#39;t matter that adp take precendence.</li><li>If a <code>.tcl</code> file is present, its <a href="/api-doc/proc-view?proc=ad_page_contract"><code>ad_page_contract</code></a>
+same handler, it doesn&#39;t matter that adp take precedence.</li><li>If a <code>.tcl</code> file is present, its <a href="/api-doc/proc-view?proc=ad_page_contract"><code>ad_page_contract</code></a>
 in the <code>-properties</code> block indicates a set of data
 sources that will be made available to the template.</li><li>The rest of the Tcl script executes, defining these data
 sources. It may change the name of the page being served by calling