anchor.diff:    &lt;title&gt;{{This_Does_Not_Work}}&lt;/title&gt;
   :marked
     Sorry but that won't work.
  -  The root component of our application is an element contained within the `<body>` tag.
  +  The root component of the application is an element contained within the `<body>` tag.
     The HTML `<title>` is in the document `<head>`, outside the body, making it inaccessible to Angular data binding.
   
  -  We could grab the browser `document` object and set the title manually.
  -  That's dirty and undermines our chances of running the app outside of a browser someday.
  +  You could grab the browser `document` object and set the title manually.
  +  That's dirty and undermines your chances of running the app outside of a browser someday.
   .l-sub-section
     :marked
       Running your app outside a browser means that you can take advantage of server-side
  
positive.code: 
  .l-main-section
  :marked
    ## Why we provide the *Title* service in *bootstrap*
  
    We generally recommended providing application-wide services in the root application component, `AppComponent`.
  
    Here we recommend registering the title service during bootstrapping,
    a location we reserve for configuring the runtime Angular environment.
  
    That's exactly what we're doing.
    The `Title` service is part of the Angular *browser platform*.
    If we bootstrap our application into a different platform,
    we'll have to provide a different `Title` service that understands the concept of a "document title" for that specific platform.
    Ideally the application itself neither knows nor cares about the runtime environment.
  :marked
    [Back to top](#top)
  
negative.code: 
  a(id='top')
  :marked
    Your app should be able to make the browser title bar say whatever you want it to say.
    This cookbook explains how to do it.
  :marked
    See the <live-example name="cb-set-document-title"></live-example>.
  
  table
    tr
  