Lots of documentation cleanup

docs/UserDocumentation.md

-# GYP (Generate Your Projects) User Documentation
+# User Documentation
 
-Status: Draft (as of 2009-05-19)
-
-Mark Mentovai <mark@chromium.org>,
-Steven Knight <sgk@chromium.org>
-_et al._
-
-Modified: 2009-05-19
-
 [TOC]
 
 ## Introduction
 
 This document is intended to provide a user-level guide to GYP.  The
 emphasis here is on how to use GYP to accomplish specific tasks, not on
 the complete technical language specification.  (For that, see the
 [LanguageSpecification](LanguageSpecification).)
 
 The document below starts with some overviews to provide context: an
@@ skipping 418 matching lines @@
 
 The above two examples end up generating equivalent builds, with the
 small exception that the `sources` lists will list the files in
 different orders.  (The first example defines explicitly where
 `linux_specific.cc` appears in the list--perhaps in in the
 middle--whereas the second example will always tack it on to the end of
 the list.)
 
 **Including or excluding files using patterns**: There are more
 complicated ways to construct a `sources` list based on patterns.  See
-`TODO(sgk)` below.
+`TODO` below.
 
 ### Add a new executable
 
 An executable program is probably the most straightforward type of
 target, since all it typically needs is a list of source files, some
 compiler/linker settings (probably varied by platform), and some library
 targets on which it depends and which must be used in the final link.
 
 #### Add an executable that builds on all platforms
 
@@ skipping 489 matching lines @@
 setting `product_extension` if you want. Files listed in
 `mac_bundle_resources` will be copied to the bundle's `Resource` folder
 of the bundle. You can also set
 `process_outputs_as_mac_bundle_resources` to 1 in actions and rules to
 let the output of actions and rules be added to that folder (similar to
 `process_outputs_as_sources`). If `product_name` is not set, the bundle
 will be named after `target_name`as usual.
 
 ### Move files (refactoring)
 
-TODO(sgk)
+TODO
 
 ### Custom build steps
 
-TODO(sgk)
+TODO
 
 #### Adding an explicit build step to generate specific files
 
-TODO(sgk)
+TODO
 
 #### Adding a rule to handle files with a new suffix
 
-TODO(sgk)
+TODO
 
 ### Build flavors
 
-TODO(sgk)
+TODO