| Index: examples/js/users-guide.md
|
| diff --git a/examples/js/users-guide.md b/examples/js/users-guide.md
|
| index 52ee2b379394d87bf7457ff08093abd2c42cae23..33065bc359845058830800787e85fca28b8c0015 100644
|
| --- a/examples/js/users-guide.md
|
| +++ b/examples/js/users-guide.md
|
| @@ -13,7 +13,7 @@ content handler. In other words, the first line of the JS source file
|
| must be:
|
|
|
| ```javascript
|
| -#!mojo:js_content_handler
|
| +#!mojo mojo:js_content_handler
|
| ```
|
|
|
| Following the shebang should be a single AMD module called "main" whose value
|
| @@ -39,7 +39,7 @@ services of its own.
|
| This is the overall structure of a JS Mojo application:
|
|
|
| ```javascript
|
| -#!mojo:js_content_handler
|
| +#!mojo mojo:js_content_handler
|
|
|
| define("main", ["mojo/services/public/js/application",
|
| <list of other modules that this application depends on>
|
| @@ -430,7 +430,7 @@ can use the application's shell to get an EchoService proxy. Here's a
|
| complete application:
|
|
|
| ```javascript
|
| -#!mojo:js_content_handler
|
| +#!mojo mojo:js_content_handler
|
|
|
| define("main", [
|
| "console",
|
| @@ -467,7 +467,7 @@ A complete application that unconditionally provides the EchoService
|
| looks like this:
|
|
|
| ```javascript
|
| -#!mojo:js_content_handler
|
| +#!mojo mojo:js_content_handler
|
|
|
| define("main", [
|
| "mojo/services/public/js/application",
|
|
|