changeset 285:814698eebbaf

fixed a typo and formatted the notify hook configuration example nicer.

--- a/en/hook.tex	Fri Jan 04 13:04:07 2008 -0800
+++ b/en/hook.tex	Fri Jan 04 22:09:00 2008 +0100
@@ -916,14 +916,14 @@
   config = /home/hg/repos/notify/notify.conf
   # repos live in /home/hg/repos on server, so strip 4 "/" chars
   strip = 4
-  template = X-Hg-Repo: \{webroot\}\\n\\\\
-    Subject: \{webroot\}: \{desc|firstline|strip\}\\n\\\\
-    From: \{author\}\\n\\\\
-    \\n\\\\
-    changeset \{node|short\} in \{root\}\\n\\\\
-    details: \{baseurl\}\{webroot\}?cmd=changeset;node=\{node|short\}\\n\\\\
-    description:\\n\\\\
-    \\t\{desc|tabindent|strip\}
+  template = X-Hg-Repo: \{webroot\}
+    Subject: \{webroot\}: \{desc|firstline|strip\}
+    From: \{author\}
+
+    changeset \{node|short\} in \{root\}
+    details: \{baseurl\}\{webroot\}?cmd=changeset;node=\{node|short\}
+    description:
+      \{desc|tabindent|strip\}
 
   [web]
   baseurl = http://hg.example.com/

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