Don't emulate Sky server when --sky is passed.

README.md

 Mojo
 ====
 
 Mojo is an effort to extract a common platform out of Chrome's renderer and
 plugin processes that can support multiple types of sandboxed content, such as
 HTML, Pepper, or NaCl.
 
 ## Set-up and code check-out
 
 The instructions below only need to be done once. Note that a simple "git clone"
@@ skipping 194 matching lines @@
 Because the dart analyzer is a bit slow, we don't run it unless the user
 specifically asks for it. To run the dart analyzer against the list of dart
 targets in the toplevel BUILD.gn file, run:
 
 ```
 $ mojo/tools/mojob.py dartcheck
 ```
 
 ## Run Mojo Shell
 
-Devtools script `mojo_run` is a universal shell runner abstracting away the
-differences between running on Linux and Android. Having built Mojo as
-described above, a demo app can be run as follows:
+Devtools `mojo_run` is a universal shell runner abstracting away the differences
+between running on Linux and Android. Having built Mojo as described above, a
+demo app can be run as follows:
 
 ```
 mojo/devtools/common/mojo_run mojo:spinning_cube  # Linux.
 mojo/devtools/common/mojo_run mojo:spinning_cube  --android # Android.
 ```
 
-Pass `--sky path_to_sky_file` to run a
-[Sky](https://github.com/domokit/mojo/tree/master/sky) app on either platform:
-```
-mojo/devtools/common/mojo_run --sky sky/examples/raw/hello_world.dart
-mojo/devtools/common/mojo_run --sky sky/examples/raw/hello_world.dart --android
-```
-
 Passing the `-v` flag will increase the output verbosity. In particular, it will
 also print all arguments passed by `mojo_run` to the shell binary.
 
-### Chromoting
-
-Some Mojo apps (Sky apps in particular) will need the --use-osmesa flag to run
-over [chromoting](https://support.google.com/chrome/answer/1649523?hl=en):
-
-```
-mojo/devtools/common/mojo_run --sky sky/examples/raw/hello_world.dart --use-osmesa
-```
+For additional information refer to the built-in help and the
+[documentation](https://github.com/domokit/devtools/blob/master/README.md#runner).
 
 ### <a name="debugging"></a>Debugging, tracing, profiling
 
-Devtools `mojo_debug` script allows you to interactively inspect a running
-shell, collect performance traces and attach a gdb debugger. Refer to the
-[documentation](https://github.com/domokit/devtools/blob/master/README.md#debugger)
-for details.
+Devtools `mojo_debug` allows you to interactively inspect a running shell,
+collect performance traces and attach a gdb debugger.
+
+For additional information refer to the built-in help and the
+[documentation](https://github.com/domokit/devtools/blob/master/README.md#debugger).
 
 ### Android set-up
 
 #### Adb
 
 For the Android tooling to work, you will need to have `adb` in your PATH. For
 that, you can either run:
 ```
 source build/android/envsetup.sh
 ```
@@ skipping 13 matching lines @@
 running shell on the device) will not work unless the device is rooted and
 running a userdebug build. For Googlers, [follow the instructions at this
 link](http://go/mojo-internal-build-instructions).
 
 ### Running manually on Linux
 
 If you wish to, you can also run the Linux Mojo shell directly with no wrappers:
 ```
 ./out/Debug/mojo_shell mojo:spinning_cube
 ```