The `application` template is the default template that is rendered when
your application starts. 

You should put your header, footer, and any other decorative content
here. Additionally, you should have at least one `{{outlet}}`:
a placeholder that the router will fill in with the appropriate template,
based on the current URL.

Here's an example template:

```handlebars
<header>
  <h1>Igor's Blog</h1>
</header>

<div>
  {{outlet}}
</div>

<footer>
  &copy;2013 Igor's Publishing, Inc.
</footer>
```

The header and footer will always be displayed on screen, but the
contents of the `<div>` will change depending on if the user is
currently at `/posts` or `/posts/15`, for example.

For more information about how outlets are filled in by the router, see
[Routing](/guides/routing).

If you are keeping your templates in HTML, create a `<script>` tag
without a template name. Ember will use the template without a name as the application template and it will automatically be compiled and appended
to the screen.

```handlebars
<script type="text/x-handlebars">
  <div>
    {{outlet}}
  </div>
</script>
```

If you're using build tools to load your templates, make sure you name
the template `application`.

The `application` template is the default template that is rendered when
your application starts. 

You should put your header, footer, and any other decorative content
here. Additionally, you should have at least one `{{outlet}}`:
a placeholder that the router will fill in with the appropriate template,
based on the current URL.

Here's an example template:

```handlebars
<header>
  <h1>Igor's Blog</h1>
</header>

<div>
  {{outlet}}
</div>

<footer>
  &copy;2013 Igor's Publishing, Inc.
</footer>
```

The header and footer will always be displayed on screen, but the
contents of the `<div>` will change depending on if the user is
currently at `/posts` or `/posts/15`, for example.

For more information about how outlets are filled in by the router, see
[Routing](/guides/routing).

If you are keeping your templates in HTML, create a `<script>` tag
without a template name. Ember will use the template without a name as the application template and it will automatically be compiled and appended
to the screen.

```html
<script type="text/x-handlebars">
  <div>
    {{outlet}}
  </div>
</script>
```

If you're using build tools to load your templates, make sure you name
the template `application`.

Revert "fix html->handlebars indicator in handlebars guide"
Revert "fix html->handlebars indicator in handlebars guide"

The guide was actually previously correct as it was documenting doing
handlebars templates with script tags in HTML.

This reverts commit 3f221b47920575766aef19f7dd5a2bd1e9016994.
