anchor.diff:  
   :marked
     Now when we visit `http://localhost:3000`, the `/heroes` route will load in the foreground, while the *CrisisCenterModule* and any other asynchronous feature
  -  modules we could have are _eagerly_ loaded in the background, waiting for us to navigate to them.
  +  modules are _eagerly_ loaded in the background, waiting for us to navigate to them.
   
   <a id="custom-preloading"></a>
   :marked
  
positive.code:   The *Router* also supports [custom preloading strategies](#custom-preloading) to give us control of what we want to pre-load.
  
    We'll update our *CrisisCenterModule* to be loaded lazily by default and use the `PreloadAllModules` strategy to eagerly
    it them up initial navigation.
  
  <a id="preload-canload"></a>
  .l-sub-section
  
negative.code:   We can define our own strategy the same way the **PreloadAllModules** modules strategy was provided to our *RouterModule.forRoot* configuration object.
  
    Since we want to take advantage of this, we'll add a custom strategy that _only_ preloads the modules we select. We'll enable the preloading by using the *Route Data*,
    which, as we learned, is an object to store arbitrary route data and and [resolve data](#resolve-guard).
  
    We'll add a custom `preload` boolean to our `crisis-center` route data that we'll use with our custom strategy. To see it in action, we'll add 
    the `route.path` to the `preloadedModules` array in our custom strategy service. We'll also log a message
    to the console for the preloaded module.
  
  