1.1 --- a/en/undo.tex	Thu Dec 28 14:06:15 2006 -0800
     1.2 +++ b/en/undo.tex	Mon Mar 26 22:24:39 2007 -0700
     1.3 @@ -620,17 +620,17 @@
     1.4  \command{grep} command to see if our ``bad'' file is present in the
     1.5  working directory.  If it is, this revision is bad; if not, this
     1.6  revision is good.
     1.7 -\interaction{search.step1}
     1.8 +\interaction{bisect.search.step1}
     1.9  
    1.10  This test looks like a perfect candidate for automation, so let's turn
    1.11  it into a shell function.
    1.12 -\interaction{search.mytest}
    1.13 +\interaction{bisect.search.mytest}
    1.14  We can now run an entire test step with a single command,
    1.15  \texttt{mytest}.
    1.16 -\interaction{search.step2}
    1.17 +\interaction{bisect.search.step2}
    1.18  A few more invocations of our canned test step command, and we're
    1.19  done.
    1.20 -\interaction{search.rest}
    1.21 +\interaction{bisect.search.rest}
    1.22  
    1.23  Even though we had~40 changesets to search through, the \hgext{bisect}
    1.24  extension let us find the changeset that introduced our ``bug'' with
    1.25 @@ -647,7 +647,7 @@
    1.26  doesn't use much space, so it doesn't matter if you forget to run this
    1.27  command.  However, \hgext{bisect} won't let you start a new search in
    1.28  that repository until you do a \hgcmdargs{bisect}{reset}.
    1.29 -\interaction{search.reset}
    1.30 +\interaction{bisect.search.reset}
    1.31  
    1.32  \section{Tips for finding bugs effectively}
    1.33