anchor.diff:    The view still renders but the displayed value is blank; we see only "`The title is`" with nothing after it.
     That is reasonable behavior. At least the app doesn't crash.
   
  -  Suppose the template expression involves a property path as in this next example 
  +  Suppose the template expression involves a property path as in this next example
     where we’re displaying the `firstName` of a null hero.
   
   code-example(format="" language="html").
  
positive.code:       +makeExample('template-syntax/ts/app/app.component.html', 'style-binding-syntax-1')(format=".")
  </div>
  
  .l-sub-section
    :marked
      According to this rule, we should write `[inner-h-t-m-l]` to access the element’s `innerHTML` property.
      Fortunately, the Angular template parser recognizes `inner-html` as an acceptable alias for `innerHTML`.
  :marked
    Let’s descend from the architectural clouds and look at each of these binding types in concrete detail.
  
  
negative.code:   The (#) prefix character in front of "hero" means that we're defining a `hero` variable.
  .l-sub-section
    :marked
      Some folks don't like the (#) character.
      The `var-` prefix is the  “cannonical” alternative to "#". We could have declared our variable as `var-hero`.
  :marked
    We defined `hero` on the outer `<template>` element where it becomes the current hero item
    as Angular iterates through the list of heroes.
  
    The `hero` variable appears again in the binding on the inner `<hero-detail>` component element.
    That's how each instance of the `<hero-detail>` gets its hero.
  
    ### Referencing a local template variable
  
    We can reference a local template variable on the same element, on a sibling element, or on
    any of its child elements.
  
  