# HG changeset patch
# User Bryan O'Sullivan <bos@serpentine.com>
# Date 1167155952 28800
# Node ID f954c6f6eaa1bc01ceaa366353573406faf3dc8d
# Parent  3af28630fe8c97bb74942c91de80f6366099d868
Progress.

diff -r 3af28630fe8c -r f954c6f6eaa1 en/examples/daily.revert
--- a/en/examples/daily.revert	Wed Nov 15 16:57:29 2006 -0800
+++ b/en/examples/daily.revert	Tue Dec 26 09:59:12 2006 -0800
@@ -70,6 +70,5 @@
 hg status
 
 #$ name: rename-orig
-
 hg revert file
 hg status
diff -r 3af28630fe8c -r f954c6f6eaa1 en/undo.tex
--- a/en/undo.tex	Wed Nov 15 16:57:29 2006 -0800
+++ b/en/undo.tex	Tue Dec 26 09:59:12 2006 -0800
@@ -154,7 +154,9 @@
 \interaction{daily.revert.missing}
 
 If you revert a \hgcmd{copy}, the copied-to file remains in your
-working directory afterwards, unmodified.
+working directory afterwards, untracked.  Since a copy doesn't affect
+the copied-from file in any way, Mercurial doesn't do anything with
+the copied-from file.
 \interaction{daily.revert.copy}
 
 \subsubsection{A slightly special case: reverting a rename}
@@ -178,7 +180,7 @@
 If you need the modifications in the renamed-to file to show up in the
 renamed-from file, don't forget to copy them over.)
 
-These fiddly aspects of reverting a rename arguably consitute a small
+These fiddly aspects of reverting a rename arguably constitute a small
 bug in Mercurial.
 
 %%% Local Variables: