Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml,v
diff -u -r1.10.12.1 -r1.10.12.2
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml	7 Sep 2013 14:36:49 -0000	1.10.12.1
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/templates.xml	28 Sep 2013 15:52:12 -0000	1.10.12.2
@@ -187,33 +187,10 @@
 Master templates allow you do centralize display code that is used
 throughout an application in a single file. In this case, we intend to
 have a master template that does the standard page headers and footers
-for us - create the <computeroutput>master.adp</computeroutput> file, which looks like
-this:
+for us
 </para>
 
- 
-
-<programlisting>
-
-&lt;%= [ad_header $title] %&gt; 
-&lt;h2&gt;@title@&lt;/h2&gt; 
-&lt;%= [eval ad_context_bar $context_bar] %&gt; 
-&lt;hr&gt; 
-&lt;slave&gt; 
-&lt;br clear="all"&gt; 
-&lt;%= [ad_footer] %&gt;
-
-</programlisting>
-
-
 <para>
-The main subtlety in this code is the inline Tcl code for running
-procs to build the header, footer, context bar, etc.  Also, note the
-property substitutions that happen here, the values of which are set
-up in the <computeroutput>&lt;property&gt;</computeroutput> tags in the slave page.  
-</para>
-
-<para>
 After putting all these files into
 <computeroutput>ROOT/packages/notes/www</computeroutput>, you should be able to go to
 <computeroutput>/notes/</computeroutput> URL for your server and see the input form.