Index: openacs-4/packages/acs-templating/www/doc/guide/composite.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/composite.html,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/acs-templating/www/doc/guide/composite.html	7 Aug 2017 23:48:03 -0000	1.4
+++ openacs-4/packages/acs-templating/www/doc/guide/composite.html	27 Mar 2018 11:18:00 -0000	1.5
@@ -167,7 +167,7 @@
       Any (sub)page can have 0 or 1 master and 0 or more included
       pages.  Each page has its own <em>separate</em> scope for
       variables.  Arguments can be passed to dependent pages as
-      attributes to <code>&lt;inlcude&gt;</code>, or as properties to
+      attributes to <code>&lt;include&gt;</code>, or as properties to
       <code>&lt;master&gt;</code>.  The directed graph of pages will
       often be be acyclic, as in the example, but this is not
       required.
@@ -178,7 +178,7 @@
     <p>
       Sometimes it is of interest in which order the different
       parts are evaluated.  The "code" always runs first, followed by
-      the template.  The <code>&lt;inlcude&gt;</code> tag causes the
+      the template.  The <code>&lt;include&gt;</code> tag causes the
       subpage to be evaluated at this point of the template, and the
       rest of the including template is evaluated after that's done.
       This is like a procedure call.  In contrast, the