anchor.diff:    We need to represent that variable part of the route with a *parameter* (or *token*) that stands for the hero's `id`.
   
     URL中的`/detail/`部分是固定不变的，但结尾的数字`id`部分会随着英雄的不同而变化。
  -  我们要把路由中可变的那部分表示成一个*参数(parameter)*或*Token*，用以获取英雄的`id`。
  +  我们要把路由中可变的那部分表示成一个*参数（parameter）*或*符号（token）*，代表英雄的`id`。
   
     ### Configure a Route with a Parameter
   
  
positive.code:   Recall earlier in the chapter that we removed the `HeroService` from the `providers` !{_array} of `HeroesComponent`
    and added it to the `providers` !{_array} of `!{_AppModuleVsAppComp}`.
  
    回忆一下，在前面的章节中，我们从`HeroesComponent`的`providers`数组中移除了`HeroService`服务，并把它添加到顶级组件`!{_AppModuleVsAppComp}`的`providers`数组中。
  
    That move created a singleton `HeroService` instance, available to *all* components of the application.
    Angular will inject `HeroService` and we'll use it here in the `DashboardComponent`.
  
    这个改动创建了一个`HeroService`的单例对象，它对应用中的*所有*组件都有效。
    在`DashboardComponent`组件中，Angular会把`HeroService`注入进来，我们就能在`DashboardComponent`中使用它了。
  
    ### Get heroes
  
    ### 获取英雄数组
  
    Open <span ngio-ex>dashboard.component.ts</span> and add the requisite `import` statements.
  
  
negative.code: :marked
    Our goal is to move the detail to its own view and navigate to it when the user decides to edit a selected hero.
  
    我们要做的是将详情建移动到它自己的视图，并在用户决定编辑一个英雄时导航到它。
  
    Delete the `<h1>` at the top (we forgot about it during the `AppComponent`-to-`HeroesComponent` conversion).
    
    删除顶部的`<h1>`（在从`AppComponent`转到`HeroesComponent`时忘记改它了）。
    
    Delete the last line of the template with the `<my-hero-detail>` tags.
  
  