anchor.diff:  :marked
     The key is to make the code more reusable, easier to read, and less mistake prone.
   
  -  The following *negative* example defines the `AppComponent`, bootstraps the app, defines the `Hero` model object, and loads heroes from the server ... all in the same file. *Don't do this*.
  +  The following *negative* example defines the `AppComponent`, bootstraps the app, 
  +  defines the `Hero` model object, and loads heroes from the server all in the same file. 
  +  *Don't do this*.
   
   +makeExample('style-guide/ts/src/01-01/app/heroes/hero.component.avoid.ts', '', 'app/heroes/hero.component.ts')(avoid=1)
   :marked
  
positive.code: 
  .s-rule.do
    :marked
      **Do** use the `@Injectable` class decorator instead of the `@Inject` parameter decorator when using types as tokens for the dependencies of a service.
  
  .s-why
    :marked
  
negative.code: .s-rule.avoid
    :marked
      **Avoid** indicates something you should almost never do. Code examples to *avoid* have an unmistakeable red header.
  
  .s-why
    :marked
      **Why?** gives reasons for following the previous recommendations.
  
  .l-main-section
  
  :marked
  