diff en/ch00-preface.xml @ 766:3b33dd6aba87

Merge with http://hg.serpentine.com/mercurial/book
author Dongsheng Song <songdongsheng@live.cn>
date Thu, 02 Apr 2009 09:24:36 +0800
parents 1c13ed2130a7 c44d5854620b
children b338f5490029
line wrap: on
line diff
--- a/en/ch00-preface.xml	Tue Mar 31 21:17:59 2009 +0800
+++ b/en/ch00-preface.xml	Thu Apr 02 09:24:36 2009 +0800
@@ -68,9 +68,10 @@
 	    project.</para></listitem>
       </itemizedlist>
 
-      <para id="x_76">Most of these reasons are equally valid---at least in
-	theory---whether you're working on a project by yourself, or
-	with a hundred other people.</para>
+      <para id="x_76">Most of these reasons are equally
+	valid&emdash;at least in theory&emdash;whether you're working
+	on a project by yourself, or with a hundred other
+	people.</para>
 
       <para id="x_77">A key question about the practicality of revision control
 	at these two different scales (<quote>lone hacker</quote> and
@@ -143,7 +144,7 @@
     <title>About the examples in this book</title>
 
     <para id="x_84">This book takes an unusual approach to code samples.  Every
-      example is <quote>live</quote>---each one is actually the result
+      example is <quote>live</quote>&emdash;each one is actually the result
       of a shell script that executes the Mercurial commands you see.
       Every time an image of the book is built from its sources, all
       the example scripts are automatically run, and their current
@@ -353,8 +354,8 @@
 	centralised system to fall over under the combined load of
 	just a few dozen concurrent users.  Once again, the typical
 	response tends to be an expensive and clunky replication
-	facility.  Since the load on a central server---if you have
-	one at all---is many times lower with a distributed tool
+	facility.  Since the load on a central server&emdash;if you have
+	one at all&emdash;is many times lower with a distributed tool
 	(because all of the data is replicated everywhere), a single
 	cheap server can handle the needs of a much larger team, and
 	replication to balance load becomes a simple matter of