# HG changeset patch
# User Bryan O'Sullivan <bos@serpentine.com>
# Date 1154549336 25200
# Node ID e94202d88199af610848a3cbdfc16f3eecd5abb0
# Parent  0c998750744f6ae80abab521d3e2a6f9115de966
Tix fypos.

diff -r 0c998750744f -r e94202d88199 en/hook.tex
--- a/en/hook.tex	Tue Aug 01 12:38:13 2006 -0700
+++ b/en/hook.tex	Wed Aug 02 13:08:56 2006 -0700
@@ -151,7 +151,7 @@
 \section{Using hooks with shared access to a repository}
 
 If you want to use hooks to so some automated work in a repository
-that a number of people have ahred access to, you need to be careful
+that a number of people have shared access to, you need to be careful
 in how you do this.
 
 Mercurial only locks a repository when it is writing to the
@@ -177,7 +177,7 @@
 (which contains pointers to the new manifest data).  Before the first
 write to each file, it stores a record of where the end of the file
 was in its transaction log.  If the transaction must be rolled back,
-Mercurial simply truncates each file back to te size it was before the
+Mercurial simply truncates each file back to the size it was before the
 transaction began.
 
 When Mercurial \emph{reads} metadata, it reads the changelog first,
@@ -492,7 +492,7 @@
 whitespace from a file.  This is concise and useful enough that I will
 reproduce it here.
 \begin{codesample2}
-  perl -pi -e 's,\\s+$,,' filename
+  perl -pi -e 's,\\s+\$,,' filename
 \end{codesample2}
 
 \section{Bundled hooks}
@@ -631,7 +631,7 @@
 
 You can use this hook for the same purposes as the \hook{changegroup}
 hook (section~\ref{sec:hook:changegroup}); it's simply more convenient
-sometimes to run a hook once per group of changesets, while othher
+sometimes to run a hook once per group of changesets, while other
 times it's handier once per changeset.
 
 Parameters to this hook: