Fix docs

help/markdown/core-commandlineparsing.md

@@ -1,6 +1,6 @@
 # Fake.Core.CommandLineParsing
 
-This module is a re-implementation from https://github.com/docopt/docopt.fs/ but with strong ordering.
+This module is a fork from https://github.com/docopt/docopt.fs/ but with strong ordering.
 The strong ordering enables you to have a nice CLI on your script or to write your own fake 5 modules with a CLI.
 
 Example `script.fsx`:
@@ -22,7 +22,7 @@ options:
 """
 
 // retrieve the fake 5 context information
-let ctx = Fake.Core.Context.forceFakeContext ()
+let ctx = Context.forceFakeContext ()
 // get the arguments
 let args = ctx.Arguments
 let parser = Docopt(cli)
@@ -36,6 +36,17 @@ match DocoptResult.tryGetArgument "-m" results with
 | Some arg -> printfn "%s" arg
 ```
 
+A more sophisticated example can be in the fake runner: https://github.com/fsharp/FAKE/blob/64d871f5065412fe7b233025e454ccf3b89e46d7/src/app/Fake.netcore/Program.fs#L204-L259
+
+Or the target module:
+
+- https://github.com/fsharp/FAKE/blob/rc_1/src/app/Fake.Core.Target/Target.fs#L9-L26
+- https://github.com/fsharp/FAKE/blob/64d871f5065412fe7b233025e454ccf3b89e46d7/src/app/Fake.Core.Target/Target.fs#L564-L619
+
+You can also take a look at the test-suite:
+
+- https://github.com/fsharp/FAKE/blob/rc_1/src/test/Fake.Core.CommandLine.UnitTests/Fake.Core.CommandLine.fs
+
 ## Differences to the python reference Docopt implementation
 
 - The parser doesn't differentiate between arguments with and without `-` with regards to ordering. They are subject to the same rules as other arguments. The only exception is when defining multiple arguments like `[-a -b -c]`, then the ordering of the group doesn't matter.

help/markdown/fake-commandline.md

@@ -41,8 +41,8 @@ Ordering of arguments does MATTER. This is a change in behavior from FAKE versio
 
 Examples:
 
-- `fake run -v build.fsx` - This will not run fake in verbose mode. Instead it will try to run the script named `-v`.
-- `fake --fsiargs "--define:BOOTSTRAP" build.fsx` - This will not run `build.fsx` and define BOOTSTRAP, because `--fsiargs` needs to follow after the script-name
+- `fake run -v build.fsx` - This will not run fake in verbose mode. Instead it will try to run the script named `-v`. (But we might support that in the future)
+- `fake build.fsx --fsiargs "--define:BOOTSTRAP"` - This will not run `build.fsx` and define BOOTSTRAP, because `--fsiargs` needs to be before the script-name.
 - `fake build -s` - This will run fake in single-target mode and not in silent mode, you need to use `fake -s build` as described in the above usage description.
 
 ## `--verbose [-v]`