 
             HTML({lang: "en"},
               HEAD(
-                TITLE("Simple domo example"),
+                TITLE("Simple dōmo example"),
                 STYLE({type: "text/css"},
                   CSS("body", {textAlign: "center", fontSize: 100}),
                   CSS("h1", opacity(50), {background: "#000", color: "#fff"})

    H3 "Example"

    P {},
      "The following is a simple, self-contained example using domo in the browser. "
      "It replaces the existing documentElement with a DOM tree, using a simple function as a CSS mixin."

    DIV class: "sub",

          <\/script>
        """

    H3 "Why dōmo?"

    UL class: "why-dōmo",
      LI B "Reduce your exposure to XSS attacks. "
      "Writing straight from JavaScript to DOM without an HTML step means you don't need to rely on a library to sanitize your rendered data because the browser does it for you automatically."

      LI B "Eliminate a separate compile step. "
      "With dōmo, 'compilation' is done in the same JavaScript process as your code, which means that any syntax errors are thrown with line numbers in the same JavaScript process."

      LI B "Don't let implementations drive architectural decisions. "
      "If you're writing a view that renders a DOM node, you can write it directly within the rendering code for convenience, and then pull it out into its own file when the size of your app requires it."

      LI B "Use JavaScript syntax everywhere. "
      "Instead of remembering which HAML or LESS symbols map to which behaviors, like looping or escaping or conditionals or negation, just use JavaScript."

      LI B "Decouple your syntax sugar. "
      "Instead of choosing a template engine or CSS compiler with the ideal syntax, just use JavaScript, and do your sweetening on a more reliable level. CoffeeScript can go a long way in making DOM building code look like HAML, for example."
