anchor.diff:  .l-main-section  
   :marked
     ## Navigate to Hero Details
  +  
     ## 导航到英雄详情
   
     Although we display the details of a selected hero at the bottom of the `HeroesComponent`,
     we don't yet *navigate* to the `HeroDetailComponent` in the three ways specified in our requirements:
     
     虽然我们在`HeroesComponent`组件的底部显示了所选英雄的详情，但我们还从没有*导航*到`HeroDetailComponent`组件过 —— 我们曾在需求中指定过三种：
  +  
     1. from the *Dashboard* to a selected hero.
  +  
     1. 从*仪表盘(Dashboard)*导航到一个选定的英雄。
  +  
     1. from the *Heroes* list to a selected hero.
  +  
     1. 从*英雄列表(Heroes)*导航到一个选定的英雄。
  +  
     1. from a "deep link" URL pasted into the browser address bar.
  +  
     1. 把一个指向该英雄的“深链接”URL粘贴到浏览器的地址栏。
     
     Adding a `'HeroDetail'` route seem an obvious place to start.
  
positive.code:     回到`HeroesComponent`，并从`providers`数组中**移除`HeroService`**。
      我们要把它从`HeroesComponent`*提升*到`AppComponent`中。
      我们可不希望在应用的两个不同层次上存在它的***两个副本***。
  :marked
    The app still runs and still displays heroes. 
    Our refactoring of `AppComponent` into a new `AppComponent` and a `HeroesComponent` worked!
  
negative.code: 
  :marked
    ## Create *AppComponent*
    
    ## 创建*AppComponent*
    
    The new `AppComponent` will be the application shell. 
    It will have some navigation links at the top and a display area below for the pages we navigate to.
    
  