Update mojo_run to use mojo:launcher instead of mojo:kiosk_wm.

README.md

 Mojo
 ====
 
 Mojo is a collection of interprocess communication technologies, protocols
 and a runtime for creating applications and services that are composable while
 being loosely coupled. It simplifies the creation of fully asynchronous
 component-based systems and provides guarantees so that components made by
 different vendors and in different programming languages can interoperate.
 
 
@@ skipping 179 matching lines @@
 
 Some applications can be run directly from the source tree. The development
 server serves the `src` directory, allowing to refer to these apps. For
 instance, this command serves a dart Mojo app from the source at
 `examples/dart/device_info/main.dart`:
 
 ```sh
 mojo/devtools/common/mojo_run https://core.mojoapps.io/examples/dart/device_info/lib/main.dart [--android]
 ```
 
-Some applications are meant to be run embedded in a **window manager**. To run
-these, you can pass the app url using the `--embed` flag. This will run the
-window manager and pass the given url to it:
+Some applications implement ViewProvider and are run embedded in a view. To run
+these, you can pass the app url using the `--embed` flag:
 
 ```sh
-mojo/devtools/common/mojo_run --embed https://core.mojoapps.io/ganesh_app.mojo [--android]
+mojo/devtools/common/mojo_run --embed mojo:moterm_example_app [--android]
 ```
 
-By default, `mojo_run` uses mojo:kiosk_wm as the window
-manager. You can pass a different window manager url using the
-`--window-manager` flag to override this.
+which is a shorthand for:
+
+```sh
+mojo/devtools/common/mojo_run "mojo:launcher mojo:moterm_example_app"
+```
 
 For additional information on `mojo_run` refer to the built-in help and the
 [documentation](mojo/devtools/common/docs/mojo_run.md).
 You can also request more information on what the tool is doing for you by
 passing the `--verbose` flag.
 
 ### <a name="debugging"></a>Debugging, tracing, profiling
 
 Devtools `mojo_debug` allows you to interactively inspect a running shell,
 collect performance traces and attach a gdb debugger.
@@ skipping 93 matching lines @@
 
 Automated alerts about performance regressions are sent to
 [mojo-perf-alerts@chromium.org](https://groups.google.com/a/chromium.org/forum/#!forum/mojo-perf-alerts).
 
 For examples of interesting sets of graphs see:
 
  - [app
    startup](https://chromeperf.appspot.com/report?sid=4848464df5ca8467770d80b309740ef56fbff00e773c2c53816fd8bff1fda1e0)
  - [ipc
    performance](https://chromeperf.appspot.com/report?sid=9abc20b46f6f8d908b0f07847f1d42eab54c7025a098336e6dc2d3e2030d66f8)