Updating blimp_shell doc

blimp/docs/running.md

 # Running Blimp
 [TOC]
 
 See [build](build.md) for instructions on how to build Blimp.
 
 ## Android Client
 
 ### Installing the client
 
 Install the Chrome Public APK with the following:
@@ skipping 134 matching lines @@
 * Some of scripts under `build/android` will fail to run as it uses `adb scp`.
   Follow the instruction above to use `adb` directly.
 
 * To connect to an Engine running on the host machine, you should use
   `10.0.2.2` as `engine-ip` instead of `127.0.0.1` as `127.0.0.1` will refer to
   the emulator itself. There is no need of set up
   [port forwarding](#Port-forwarding) when this approach is used.
 
 ## Linux Client
 
-The Linux client is used for development purpose while the Android client is
-shipped. The Linux client is built as part of the `blimp` target.
+The Linux client is useful for development purposes where the full Android UI
+is not required.
+
+Build with the following commands:
+```
+mkdir -p out-linux/Client

[Wez, 2016/09/16 00:48:53]

nit: Looks like gn gen will take care of this :)

+
+gn gen out-linux/Client
+ninja -C out-linux/Client blimp_shell
+```
+
+
 To run it with local logging enabled, execute:
 
 ```bash
-./out-linux/Debug/blimp_shell \
+./out-linux/Client/blimp_shell \
   --user-data-dir=/tmp/blimpclient \
   --enable-logging=stderr \
-  --vmodule="*=1"
+  --vmodule="*=1" \
+  --engine-ip=127.0.0.1 \
+  --engine-port=25467 \
+  --engine-transport=tcp \
+  --blimp-client-token-path=/tmp/blimpengine-token
+```
+
+**PS:** Create the `/tmp/blimpengine-token` file with any amount of characters.
+For example:
+
+```
+echo "anything" > /tmp/blimpengine-token
 ```
 
 ## Running the engine
 
 ### In a container
 For running the engine in a container, see [container](container.md).
 
 ### On a workstation
 The following flags are required to start an Engine instance:
 
@@ skipping 81 matching lines @@
     killing engine if keyboard interrupts or client gets killed.
 
     ```bash
     out-linux/Debug/bin/client_engine_integration run
     ```
 
 2.  Same as step 2 in Option A.
 
 3.  Engine should be auto-killed by keyboard stopping the `{run}` script or the client
     gets wiped out. `{stop}` works as well.