1.1 --- a/en/ch01-tour-basic.xml	Sun May 03 19:23:08 2009 -0700
     1.2 +++ b/en/ch01-tour-basic.xml	Sun May 03 19:23:31 2009 -0700
     1.3 @@ -53,7 +53,7 @@
     1.4  	  <programlisting>apt-get install mercurial</programlisting></listitem>
     1.5  	<listitem><para id="x_5">Fedora:</para>
     1.6  	  <programlisting>yum install mercurial</programlisting></listitem>
     1.7 -	<listitem><para>OpenSUSE:</para>
     1.8 +	<listitem><para id="x_715">OpenSUSE:</para>
     1.9  	  <programlisting>zypper install mercurial</programlisting></listitem>
    1.10  	<listitem><para id="x_6">Gentoo:</para>
    1.11  	  <programlisting>emerge mercurial</programlisting></listitem>
    1.12 @@ -601,7 +601,7 @@
    1.13  	<tip>
    1.14  	  <title><quote>Home directory</quote> on Windows</title>
    1.15  
    1.16 -	  <para>When we refer to your home directory, on an English
    1.17 +	  <para id="x_716">When we refer to your home directory, on an English
    1.18  	    language installation of Windows this will usually be a
    1.19  	    folder named after your user name in
    1.20  	    <filename>C:\Documents and Settings</filename>.  You can
    1.21 @@ -712,7 +712,7 @@
    1.22        <note>
    1.23  	<title>A surprise for Subversion users</title>
    1.24  
    1.25 -	<para>Like other Mercurial commands, if we don't supply
    1.26 +	<para id="x_717">Like other Mercurial commands, if we don't supply
    1.27  	  explicit names to commit to the <command role="hg-cmd">hg
    1.28  	    commit</command>, it will operate across a repository's
    1.29  	  entire working directory.  Be wary of this if you're coming
    1.30 @@ -821,7 +821,7 @@
    1.31  	  possible to pull more changes than you saw when using
    1.32  	  <command role="hg-cmd">hg incoming</command>.</para>
    1.33  
    1.34 -	<para>If you only want to pull precisely the changes that were
    1.35 +	<para id="x_718">If you only want to pull precisely the changes that were
    1.36  	  listed by <command role="hg-cmd">hg incoming</command>, or
    1.37  	  you have some other reason to pull a subset of changes,
    1.38  	  simply identify the change that you want to pull by its
    1.39 @@ -943,7 +943,7 @@
    1.40      <sect2>
    1.41        <title>Default locations</title>
    1.42  
    1.43 -      <para>When we clone a repository, Mercurial records the location
    1.44 +      <para id="x_719">When we clone a repository, Mercurial records the location
    1.45  	of the repository we cloned in the
    1.46  	<filename>.hg/hgrc</filename> file of the new repository.  If
    1.47  	we don't supply a location to <command>hg pull</command> from
    1.48 @@ -951,14 +951,14 @@
    1.49  	location as a default.  The <command>hg incoming</command>
    1.50  	and <command>hg outgoing</command> commands do so too.</para>
    1.51  
    1.52 -      <para>If you open a repository's <filename>.hg/hgrc</filename>
    1.53 +      <para id="x_71a">If you open a repository's <filename>.hg/hgrc</filename>
    1.54  	file in a text editor, you will see contents like the
    1.55  	following.</para>
    1.56  
    1.57        <programlisting>[paths]
    1.58  default = http://www.selenic.com/repo/hg</programlisting>
    1.59  
    1.60 -      <para>It is possible&emdash;and often useful&emdash;to have the
    1.61 +      <para id="x_71b">It is possible&emdash;and often useful&emdash;to have the
    1.62  	default location for <command>hg push</command> and
    1.63  	<command>hg outgoing</command> be different from those for
    1.64  	<command>hg pull</command> and <command>hg incoming</command>.