1.1 --- a/en/mq.tex	Tue Jul 04 15:00:18 2006 -0700
     1.2 +++ b/en/mq.tex	Tue Jul 04 16:41:31 2006 -0700
     1.3 @@ -310,8 +310,8 @@
     1.4  
     1.5  Here's an example that illustrates how you can use this ability.
     1.6  Let's say you're developing a new feature as two patches.  The first
     1.7 -is a change to the core of your software, and the second--layered on
     1.8 -top of the first--changes the user interface to use the code you just
     1.9 +is a change to the core of your software, and the second---layered on
    1.10 +top of the first---changes the user interface to use the code you just
    1.11  added to the core.  If you notice a bug in the core while you're
    1.12  working on the UI patch, it's easy to fix the core.  Simply
    1.13  \hgcmd{qrefresh} the UI patch to save your in-progress changes, and
    1.14 @@ -439,8 +439,8 @@
    1.15  \begin{itemize}
    1.16  \item The context in the middle of a hunk has changed.
    1.17  \item A hunk is missing some context at the beginning or end.
    1.18 -\item A large hunk might apply better--either entirely or in part--if
    1.19 -  it was broken up into smaller hunks.
    1.20 +\item A large hunk might apply better---either entirely or in
    1.21 +  part---if it was broken up into smaller hunks.
    1.22  \item A hunk removes lines with slightly different content than those
    1.23    currently present in the file.
    1.24  \end{itemize}
    1.25 @@ -629,7 +629,7 @@
    1.26  
    1.27  The \command{diffstat} command~\cite{web:diffstat} generates a
    1.28  histogram of the modifications made to each file in a patch.  It
    1.29 -provides a good way to ``get a sense of'' a patch--which files it
    1.30 +provides a good way to ``get a sense of'' a patch---which files it
    1.31  affects, and how much change it introduces to each file and as a
    1.32  whole.  (I find that it's a good idea to use \command{diffstat}'s
    1.33  \texttt{-p} option as a matter of course, as otherwise it will try to