anchor.diff:    could be rendered on the server and delivered to the user's device
     in less than a second.
   
  -  Thist option is only available if application URLs look like normal web URLs
  +  This option is only available if application URLs look like normal web URLs
     without hashes (#) in the middle.
   
     Stick with the default unless you have a compelling reason to
     resort to hash routes.
   
     ### HTML 5 URLs and the  *&lt;base href>*
  -  While the router use the "[HTML 5 pushState](https://developer.mozilla.org/en-US/docs/Web/API/History_API#Adding_and_modifying_history_entries)"
  +  While the router uses the "[HTML 5 pushState](https://developer.mozilla.org/en-US/docs/Web/API/History_API#Adding_and_modifying_history_entries)"
     style by default, we *must* configure that strategy with a **base href**
     
     The preferred way to configure the strategy is to add a
  
positive.code: figure.image-display
    img(src='/resources/images/devguide/router/hero-list.png' alt="Hero List" width="250")
  :marked
    We select one and the applications takes us to a hero editing screen.
  figure.image-display
    img(src='/resources/images/devguide/router/hero-detail.png' alt="Crisis Center Detail" width="250")
  :marked
    Our changes take affect immediately. We click the "Back" button and the
    app returns us to the Heroes list.
  
    We could have clicked the browser's back button instead.
  
negative.code:   We added a new route definition for the `HeroDetailComponent` &mdash; and this definition has a twist.
  +makeExample('router/ts/app/app.component.2.ts','hero-detail-route')(format=".")
  :marked
    Notice the `:id` token in the path. That creates a slot in the path for a **Route Parameter**.
    In this case, we're expecting the router to insert the `id` of a hero into that slot.
  
    If we tell the router to navigate to the detail component and display "Magneta", we expect hero `id` (15) to appear in the
  