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've learned how to load modules on-demand, but we can also take advantage of loading feature areas modules in *advance*. The *Router*
    supports **pre-loading** of asynchronous feature areas prior to navigation to their respective URL. Pre-loading allows us to to load our initial route
    quickly, while other feature modules are loaded in the background. Once we navigate to those areas, they will have already been loaded
    as if they were included in our initial bundle.
  
    Each time a **successful** navigation happens, the *Router* will look through our configuration for lazy loaded feature areas
    and react based on the provided strategy.
  