[Docs] Update to latest content on the wiki

docs/cr_user_manual.md

 # Cr
 
-Cr is the new unified interface to the myriad tools we use while working within
-a chromium checkout. Its main additional feature is that it allows you to build
-many configurations and run targets within a single checkout (by not relying on
-a directory called 'out'). This is especially important when you want to
-cross-compile (for instance, building android from linux or building arm from
+Cr is a tool that tries to hide some of the tools used for working on Chromium
+behind an abstraction layer. Nothing that cr does can't be done manually, but cr
+attempts to make things nicer. Its main additional feature is that it allows you
+to build many configurations and run targets within a single checkout (by not
+relying on a directory called 'out'). This is especially important when you want
+to cross-compile (for instance, building android from linux or building arm from
 intel), but it extends to any build variation.
 
 [TOC]
 
 ## A quick example
 
 The following is all you need to prepare an output directory, and then build and
 run the release build of chrome for the host platform:
 
 ```shell
@@ skipping 190 matching lines @@
     to infer from the target whether it is a runnable binary or a test. The
     inference could be improved, and it needs to handle the other test types as
     well.
 *   **No support for windows or mac** : allowed for in the design, but need
     people with expertise on those platforms to help out
 *   **Bash completion** : The hooks for it are there, but at the moment it only
     ever completes the command, not any of the arguments
 
 [Report a bug]:
 https://code.google.com/p/chromium/issues/entry?comment=%3CDont%20forget%20to%20attach%20the%20command%20lines%20used%20with%20-v=4%20if%20possible%3E&pri=2&labels=OS-Android,tool-cr,Build-Tools,Type-Bug&owner=iancottrell@chromium.org&status=Assigned