anchor.diff:  :marked
     ### Configuration
     When the browser's URL changes, the router looks for a corresponding **`RouteDefinition`**
  -  from which it can determine the Component to display.
  +  from which it can determine the component to display.
   
     A new router has no route definitions. We have to configure it.
     The preferred way to configure the router is with a **`@RouteConfig`** [decorator](glossary.html#decorator)
  
positive.code:   Each definition translates to a [Route](https://angular.io/docs/ts/latest/api/router/Route-class.html) which has a
    * `path` - the URL path segment for this route
    * `name` - the name of the route
    * `component` - the Component associated with this route.
  
    The router draws upon its registry of route definition when
    1. the browser URL changes
  
negative.code: .l-sub-section
    :marked
      There are several flavors of `RouteDefinition`.
      The most common by far is the named **`Route`** which maps a URL path to a component
  
      The `name` field is the name of the `Route`. The name **must** be spelled in **PascalCase**.
  
  