1.1 --- a/en/ch10-template.xml	Thu Mar 19 21:18:52 2009 -0700
     1.2 +++ b/en/ch10-template.xml	Tue Mar 31 12:21:50 2009 -0700
     1.3 @@ -107,7 +107,7 @@
     1.4        <emphasis>escape sequence</emphasis>, telling Mercurial to print
     1.5        a newline at the end of each template item.  If you omit this
     1.6        newline, Mercurial will run each piece of output together.  See
     1.7 -      section <xref linkend="sec:template:escape"/> for more details
     1.8 +      <xref linkend="sec:template:escape"/> for more details
     1.9        of escape sequences.</para>
    1.10  
    1.11      <para id="x_587">A template that prints a fixed string of text all the time
    1.12 @@ -121,11 +121,10 @@
    1.13        been replaced in the output with the description of each
    1.14        changeset.  Every time Mercurial finds text enclosed in curly
    1.15        braces (<quote><literal>{</literal></quote> and
    1.16 -      <quote><literal>}</literal></quote>), it will try to replace the braces
    1.17 -      and text with the expansion of whatever is inside.  To print a
    1.18 -      literal curly brace, you must escape it, as described in section
    1.19 -      <xref
    1.20 -	linkend="sec:template:escape"/>.</para>
    1.21 +      <quote><literal>}</literal></quote>), it will try to replace the
    1.22 +      braces and text with the expansion of whatever is inside.  To
    1.23 +      print a literal curly brace, you must escape it, as described in
    1.24 +      <xref linkend="sec:template:escape"/>.</para>
    1.25  
    1.26    </sect1>
    1.27    <sect1 id="sec:template:keyword">
    1.28 @@ -149,7 +148,7 @@
    1.29  	  Date information.  The date when the changeset was
    1.30  	  committed.  This is <emphasis>not</emphasis> human-readable;
    1.31  	  you must pass it through a filter that will render it
    1.32 -	  appropriately.  See section <xref
    1.33 +	  appropriately.  See <xref
    1.34  	    linkend="sec:template:filter"/> for more information
    1.35  	  on filters. The date is expressed as a pair of numbers.  The
    1.36  	  first number is a Unix UTC timestamp (seconds since January
    1.37 @@ -197,8 +196,7 @@
    1.38      <para id="x_596">As we noted above, the date keyword does not produce
    1.39        human-readable output, so we must treat it specially.  This
    1.40        involves using a <emphasis>filter</emphasis>, about which more
    1.41 -      in section <xref
    1.42 -	linkend="sec:template:filter"/>.</para>
    1.43 +      in <xref linkend="sec:template:filter"/>.</para>
    1.44  
    1.45      &interaction.template.simple.datekeyword;
    1.46