1.1 --- a/en/appB-mq-ref.xml	Mon May 04 23:52:38 2009 -0700
     1.2 +++ b/en/appB-mq-ref.xml	Mon May 04 23:53:21 2009 -0700
     1.3 @@ -75,7 +75,7 @@
     1.4        <title><command role="hg-ext-mq">qfold</command>&emdash;move
     1.5  	applied patches into repository history</title>
     1.6  
     1.7 -      <para>The <command>hg qfinish</command> command converts the
     1.8 +      <para id="x_72d">The <command>hg qfinish</command> command converts the
     1.9  	specified applied patches into permanent changes by moving
    1.10  	them out of MQ's control so that they will be treated as
    1.11  	normal repository history.</para>

     2.1 --- a/en/ch02-tour-merge.xml	Mon May 04 23:52:38 2009 -0700
     2.2 +++ b/en/ch02-tour-merge.xml	Mon May 04 23:53:21 2009 -0700
     2.3 @@ -428,21 +428,21 @@
     2.4    <sect1>
     2.5      <title>Renaming, copying, and merging</title>
     2.6  
     2.7 -    <para>During the life of a project, we will often want to change
     2.8 +    <para id="x_729">During the life of a project, we will often want to change
     2.9        the layout of its files and directories. This can be as simple
    2.10        as renaming a single file, or as complex as restructuring the
    2.11        entire hierarchy of files within the project.</para>
    2.12  
    2.13 -    <para>Mercurial supports these kinds of complex changes fluently,
    2.14 +    <para id="x_72a">Mercurial supports these kinds of complex changes fluently,
    2.15        provided we tell it what we're doing.  If we want to rename a
    2.16        file, we should use the <command>hg rename</command><footnote>
    2.17 -	<para>If you're a Unix user, you'll be glad to know that the
    2.18 +	<para id="x_72b">If you're a Unix user, you'll be glad to know that the
    2.19  	  <command>hg rename</command> command can be abbreviated as
    2.20  	  <command>hg mv</command>.</para>
    2.21        </footnote> command to rename it, so that Mercurial can do the
    2.22        right thing later when we merge.</para>
    2.23  
    2.24 -    <para>We will cover the use of these commands in more detail in
    2.25 +    <para id="x_72c">We will cover the use of these commands in more detail in
    2.26        <xref linkend="chap:daily.copy"/>.</para>
    2.27    </sect1>
    2.28  </chapter>

     3.1 --- a/en/ch03-concepts.xml	Mon May 04 23:52:38 2009 -0700
     3.2 +++ b/en/ch03-concepts.xml	Mon May 04 23:53:21 2009 -0700
     3.3 @@ -116,7 +116,7 @@
     3.4  	Mercurial tracks hasn't changed between two changesets, the
     3.5  	entry for that file in the two revisions of the manifest will
     3.6  	point to the same revision of its filelog<footnote>
     3.7 -	  <para>It is possible (though unusual) for the manifest to
     3.8 +	  <para id="x_725">It is possible (though unusual) for the manifest to
     3.9  	    remain the same between two changesets, in which case the
    3.10  	    changelog entries for those changesets will point to the
    3.11  	    same revision of the manifest.</para>
    3.12 @@ -746,7 +746,7 @@
    3.13  
    3.14        <itemizedlist>
    3.15  	<listitem>
    3.16 -	  <para>When Mercurial checks the state of a file in the
    3.17 +	  <para id="x_726">When Mercurial checks the state of a file in the
    3.18  	    working directory, it first checks a file's modification
    3.19  	    time against the time in the dirstate that records when
    3.20  	    Mercurial last wrote the file. If the last modified time
    3.21 @@ -755,7 +755,7 @@
    3.22  	    need to check any further.</para>
    3.23  	</listitem>
    3.24  	<listitem>
    3.25 -	  <para>If the file's size has changed, the file must have
    3.26 +	  <para id="x_727">If the file's size has changed, the file must have
    3.27  	    been modified.  If the modification time has changed, but
    3.28  	    the size has not, only then does Mercurial need to
    3.29  	    actually read the contents of the file to see if it has
    3.30 @@ -763,7 +763,7 @@
    3.31  	</listitem>
    3.32        </itemizedlist>
    3.33  
    3.34 -      <para>Storing the modification time and size dramatically
    3.35 +      <para id="x_728">Storing the modification time and size dramatically
    3.36  	reduces the number of read operations that Mercurial needs to
    3.37  	perform when we run commands like <command>hg status</command>.
    3.38  	This results in large performance improvements.</para>