X-Git-Url: https://git.verplant.org/?a=blobdiff_plain;f=Documentation%2Fcvs-migration.txt;h=8fd1a33499b34bea37a8a2ac3ce80f6681dfee86;hb=5df466c507ee2dd81c2e9002c3fedf3536cde0dc;hp=57436f00783a7f6682431b24a5719effd04faf32;hpb=72e5890b68e7199d92620d3bba91fa36dd259404;p=git.git

diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
index 57436f00..8fd1a334 100644
--- a/Documentation/cvs-migration.txt
+++ b/Documentation/cvs-migration.txt
@@ -138,7 +138,7 @@ mailing list archives for details).
 git has a couple of alternatives, though, that you may find sufficient
 or even superior depending on your use.  One is called "git-whatchanged"
 (for obvious reasons) and the other one is called "pickaxe" ("a tool for
-the software archeologist"). 
+the software archaeologist"). 
 
 The "git-whatchanged" script is a truly trivial script that can give you
 a good overview of what has changed in a file or a directory (or an
@@ -187,7 +187,8 @@ you would use git-rev-list and git-diff-tree like this:
 
 We have already talked about the "\--stdin" form of git-diff-tree
 command that reads the list of commits and compares each commit
-with its parents.  The git-whatchanged command internally runs
+with its parents (otherwise you should go back and read the tutorial).
+The git-whatchanged command internally runs
 the equivalent of the above command, and can be used like this:
 
 	$ git-whatchanged -p -S'if (frotz) {