1.1 --- a/en/hook.tex	Tue Aug 01 12:38:13 2006 -0700
     1.2 +++ b/en/hook.tex	Wed Aug 02 13:08:56 2006 -0700
     1.3 @@ -151,7 +151,7 @@
     1.4  \section{Using hooks with shared access to a repository}
     1.5  
     1.6  If you want to use hooks to so some automated work in a repository
     1.7 -that a number of people have ahred access to, you need to be careful
     1.8 +that a number of people have shared access to, you need to be careful
     1.9  in how you do this.
    1.10  
    1.11  Mercurial only locks a repository when it is writing to the
    1.12 @@ -177,7 +177,7 @@
    1.13  (which contains pointers to the new manifest data).  Before the first
    1.14  write to each file, it stores a record of where the end of the file
    1.15  was in its transaction log.  If the transaction must be rolled back,
    1.16 -Mercurial simply truncates each file back to te size it was before the
    1.17 +Mercurial simply truncates each file back to the size it was before the
    1.18  transaction began.
    1.19  
    1.20  When Mercurial \emph{reads} metadata, it reads the changelog first,
    1.21 @@ -492,7 +492,7 @@
    1.22  whitespace from a file.  This is concise and useful enough that I will
    1.23  reproduce it here.
    1.24  \begin{codesample2}
    1.25 -  perl -pi -e 's,\\s+$,,' filename
    1.26 +  perl -pi -e 's,\\s+\$,,' filename
    1.27  \end{codesample2}
    1.28  
    1.29  \section{Bundled hooks}
    1.30 @@ -631,7 +631,7 @@
    1.31  
    1.32  You can use this hook for the same purposes as the \hook{changegroup}
    1.33  hook (section~\ref{sec:hook:changegroup}); it's simply more convenient
    1.34 -sometimes to run a hook once per group of changesets, while othher
    1.35 +sometimes to run a hook once per group of changesets, while other
    1.36  times it's handier once per changeset.
    1.37  
    1.38  Parameters to this hook: