hgbook

diff en/ch00-preface.xml @ 609:c44d5854620b

Fix up chapter 1.
author Bryan O'Sullivan <bos@serpentine.com>
date Tue Mar 31 22:38:30 2009 -0700 (2009-03-31)
parents 4ce9d0754af3
children 3b33dd6aba87
line diff
     1.1 --- a/en/ch00-preface.xml	Thu Mar 26 21:22:03 2009 -0700
     1.2 +++ b/en/ch00-preface.xml	Tue Mar 31 22:38:30 2009 -0700
     1.3 @@ -68,9 +68,10 @@
     1.4  	    project.</para></listitem>
     1.5        </itemizedlist>
     1.6  
     1.7 -      <para id="x_76">Most of these reasons are equally valid---at least in
     1.8 -	theory---whether you're working on a project by yourself, or
     1.9 -	with a hundred other people.</para>
    1.10 +      <para id="x_76">Most of these reasons are equally
    1.11 +	valid&emdash;at least in theory&emdash;whether you're working
    1.12 +	on a project by yourself, or with a hundred other
    1.13 +	people.</para>
    1.14  
    1.15        <para id="x_77">A key question about the practicality of revision control
    1.16  	at these two different scales (<quote>lone hacker</quote> and
    1.17 @@ -143,7 +144,7 @@
    1.18      <title>About the examples in this book</title>
    1.19  
    1.20      <para id="x_84">This book takes an unusual approach to code samples.  Every
    1.21 -      example is <quote>live</quote>---each one is actually the result
    1.22 +      example is <quote>live</quote>&emdash;each one is actually the result
    1.23        of a shell script that executes the Mercurial commands you see.
    1.24        Every time an image of the book is built from its sources, all
    1.25        the example scripts are automatically run, and their current
    1.26 @@ -353,8 +354,8 @@
    1.27  	centralised system to fall over under the combined load of
    1.28  	just a few dozen concurrent users.  Once again, the typical
    1.29  	response tends to be an expensive and clunky replication
    1.30 -	facility.  Since the load on a central server---if you have
    1.31 -	one at all---is many times lower with a distributed tool
    1.32 +	facility.  Since the load on a central server&emdash;if you have
    1.33 +	one at all&emdash;is many times lower with a distributed tool
    1.34  	(because all of the data is replicated everywhere), a single
    1.35  	cheap server can handle the needs of a much larger team, and
    1.36  	replication to balance load becomes a simple matter of