# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1240987154 -7200
# Node ID ea1289ecb35eddff1414731bb5815840ee8bc7f5
# Parent  0bee8982f334fb67c97415dd15020120f21ff3c0
learning in workflows: intro fixed.

diff -r 0bee8982f334 -r ea1289ecb35e text/learning_mercurial_in_workflows.txt
--- a/text/learning_mercurial_in_workflows.txt	Tue Apr 28 23:21:15 2009 +0200
+++ b/text/learning_mercurial_in_workflows.txt	Wed Apr 29 08:39:14 2009 +0200
@@ -2,25 +2,7 @@
 
 With Mercurial you can use a multitude of different workflows. This page shows some of them, including their use cases. 
 
-It is intended to make it easier for you to create your own workflow. 
-
-To write this page we gathered [real life workflows](wiki - workflows), so every more complex workflow in here has proven itself in real life usage. We begin with basic workflows and then go on to more complex examples. 
-
-<!--Structure: 
-* For whom? -> Why?
-* What do you need? -> Resources + extensions
-* Single Developer workflow
-* Sharing changes. -->
-
-<!-- Plan
-
-* Simple workflows without extensions
-
-* Complex Workflows, including collaborative patch development and similar. 
-
-* Smoothing workflows with extensions -> i.e. shelve before merging. 
-
--->
+It is intended to make it easy for Beginners of Version tracking to get going instantly and learn completely incrementally. 
 
 = Basic workflows =