anchor.diff:    
     When we wrote ...
     ```
  -  import {bootstrap} from 'angular2/angular2';
  +  import {bootstrap} from 'angular2/platform/browser';
     
     bootstrap(AppComponent, [HeroService]);
     ```
     ... Angular translated that statement into a mapping instruction involving the Angular `provide` method
     ```
  -  import {bootstrap, provide} from 'angular2/angular2';
  +  import {bootstrap, provide} from 'angular2/platform/browser';
     
     bootstrap(AppComponent, [
       provide(HeroService, {useClass:HeroService})
  
positive.code:   We don't have a gigantic factory class to maintain.
    Both `Car` and consumer simply ask for what they need and the `Injector` delivers.
  
    This is what a **Dependency InjectionFramework** is all about. 
  
    Now that we know what Dependency Injection is and appreciate its benefits, 
    let's see how it is implemented in Angular.
  
negative.code:   That's not going to work. There is no type called `config` and we didn't register the `config` object under that name anyway.
    We'll need a little help from another Angular decorator called `@Inject`.
    ```
    import {Inject} from 'angular2/core'
    
    constructor(heroService: HeroService, @Inject('app.config') config)
    
  