# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1242109985 -7200
# Node ID 08f4b19d865eccc084ea6fc7dca6724d7733cc58
# Parent  53e4007ac24fd278d18ee7a4dbf9a8dd9aea922a
learning in workflows: Lone Dev: example reason for going back: fix the bug where it occurred.

diff -r 53e4007ac24f -r 08f4b19d865e hgscm/templates/workflow_guide.html
--- a/hgscm/templates/workflow_guide.html	Tue May 12 08:30:24 2009 +0200
+++ b/hgscm/templates/workflow_guide.html	Tue May 12 08:33:05 2009 +0200
@@ -129,7 +129,7 @@
 
 <h5>Seeing an earlier revision</h5>
 
-Different from the log keeping workflow, you'll want to go back in history at times and undo some changes, for example because it introduced a bug. 
+Different from the log keeping workflow, you'll want to go back in history at times and do some changes directly there, for example because an earlier change introduced a bug and you want to fix it where it occurred. 
 
 To look at a previous version of your code, you can use update. Let's assume that you want to see revision 3.