Move walkthrough to end of tutorial, add real TL;DR section.

docs/src/depot_tools_tutorial.txt

 depot_tools_tutorial(7)
 =======================
 
 NAME
 ----
 depot_tools_tutorial - A tutorial introduction to the Chromium depot_tools git
 extensions.
 
 DESCRIPTION
 -----------
 
 The Chromium linkgit:depot_tools[7] suite contains many git workflow-enhancing
 tools which are designed to work together to enable anyone to wrangle the
 Chromium codebase expertly. This tutorial explains how to do development on
 Chromium using these tools. This will cover:
 
 * <<_setting_up,Setting up>>
 * <<_getting_the_code,Getting the code>>
-* <<_tl_dr_walkthrough,TL;DR Walkthrough>>
+* <<_tl_dr,TL;DR>>
 * <<_creating_uploading_a_cl,Creating / Uploading a CL>>
 * <<_updating_the_code,Updating the code>>
 * <<_managing_multiple_cls,Managing multiple CLs>>
 * <<_managing_dependent_cls,Managing dependent CLs>>
+* <<_example_walkthrough,Example Walkthrough>>
 
 Please refer to the manpages (or `--help` output) for details about any of the
 commands mentioned in this tutorial.
 
 [NOTE]
 If your platform does not support manpages (or you prefer something a bit more
 expressive than plain text) you can find all documentation in 'html' form in the
 `[DEPOT_TOOLS]/docs/html` folder.
 
 PREREQUISITES
@@ skipping 104 matching lines @@
 [subs="quotes,attributes"]
 ----
 [white]**$ git config --global user.name ``John Doe''**
 [white]**$ git config --global user.email ``jdoe@email.com''**
 [white]**$ git config --global core.autocrlf false**
 [white]**$ git config --global core.filemode false**
 [white]**$** # and for fun!
 [white]**$ git config --global color.ui true**
 ----
 
+TL;DR
+-----
+[postsubs="quotes"]
+----
+[white]**$** # get the code
+[white]**$** # In an empty directory:
+[white]**$ fetch {chromium,blink,...}**
+
+[white]**$** # Update third_party repos and run pre-compile hooks
+[white]**$ gclient sync**
+
+[white]**$** # Make a new change and upload it for review
+[white]**$ git new-branch branchname**
+[white]**$** # repeat: [edit, git add, git commit]
+[white]**$ git cl upload**
+
+[white]**$** # After change is reviewed, commit with the CQ
+[white]**$ git cl set_commit**
+[white]**$** # Note that the committed hash which lands will /not/ match the
+[white]**$** # commit hashes of your local branch.
+----
+
+
 GETTING THE CODE
 ----------------
 Pick an empty directory and run one of the following:
 
 [subs="quotes"]
 ----
 [white]**$ fetch chromium**  # Basic checkout for desktop Chromium
 [white]**$ fetch blink**     # Chromium code with Blink checked out to tip-of-tree
 [white]**$ fetch android**   # Chromium checkout for Android platform
 [white]**$ fetch ios**       # Chromium checkout for iOS platform
@@ skipping 12 matching lines @@
 
 [subs="specialcharacters,quotes"]
 ----
 [white]**$ cd src && ./build/install-build-deps.sh**
 ----
 
 And finally:
 
 [postsubs="quotes"]
 ----
-[white]**$ gclient sync** <1>
+[white]**$ gclient sync**
 ----
-<1> This will pull all dependencies of the Chromium src checkout. You will need
+
+This will pull all dependencies of the Chromium src checkout. You will need
 to run this any time you update the main src checkout.
 
 
-TL;DR WALKTHROUGH
------------------
-This section will demo what a typical workflow looks like when writing, updating,
-and committing multiple CLs.
-
-demo:tldr[]
-
-So there you have the basic flow. Note that you don't 'have' to do chromium
-development using these tools. Any git workflow is compatible, as long as
-`git cl upload` is able to upload good patches.
-
-
 CREATING / UPLOADING A CL
 -------------------------
 NOTE: The remainder of the tutorial assumes that your current working directory
 is the `src/` folder mentioned in <<_getting_the_code,Getting the code>>.
 
 Each CL corresponds exactly with a single branch in git. Any time you want to
 begin a new CL, just:
 
 [subs="specialcharacters,quotes"]
 ----
@@ skipping 164 matching lines @@
 Sometimes when dealing with dependent CLs, it turns out that you accidentally
 based a branch on the wrong upstream, but since then you've committed changes to
 it, or even based 'another' branch off of that one. Or you discover that you
 have two independent CLs that would actually be much better off as dependent
 CLs. In instances like these, you can check out the offending branch and use
 linkgit:git-reparent-branch[1] to move it to track a different parent. Note that
 this can also be used to move a branch from tracking `origin/master` to `lkgr`
 or vice versa.
 
 
+EXAMPLE WALKTHROUGH
+-------------------
+This section will demo what a typical workflow looks like when writing,
+updating, and committing multiple CLs.
+
+demo:walkthrough[]
+
+So there you have the basic flow. Note that you don't 'have' to do chromium
+development using these tools. Any git workflow is compatible, as long as
+`git cl upload` is able to upload good patches.
+
+
 CONCLUSION
 ----------
 Hopefully that gives you a good starting overview on Chromium development using
 'depot_tools'. If you have questions which weren't answered by this tutorial or
 the man pages for the tools (see the index of all tools here:
 linkgit:depot_tools[7]), please feel free to ask.
 
 
 GLOSSARY
 --------
 
 CL::
   A 'change-list'. This is a diff which you would like to commit to the
   codebase.
 
 DEPS::
   A file in the chromium checkout which `gclient sync` uses to determine what
   dependencies to pull in. This file also contains 'hooks'.
 
 LKGR::
   Last Known Good Revision. This is a linkgit:git-tag[1] which tracks the last
   version of `origin/master` which has passed the full set of testing on the
   link:http://build.chromium.org[main Chromium waterfall].
 
 include::_footer.txt[]
 
 // vim: ft=asciidoc: