1.1 --- a/en/hook.tex	Fri Jan 04 13:04:07 2008 -0800
     1.2 +++ b/en/hook.tex	Fri Jan 04 22:09:00 2008 +0100
     1.3 @@ -916,14 +916,14 @@
     1.4    config = /home/hg/repos/notify/notify.conf
     1.5    # repos live in /home/hg/repos on server, so strip 4 "/" chars
     1.6    strip = 4
     1.7 -  template = X-Hg-Repo: \{webroot\}\\n\\\\
     1.8 -    Subject: \{webroot\}: \{desc|firstline|strip\}\\n\\\\
     1.9 -    From: \{author\}\\n\\\\
    1.10 -    \\n\\\\
    1.11 -    changeset \{node|short\} in \{root\}\\n\\\\
    1.12 -    details: \{baseurl\}\{webroot\}?cmd=changeset;node=\{node|short\}\\n\\\\
    1.13 -    description:\\n\\\\
    1.14 -    \\t\{desc|tabindent|strip\}
    1.15 +  template = X-Hg-Repo: \{webroot\}
    1.16 +    Subject: \{webroot\}: \{desc|firstline|strip\}
    1.17 +    From: \{author\}
    1.18 +
    1.19 +    changeset \{node|short\} in \{root\}
    1.20 +    details: \{baseurl\}\{webroot\}?cmd=changeset;node=\{node|short\}
    1.21 +    description:
    1.22 +      \{desc|tabindent|strip\}
    1.23  
    1.24    [web]
    1.25    baseurl = http://hg.example.com/

     2.1 --- a/en/mq.tex	Fri Jan 04 13:04:07 2008 -0800
     2.2 +++ b/en/mq.tex	Fri Jan 04 22:09:00 2008 +0100
     2.3 @@ -31,7 +31,7 @@
     2.4  When you have few changes to maintain, it is easy to manage a single
     2.5  patch using the standard \command{diff} and \command{patch} programs
     2.6  (see section~\ref{sec:mq:patch} for a discussion of these tools).
     2.7 -Once the number of changes grows, it starts to makes sense to maintain
     2.8 +Once the number of changes grows, it starts to make sense to maintain
     2.9  patches as discrete ``chunks of work,'' so that for example a single
    2.10  patch will contain only one bug fix (the patch might modify several
    2.11  files, but it's doing ``only one thing''), and you may have a number