diff --git a/public/docs/_examples/router/e2e-spec.ts b/public/docs/_examples/router/e2e-spec.ts
index bf672c3f01..a82ebd08a5 100644
--- a/public/docs/_examples/router/e2e-spec.ts
+++ b/public/docs/_examples/router/e2e-spec.ts
@@ -16,8 +16,8 @@ describe('Router', function () {
 
       crisisHref: hrefEles.get(0),
       crisisList: element.all(by.css('my-app > ng-component > ng-component li')),
-      crisisDetail: element(by.css('my-app > ng-component > ng-component > div')),
-      crisisDetailTitle: element(by.css('my-app > ng-component > ng-component > div > h3')),
+      crisisDetail: element(by.css('my-app > ng-component > ng-component > ng-component > div')),
+      crisisDetailTitle: element(by.css('my-app > ng-component > ng-component > ng-component > div > h3')),
 
       heroesHref: hrefEles.get(1),
       heroesList: element.all(by.css('my-app > ng-component li')),
@@ -34,7 +34,7 @@ describe('Router', function () {
     expect(page.hrefs.count()).toEqual(4, 'should be 4 dashboard choices');
     expect(page.crisisHref.getText()).toEqual('Crisis Center');
     expect(page.heroesHref.getText()).toEqual('Heroes');
-    expect(page.adminHref.getText()).toEqual('Crisis Admin');
+    expect(page.adminHref.getText()).toEqual('Admin');
     expect(page.loginHref.getText()).toEqual('Login');
   });
 
@@ -118,7 +118,6 @@ describe('Router', function () {
       crisisText = text.substr(text.indexOf(' ')).trim();
       return crisisEle.click();
     }).then(function () {
-      expect(page.crisisList.count()).toBe(0, 'should no longer see crisis center entries');
       expect(page.crisisDetail.isPresent()).toBe(true, 'should be able to see crisis detail');
       expect(page.crisisDetailTitle.getText()).toContain(crisisText);
       let inputEle = page.crisisDetail.element(by.css('input'));
diff --git a/public/docs/_examples/router/ts/app/admin/admin-dashboard.component.1.ts b/public/docs/_examples/router/ts/app/admin/admin-dashboard.component.1.ts
new file mode 100644
index 0000000000..ffa3e3cb8f
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin-dashboard.component.1.ts
@@ -0,0 +1,9 @@
+// #docregion
+import { Component } from '@angular/core';
+
+@Component({
+  template:  `
+    <p>Dashboard</p>
+  `
+})
+export class AdminDashboardComponent { }
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.ts b/public/docs/_examples/router/ts/app/admin/admin-dashboard.component.ts
old mode 100755
new mode 100644
similarity index 86%
rename from public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.ts
rename to public/docs/_examples/router/ts/app/admin/admin-dashboard.component.ts
index 38fe14a38e..8c8e481643
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.ts
+++ b/public/docs/_examples/router/ts/app/admin/admin-dashboard.component.ts
@@ -6,15 +6,14 @@ import 'rxjs/add/operator/map';
 
 @Component({
   template:  `
-    <h3>CRISIS ADMINISTRATION</h3>
-    <p>Manage your crises here</p>
+    <p>Dashboard</p>
 
     <p>Session ID: {{ sessionId | async }}</p>
     <a id="anchor"></a>
     <p>Token: {{ token | async }}</p>
   `
 })
-export class CrisisAdminComponent implements OnInit {
+export class AdminDashboardComponent implements OnInit {
   sessionId: Observable<string>;
   token: Observable<string>;
 
diff --git a/public/docs/_examples/router/ts/app/admin/admin.component.ts b/public/docs/_examples/router/ts/app/admin/admin.component.ts
new file mode 100755
index 0000000000..30abfa4524
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.component.ts
@@ -0,0 +1,17 @@
+// #docregion
+import { Component } from '@angular/core';
+
+@Component({
+  template:  `
+    <h3>ADMIN</h3>
+    <nav>
+      <a routerLink="./" routerLinkActive="active"
+        [routerLinkActiveOptions]="{ exact: true }">Dashboard</a>
+      <a routerLink="./crises" routerLinkActive="active">Manage Crises</a>
+      <a routerLink="./heroes" routerLinkActive="active">Manage Heroes</a>
+    </nav>
+    <router-outlet></router-outlet>
+  `
+})
+export class AdminComponent {
+}
diff --git a/public/docs/_examples/router/ts/app/admin/admin.module.ts b/public/docs/_examples/router/ts/app/admin/admin.module.ts
new file mode 100644
index 0000000000..dce2ce30e2
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.module.ts
@@ -0,0 +1,28 @@
+// #docplaster
+// #docregion
+import { NgModule }       from '@angular/core';
+import { CommonModule }   from '@angular/common';
+
+import { AdminComponent }           from './admin.component';
+import { AdminDashboardComponent }  from './admin-dashboard.component';
+import { ManageCrisesComponent }    from './manage-crises.component';
+import { ManageHeroesComponent }    from './manage-heroes.component';
+
+import { adminRouting } from './admin.routing';
+
+@NgModule({
+  imports: [
+    CommonModule,
+    adminRouting
+  ],
+  declarations: [
+    AdminComponent,
+    AdminDashboardComponent,
+    ManageCrisesComponent,
+    ManageHeroesComponent
+  ]
+})
+// #docregion admin-module-export
+export class AdminModule {}
+// #enddocregion admin-module-export
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/admin/admin.routing.1.ts b/public/docs/_examples/router/ts/app/admin/admin.routing.1.ts
new file mode 100644
index 0000000000..a620f3ba51
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.routing.1.ts
@@ -0,0 +1,31 @@
+// #docplaster
+// #docregion
+import { ModuleWithProviders }   from '@angular/core';
+import { Routes, RouterModule }  from '@angular/router';
+
+import { AdminComponent }           from './admin.component';
+import { AdminDashboardComponent }  from './admin-dashboard.component';
+import { ManageCrisesComponent }    from './manage-crises.component';
+import { ManageHeroesComponent }    from './manage-heroes.component';
+
+// #docregion admin-routes
+const adminRoutes: Routes = [
+  {
+    path: 'admin',
+    component: AdminComponent,
+    children: [
+      {
+        path: '',
+        children: [
+          { path: 'crises', component: ManageCrisesComponent },
+          { path: 'heroes', component: ManageHeroesComponent },
+          { path: '', component: AdminDashboardComponent }
+        ]
+      }
+    ]
+  }
+];
+
+export const adminRouting: ModuleWithProviders = RouterModule.forChild(adminRoutes);
+// #enddocregion admin-routes
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/admin/admin.routing.2.ts b/public/docs/_examples/router/ts/app/admin/admin.routing.2.ts
new file mode 100644
index 0000000000..9fa3f10e4a
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.routing.2.ts
@@ -0,0 +1,37 @@
+// #docplaster
+// #docregion
+import { ModuleWithProviders }   from '@angular/core';
+import { Routes, RouterModule }  from '@angular/router';
+
+import { AdminComponent }           from './admin.component';
+import { AdminDashboardComponent }  from './admin-dashboard.component';
+import { ManageCrisesComponent }    from './manage-crises.component';
+import { ManageHeroesComponent }    from './manage-heroes.component';
+
+// #docregion admin-route, can-activate-child
+import { AuthGuard }                from '../auth-guard.service';
+
+const adminRoutes: Routes = [
+  {
+    path: 'admin',
+    component: AdminComponent,
+    canActivate: [AuthGuard],
+    children: [
+      {
+        path: '',
+        children: [
+          { path: 'crises', component: ManageCrisesComponent },
+          { path: 'heroes', component: ManageHeroesComponent },
+          { path: '', component: AdminDashboardComponent }
+        ],
+        // #enddocregion admin-route
+        // #docregion can-activate-child
+        canActivateChild: [AuthGuard]
+        // #docregion admin-route
+      }
+    ]
+  }
+];
+
+export const adminRouting: ModuleWithProviders = RouterModule.forChild(adminRoutes);
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/admin/admin.routing.3.ts b/public/docs/_examples/router/ts/app/admin/admin.routing.3.ts
new file mode 100644
index 0000000000..3b4051a819
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.routing.3.ts
@@ -0,0 +1,35 @@
+// #docplaster
+// #docregion
+import { ModuleWithProviders }   from '@angular/core';
+import { Routes, RouterModule }  from '@angular/router';
+
+import { AdminComponent }           from './admin.component';
+import { AdminDashboardComponent }  from './admin-dashboard.component';
+import { ManageCrisesComponent }    from './manage-crises.component';
+import { ManageHeroesComponent }    from './manage-heroes.component';
+
+// #docregion admin-route
+import { AuthGuard }                from '../auth-guard.service';
+
+// #docregion can-activate-child
+const adminRoutes: Routes = [
+  {
+    path: 'admin',
+    component: AdminComponent,
+    canActivate: [AuthGuard],
+    children: [
+      {
+        path: '',
+        canActivateChild: [AuthGuard],
+        children: [
+          { path: 'crises', component: ManageCrisesComponent },
+          { path: 'heroes', component: ManageHeroesComponent },
+          { path: '', component: AdminDashboardComponent }
+        ]
+      }
+    ]
+  }
+];
+
+export const adminRouting: ModuleWithProviders = RouterModule.forChild(adminRoutes);
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/admin/admin.routing.ts b/public/docs/_examples/router/ts/app/admin/admin.routing.ts
new file mode 100644
index 0000000000..bc5d13554c
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/admin.routing.ts
@@ -0,0 +1,34 @@
+// #docplaster
+// #docregion
+import { ModuleWithProviders }   from '@angular/core';
+import { Routes, RouterModule }  from '@angular/router';
+
+import { AdminComponent }           from './admin.component';
+import { AdminDashboardComponent }  from './admin-dashboard.component';
+import { ManageCrisesComponent }    from './manage-crises.component';
+import { ManageHeroesComponent }    from './manage-heroes.component';
+
+// #docregion admin-route
+import { AuthGuard }                from '../auth-guard.service';
+
+const adminRoutes: Routes = [
+  {
+    path: '',
+    component: AdminComponent,
+    canActivate: [AuthGuard],
+    children: [
+      {
+        path: '',
+        canActivateChild: [AuthGuard],
+        children: [
+          { path: 'crises', component: ManageCrisesComponent },
+          { path: 'heroes', component: ManageHeroesComponent },
+          { path: '', component: AdminDashboardComponent }
+        ]
+      }
+    ]
+  }
+];
+
+export const adminRouting: ModuleWithProviders = RouterModule.forChild(adminRoutes);
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.1.ts b/public/docs/_examples/router/ts/app/admin/manage-crises.component.ts
similarity index 63%
rename from public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.1.ts
rename to public/docs/_examples/router/ts/app/admin/manage-crises.component.ts
index a8dacc8549..d3176563eb 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-admin.component.1.ts
+++ b/public/docs/_examples/router/ts/app/admin/manage-crises.component.ts
@@ -3,8 +3,7 @@ import { Component } from '@angular/core';
 
 @Component({
   template:  `
-    <h3>CRISIS ADMINISTRATION</h3>
     <p>Manage your crises here</p>
   `
 })
-export class CrisisAdminComponent { }
+export class ManageCrisesComponent { }
diff --git a/public/docs/_examples/router/ts/app/admin/manage-heroes.component.ts b/public/docs/_examples/router/ts/app/admin/manage-heroes.component.ts
new file mode 100644
index 0000000000..7f3a39893d
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/admin/manage-heroes.component.ts
@@ -0,0 +1,9 @@
+// #docregion
+import { Component } from '@angular/core';
+
+@Component({
+  template:  `
+    <p>Manage your heroes here</p>
+  `
+})
+export class ManageHeroesComponent { }
diff --git a/public/docs/_examples/router/ts/app/app.component.1.ts b/public/docs/_examples/router/ts/app/app.component.1.ts
index 1b0aba0044..21e9aa417d 100644
--- a/public/docs/_examples/router/ts/app/app.component.1.ts
+++ b/public/docs/_examples/router/ts/app/app.component.1.ts
@@ -6,7 +6,7 @@ import { Component } from '@angular/core';
   selector: 'my-app',
   // #docregion template
   template: `
-    <h1>Component Router</h1>
+    <h1>Angular Router</h1>
     <nav>
       <a routerLink="/crisis-center" routerLinkActive="active">Crisis Center</a>
       <a routerLink="/heroes" routerLinkActive="active">Heroes</a>
diff --git a/public/docs/_examples/router/ts/app/app.component.2.ts b/public/docs/_examples/router/ts/app/app.component.2.ts
index 7593aa1608..fa3ddf01b9 100644
--- a/public/docs/_examples/router/ts/app/app.component.2.ts
+++ b/public/docs/_examples/router/ts/app/app.component.2.ts
@@ -7,7 +7,7 @@ import { Component } from '@angular/core';
 @Component({
   selector: 'my-app',
   template: `
-    <h1>Component Router</h1>
+    <h1>Angular Router</h1>
     <nav>
       <a routerLink="/crisis-center" routerLinkActive="active">Crisis Center</a>
       <a routerLink="/heroes" routerLinkActive="active">Heroes</a>
diff --git a/public/docs/_examples/router/ts/app/app.component.3.ts b/public/docs/_examples/router/ts/app/app.component.3.ts
index 1150a01814..ad4dbe33d6 100644
--- a/public/docs/_examples/router/ts/app/app.component.3.ts
+++ b/public/docs/_examples/router/ts/app/app.component.3.ts
@@ -1,7 +1,7 @@
 /* tslint:disable:no-unused-variable */
 // #docplaster
 import { Component } from '@angular/core';
-import { Router } from '@angular/router';
+import { Router }    from '@angular/router';
 
 @Component({
   selector: 'my-app',
@@ -36,7 +36,7 @@ import { Router } from '@angular/router';
   */
 // #docregion template
   template: `
-    <h1 class="title">Component Router</h1>
+    <h1 class="title">Angular Router</h1>
     <nav>
       <a [routerLink]="['/crisis-center']">Crisis Center</a>
       <a [routerLink]="['/crisis-center/1', { foo: 'foo' }]">Dragon Crisis</a>
diff --git a/public/docs/_examples/router/ts/app/app.component.4.ts b/public/docs/_examples/router/ts/app/app.component.4.ts
index e609850a42..9769d4f2da 100644
--- a/public/docs/_examples/router/ts/app/app.component.4.ts
+++ b/public/docs/_examples/router/ts/app/app.component.4.ts
@@ -1,16 +1,15 @@
 // #docregion
-import { Component }          from '@angular/core';
+import { Component } from '@angular/core';
 
 @Component({
   selector: 'my-app',
   // #docregion template
   template: `
-    <h1 class="title">Component Router</h1>
+    <h1 class="title">Angular Router</h1>
     <nav>
-      <a routerLink="/crisis-center" routerLinkActive="active"
-         [routerLinkActiveOptions]="{ exact: true }">Crisis Center</a>
+      <a routerLink="/crisis-center" routerLinkActive="active">Crisis Center</a>
       <a routerLink="/heroes" routerLinkActive="active">Heroes</a>
-      <a routerLink="/crisis-center/admin" routerLinkActive="active">Crisis Admin</a>
+      <a routerLink="/admin" routerLinkActive="active">Admin</a>
     </nav>
     <router-outlet></router-outlet>
   `
diff --git a/public/docs/_examples/router/ts/app/app.component.ts b/public/docs/_examples/router/ts/app/app.component.ts
index 2dcb0a062b..37f69472a0 100644
--- a/public/docs/_examples/router/ts/app/app.component.ts
+++ b/public/docs/_examples/router/ts/app/app.component.ts
@@ -1,17 +1,16 @@
 // #docplaster
 // #docregion
-import { Component }          from '@angular/core';
+import { Component } from '@angular/core';
 
 @Component({
   selector: 'my-app',
   // #docregion template
   template: `
-    <h1 class="title">Component Router</h1>
+    <h1 class="title">Angular Router</h1>
     <nav>
-      <a routerLink="/crisis-center" routerLinkActive="active"
-         [routerLinkActiveOptions]="{ exact: true }">Crisis Center</a>
+      <a routerLink="/crisis-center" routerLinkActive="active">Crisis Center</a>
       <a routerLink="/heroes" routerLinkActive="active">Heroes</a>
-      <a routerLink="/crisis-center/admin" routerLinkActive="active">Crisis Admin</a>
+      <a routerLink="/admin" routerLinkActive="active">Admin</a>
       <a routerLink="/login" routerLinkActive="active">Login</a>
     </nav>
     <router-outlet></router-outlet>
diff --git a/public/docs/_examples/router/ts/app/app.module.1.ts b/public/docs/_examples/router/ts/app/app.module.1.ts
index c6d5648bbf..ea1edc36af 100644
--- a/public/docs/_examples/router/ts/app/app.module.1.ts
+++ b/public/docs/_examples/router/ts/app/app.module.1.ts
@@ -4,11 +4,10 @@ import { NgModule }       from '@angular/core';
 import { BrowserModule }  from '@angular/platform-browser';
 import { FormsModule }    from '@angular/forms';
 
-
 // #docregion router-basics
-import { AppComponent }       from './app.component';
+import { AppComponent }         from './app.component';
 import { routing,
-         appRoutingProviders } from './app.routing';
+         appRoutingProviders }  from './app.routing';
 
 import { HeroListComponent }    from './hero-list.component';
 import { CrisisListComponent }  from './crisis-list.component';
diff --git a/public/docs/_examples/router/ts/app/app.module.2.ts b/public/docs/_examples/router/ts/app/app.module.2.ts
index 35913ae6a2..3e1d42896c 100644
--- a/public/docs/_examples/router/ts/app/app.module.2.ts
+++ b/public/docs/_examples/router/ts/app/app.module.2.ts
@@ -1,14 +1,14 @@
 // #docplaster
 // #docregion
+// #docregion hero-import
 import { NgModule }       from '@angular/core';
 import { BrowserModule }  from '@angular/platform-browser';
 import { FormsModule }    from '@angular/forms';
 
-import { AppComponent }       from './app.component';
+import { AppComponent }         from './app.component';
 import { routing,
-         appRoutingProviders } from './app.routing';
+         appRoutingProviders }  from './app.routing';
 
-// #docregion hero-import
 import { HeroesModule }         from './heroes/heroes.module';
 
 import { CrisisListComponent }  from './crisis-list.component';
diff --git a/public/docs/_examples/router/ts/app/app.module.3.ts b/public/docs/_examples/router/ts/app/app.module.3.ts
index d1969a860a..6ddd73ac3e 100644
--- a/public/docs/_examples/router/ts/app/app.module.3.ts
+++ b/public/docs/_examples/router/ts/app/app.module.3.ts
@@ -1,24 +1,34 @@
+// #docplaster
 // #docregion
+// #docregion crisis-center-module, admin-module
 import { NgModule }       from '@angular/core';
-import { BrowserModule }  from '@angular/platform-browser';
+import { CommonModule }   from '@angular/common';
 import { FormsModule }    from '@angular/forms';
 
-import { AppComponent }       from './app.component';
+import { AppComponent }           from './app.component';
 import { routing,
-         appRoutingProviders } from './app.routing';
+         appRoutingProviders }    from './app.routing';
 
 import { HeroesModule }           from './heroes/heroes.module';
+// #docregion crisis-center-module
 import { CrisisCenterModule }     from './crisis-center/crisis-center.module';
+// #enddocregion crisis-center-module
+// #docregion admin-module
+import { AdminModule }            from './admin/admin.module';
+// #docregion crisis-center-module
 
-import { DialogService }  from './dialog.service';
+import { DialogService }          from './dialog.service';
 
 @NgModule({
   imports: [
-    BrowserModule,
+    CommonModule,
     FormsModule,
     routing,
     HeroesModule,
-    CrisisCenterModule
+    CrisisCenterModule,
+// #enddocregion crisis-center-module
+    AdminModule
+// #docregion crisis-center-module
   ],
   declarations: [
     AppComponent
@@ -31,3 +41,4 @@ import { DialogService }  from './dialog.service';
 })
 export class AppModule {
 }
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/app.module.4.ts b/public/docs/_examples/router/ts/app/app.module.4.ts
index 96a8eb61d9..840ea422db 100644
--- a/public/docs/_examples/router/ts/app/app.module.4.ts
+++ b/public/docs/_examples/router/ts/app/app.module.4.ts
@@ -2,25 +2,30 @@
 import { NgModule }       from '@angular/core';
 import { BrowserModule }  from '@angular/platform-browser';
 import { FormsModule }    from '@angular/forms';
-import { Routes, RouterModule }   from '@angular/router';
 
-import { AppComponent }   from './app.component';
+import { AppComponent }        from './app.component';
+import { routing,
+         appRoutingProviders } from './app.routing';
 
-const routes: Routes = [
+import { HeroesModule }        from './heroes/heroes.module';
+import { CrisisCenterModule }  from './crisis-center/crisis-center.module';
 
-];
+import { DialogService }       from './dialog.service';
 
 @NgModule({
   imports: [
     BrowserModule,
     FormsModule,
-    RouterModule.forRoot(routes, { useHash: true })  // .../#/crisis-center/
+    routing,
+    HeroesModule,
+    CrisisCenterModule
   ],
   declarations: [
     AppComponent
   ],
   providers: [
-
+    appRoutingProviders,
+    DialogService
   ],
   bootstrap: [ AppComponent ]
 })
diff --git a/public/docs/_examples/router/ts/app/app.module.5.ts b/public/docs/_examples/router/ts/app/app.module.5.ts
new file mode 100644
index 0000000000..b1ba4bd231
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/app.module.5.ts
@@ -0,0 +1,28 @@
+// #docregion
+import { NgModule }             from '@angular/core';
+import { BrowserModule }        from '@angular/platform-browser';
+import { FormsModule }          from '@angular/forms';
+import { Routes, RouterModule } from '@angular/router';
+
+import { AppComponent }  from './app.component';
+
+const routes: Routes = [
+
+];
+
+@NgModule({
+  imports: [
+    BrowserModule,
+    FormsModule,
+    RouterModule.forRoot(routes, { useHash: true })  // .../#/crisis-center/
+  ],
+  declarations: [
+    AppComponent
+  ],
+  providers: [
+
+  ],
+  bootstrap: [ AppComponent ]
+})
+export class AppModule {
+}
diff --git a/public/docs/_examples/router/ts/app/app.module.ts b/public/docs/_examples/router/ts/app/app.module.ts
index f273052d83..87c031e2bb 100644
--- a/public/docs/_examples/router/ts/app/app.module.ts
+++ b/public/docs/_examples/router/ts/app/app.module.ts
@@ -3,22 +3,24 @@ import { NgModule }       from '@angular/core';
 import { BrowserModule }  from '@angular/platform-browser';
 import { FormsModule }    from '@angular/forms';
 
-import { AppComponent }       from './app.component';
+import { AppComponent }         from './app.component';
 import { routing,
-         appRoutingProviders } from './app.routing';
+         appRoutingProviders }  from './app.routing';
 
-import { HeroesModule } from './heroes/heroes.module';
+import { HeroesModule }         from './heroes/heroes.module';
+import { CrisisCenterModule }   from './crisis-center/crisis-center.module';
 
-import { LoginComponent } from './login.component';
+import { LoginComponent }       from './login.component';
 
-import { DialogService }  from './dialog.service';
+import { DialogService }        from './dialog.service';
 
 @NgModule({
   imports: [
     BrowserModule,
     FormsModule,
     routing,
-    HeroesModule
+    HeroesModule,
+    CrisisCenterModule
   ],
   declarations: [
     AppComponent,
diff --git a/public/docs/_examples/router/ts/app/app.routing.1.ts b/public/docs/_examples/router/ts/app/app.routing.1.ts
index 9bc91e6b61..736f49b4fb 100644
--- a/public/docs/_examples/router/ts/app/app.routing.1.ts
+++ b/public/docs/_examples/router/ts/app/app.routing.1.ts
@@ -12,12 +12,16 @@ import { HeroListComponent }     from './hero-list.component';
 import { CrisisCenterComponent } from './crisis-center/crisis-center.component';
 import { HeroDetailComponent }   from './heroes/hero-detail.component';
 import { PageNotFoundComponent } from './not-found.component';
+import { PageNotFoundComponent as HomeComponent } from './not-found.component';
 // #enddocregion base-routes
 
 // #docregion
 // #docregion route-config
 const appRoutes: Routes = [
   // #docregion route-defs
+  // #docregion hero-detail-route
+  { path: 'hero/:id', component: HeroDetailComponent },
+  // #enddocregion hero-detail-route
   { path: 'crisis-center', component: CrisisCenterComponent },
   {
     path: 'heroes',
@@ -26,10 +30,8 @@ const appRoutes: Routes = [
       title: 'Heroes List'
     }
   },
+  { path: '', component: HomeComponent },
   // #enddocregion route-defs
-  // #docregion hero-detail-route
-  { path: 'hero/:id', component: HeroDetailComponent },
-  // #enddocregion hero-detail-route
   { path: '**', component: PageNotFoundComponent }
 ];
 
diff --git a/public/docs/_examples/router/ts/app/app.routing.3.ts b/public/docs/_examples/router/ts/app/app.routing.3.ts
index 92930849f0..247ec7f2dd 100644
--- a/public/docs/_examples/router/ts/app/app.routing.3.ts
+++ b/public/docs/_examples/router/ts/app/app.routing.3.ts
@@ -3,10 +3,10 @@
 import { ModuleWithProviders }  from '@angular/core';
 import { Routes, RouterModule } from '@angular/router';
 
-import { CrisisListComponent } from './crisis-center/crisis-list.component';
+import { CrisisCenterComponent } from './crisis-center/crisis-center.component';
 
 const appRoutes: Routes = [
-  { path: 'crisis-center', component: CrisisListComponent }
+  { path: 'crisis-center', component: CrisisCenterComponent }
 ];
 
 export const appRoutingProviders: any[] = [
diff --git a/public/docs/_examples/router/ts/app/app.routing.6.ts b/public/docs/_examples/router/ts/app/app.routing.6.ts
index ceee844f0e..8dc92f9dc4 100644
--- a/public/docs/_examples/router/ts/app/app.routing.6.ts
+++ b/public/docs/_examples/router/ts/app/app.routing.6.ts
@@ -9,24 +9,9 @@ import { loginRoutes,
 
 import { CanDeactivateGuard } from './can-deactivate-guard.service';
 
-// #docregion lazy-load-crisis-center
-const crisisCenterRoutes: Routes = [
-  {
-    path: '',
-    redirectTo: '/crisis-center',
-    pathMatch: 'full'
-  },
-  {
-    path: 'crisis-center',
-    loadChildren: 'app/crisis-center/crisis-center.module#CrisisCenterModule'
-  }
-];
-
 const appRoutes: Routes = [
-  ...loginRoutes,
-  ...crisisCenterRoutes
+  ...loginRoutes
 ];
-// #enddocregion lazy-load-crisis-center
 
 export const appRoutingProviders: any[] = [
   authProviders,
@@ -34,14 +19,3 @@ export const appRoutingProviders: any[] = [
 ];
 
 export const routing: ModuleWithProviders = RouterModule.forRoot(appRoutes);
-// #enddocregion
-
-/* A link parameters array
-// #docregion heroes-redirect
-{
-  path: '',
-  redirectTo: '/heroes',
-  pathMatch: 'full'
-},
-// #enddocregion heroes-redirect
-*/
diff --git a/public/docs/_examples/router/ts/app/app.routing.ts b/public/docs/_examples/router/ts/app/app.routing.ts
index bf456cba9a..cd00b9bf0c 100644
--- a/public/docs/_examples/router/ts/app/app.routing.ts
+++ b/public/docs/_examples/router/ts/app/app.routing.ts
@@ -1,32 +1,36 @@
+// #docplaster
 // #docregion
-import { ModuleWithProviders } from '@angular/core';
+import { ModuleWithProviders }  from '@angular/core';
 // #docregion import-router
-import { Routes, RouterModule }   from '@angular/router';
+import { Routes, RouterModule } from '@angular/router';
 // #enddocregion import-router
 
 import { loginRoutes,
-         authProviders }  from './login.routing';
+         authProviders }      from './login.routing';
 
 import { CanDeactivateGuard } from './can-deactivate-guard.service';
+// #docregion can-load-guard
+import { AuthGuard }          from './auth-guard.service';
+// #enddocregion can-load-guard
 
-// #docregion lazy-load-crisis-center
-const crisisCenterRoutes: Routes = [
+// #docregion lazy-load-admin, can-load-guard
+
+const adminRoutes: Routes = [
   {
-    path: '',
-    redirectTo: '/heroes',
-    pathMatch: 'full'
-  },
-  {
-    path: 'crisis-center',
-    loadChildren: 'app/crisis-center/crisis-center.module#CrisisCenterModule'
+    path: 'admin',
+    loadChildren: 'app/admin/admin.module#AdminModule',
+// #enddocregion lazy-load-admin
+    canLoad: [AuthGuard]
+// #docregion lazy-load-admin
   }
 ];
+// #enddocregion can-load-guard
 
 const appRoutes: Routes = [
   ...loginRoutes,
-  ...crisisCenterRoutes
+  ...adminRoutes
 ];
-// #enddocregion lazy-load-crisis-center
+// #enddocregion lazy-load-admin
 
 export const appRoutingProviders: any[] = [
   authProviders,
diff --git a/public/docs/_examples/router/ts/app/auth-guard.service.2.ts b/public/docs/_examples/router/ts/app/auth-guard.service.2.ts
index 9d4f3afb3b..8fd00e151a 100644
--- a/public/docs/_examples/router/ts/app/auth-guard.service.2.ts
+++ b/public/docs/_examples/router/ts/app/auth-guard.service.2.ts
@@ -1,22 +1,37 @@
 // #docregion
-import { Injectable }             from '@angular/core';
-import { CanActivate, Router,
-         ActivatedRouteSnapshot,
-         RouterStateSnapshot }    from '@angular/router';
-import { AuthService }            from './auth.service';
+import { Injectable }       from '@angular/core';
+import {
+  CanActivate, Router,
+  ActivatedRouteSnapshot,
+  RouterStateSnapshot
+}                           from '@angular/router';
+import { AuthService }      from './auth.service';
 
 @Injectable()
 export class AuthGuard implements CanActivate {
   constructor(private authService: AuthService, private router: Router) {}
 
-  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) {
+  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    let url: string = state.url;
+
+    return this.checkLogin(url);
+  }
+
+  checkLogin(url: string): boolean {
     if (this.authService.isLoggedIn) { return true; }
 
     // Store the attempted URL for redirecting
-    this.authService.redirectUrl = state.url;
+    this.authService.redirectUrl = url;
 
-    // Navigate to the login page
+    // Navigate to the login page with extras
     this.router.navigate(['/login']);
     return false;
   }
 }
+// #enddocregion
+
+/*
+// #docregion can-load-interface
+export class AuthGuard implements CanActivate, CanLoad {
+// #enddocregion can-load-interface
+*/
diff --git a/public/docs/_examples/router/ts/app/auth-guard.service.3.ts b/public/docs/_examples/router/ts/app/auth-guard.service.3.ts
new file mode 100644
index 0000000000..8e417625fe
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/auth-guard.service.3.ts
@@ -0,0 +1,40 @@
+// #docplaster
+// #docregion
+// #docregion can-activate-child
+import { Injectable }       from '@angular/core';
+import {
+  CanActivate, Router,
+  ActivatedRouteSnapshot,
+  RouterStateSnapshot,
+  CanActivateChild
+}                           from '@angular/router';
+import { AuthService }      from './auth.service';
+
+@Injectable()
+export class AuthGuard implements CanActivate, CanActivateChild {
+  constructor(private authService: AuthService, private router: Router) {}
+
+  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    let url: string = state.url;
+
+    return this.checkLogin(url);
+  }
+
+  canActivateChild(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    return this.canActivate(route, state);
+  }
+
+// #enddocregion can-activate-child
+  checkLogin(url: string): boolean {
+    if (this.authService.isLoggedIn) { return true; }
+
+    // Store the attempted URL for redirecting
+    this.authService.redirectUrl = url;
+
+    // Navigate to the login page
+    this.router.navigate(['/login']);
+    return false;
+  }
+// #docregion can-activate-child
+}
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/auth-guard.service.4.ts b/public/docs/_examples/router/ts/app/auth-guard.service.4.ts
new file mode 100644
index 0000000000..5d239a8432
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/auth-guard.service.4.ts
@@ -0,0 +1,47 @@
+// #docplaster
+// #docregion
+import { Injectable }       from '@angular/core';
+import {
+  CanActivate, Router,
+  ActivatedRouteSnapshot,
+  RouterStateSnapshot,
+  CanActivateChild,
+  NavigationExtras
+}                           from '@angular/router';
+import { AuthService }      from './auth.service';
+
+@Injectable()
+export class AuthGuard implements CanActivate, CanActivateChild {
+  constructor(private authService: AuthService, private router: Router) {}
+
+  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    let url: string = state.url;
+
+    return this.checkLogin(url);
+  }
+
+  canActivateChild(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    return this.canActivate(route, state);
+  }
+
+  checkLogin(url: string): boolean {
+    if (this.authService.isLoggedIn) { return true; }
+
+    // Store the attempted URL for redirecting
+    this.authService.redirectUrl = url;
+
+    // Create a dummy session id
+    let sessionId = 123456789;
+
+    // Set our navigation extras object
+    // that contains our global query params and fragment
+    let navigationExtras: NavigationExtras = {
+      queryParams: { 'session_id': sessionId },
+      fragment: 'anchor'
+    };
+
+    // Navigate to the login page with extras
+    this.router.navigate(['/login'], navigationExtras);
+    return false;
+  }
+}
diff --git a/public/docs/_examples/router/ts/app/auth-guard.service.ts b/public/docs/_examples/router/ts/app/auth-guard.service.ts
index 63aee1deb5..5f93d07533 100755
--- a/public/docs/_examples/router/ts/app/auth-guard.service.ts
+++ b/public/docs/_examples/router/ts/app/auth-guard.service.ts
@@ -1,20 +1,42 @@
-// #docregion
-import { Injectable }             from '@angular/core';
-import { CanActivate, Router,
-         ActivatedRouteSnapshot,
-         RouterStateSnapshot,
-         NavigationExtras }       from '@angular/router';
-import { AuthService }            from './auth.service';
+// #docplaster
+// #docregion, admin-can-load
+import { Injectable }       from '@angular/core';
+import {
+  CanActivate, Router,
+  ActivatedRouteSnapshot,
+  RouterStateSnapshot,
+  CanActivateChild,
+  NavigationExtras,
+  CanLoad, Route
+}                           from '@angular/router';
+import { AuthService }      from './auth.service';
 
 @Injectable()
-export class AuthGuard implements CanActivate {
+export class AuthGuard implements CanActivate, CanActivateChild, CanLoad {
   constructor(private authService: AuthService, private router: Router) {}
 
-  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) {
+  canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    let url: string = state.url;
+
+    return this.checkLogin(url);
+  }
+
+  canActivateChild(route: ActivatedRouteSnapshot, state: RouterStateSnapshot): boolean {
+    return this.canActivate(route, state);
+  }
+
+  canLoad(route: Route): boolean {
+    let url = `/${route.path}`;
+
+    return this.checkLogin(url);
+  }
+// #enddocregion admin-can-load
+
+  checkLogin(url: string): boolean {
     if (this.authService.isLoggedIn) { return true; }
 
     // Store the attempted URL for redirecting
-    this.authService.redirectUrl = state.url;
+    this.authService.redirectUrl = url;
 
     // Create a dummy session id
     let sessionId = 123456789;
@@ -30,4 +52,5 @@ export class AuthGuard implements CanActivate {
     this.router.navigate(['/login'], navigationExtras);
     return false;
   }
+// #docregion admin-can-load
 }
diff --git a/public/docs/_examples/router/ts/app/auth.service.ts b/public/docs/_examples/router/ts/app/auth.service.ts
index d6f8414af1..f86a80ebfe 100755
--- a/public/docs/_examples/router/ts/app/auth.service.ts
+++ b/public/docs/_examples/router/ts/app/auth.service.ts
@@ -13,11 +13,11 @@ export class AuthService {
   // store the URL so we can redirect after logging in
   redirectUrl: string;
 
-  login() {
+  login(): Observable<boolean> {
     return Observable.of(true).delay(1000).do(val => this.isLoggedIn = true);
   }
 
-  logout() {
+  logout(): void {
     this.isLoggedIn = false;
   }
 }
diff --git a/public/docs/_examples/router/ts/app/can-deactivate-guard.service.1.ts b/public/docs/_examples/router/ts/app/can-deactivate-guard.service.1.ts
index b6e16bfa4c..0b7c8247cf 100644
--- a/public/docs/_examples/router/ts/app/can-deactivate-guard.service.1.ts
+++ b/public/docs/_examples/router/ts/app/can-deactivate-guard.service.1.ts
@@ -3,7 +3,6 @@ import { Injectable }           from '@angular/core';
 import { CanDeactivate,
          ActivatedRouteSnapshot,
          RouterStateSnapshot }  from '@angular/router';
-import { Observable }           from 'rxjs/Observable';
 
 import { CrisisDetailComponent } from './crisis-center/crisis-detail.component';
 
@@ -14,7 +13,7 @@ export class CanDeactivateGuard implements CanDeactivate<CrisisDetailComponent>
     component: CrisisDetailComponent,
     route: ActivatedRouteSnapshot,
     state: RouterStateSnapshot
-  ): Observable<boolean> | Promise<boolean> | boolean {
+  ): Promise<boolean> | boolean {
     // Get the Crisis Center ID
     console.log(route.params['id']);
 
diff --git a/public/docs/_examples/router/ts/app/can-deactivate-guard.service.ts b/public/docs/_examples/router/ts/app/can-deactivate-guard.service.ts
index db8ecef5bf..44da69f9c7 100644
--- a/public/docs/_examples/router/ts/app/can-deactivate-guard.service.ts
+++ b/public/docs/_examples/router/ts/app/can-deactivate-guard.service.ts
@@ -4,12 +4,12 @@ import { CanDeactivate } from '@angular/router';
 import { Observable }    from 'rxjs/Observable';
 
 export interface CanComponentDeactivate {
- canDeactivate: () => boolean | Observable<boolean>;
+ canDeactivate: () => Observable<boolean> | Promise<boolean> | boolean;
 }
 
 @Injectable()
 export class CanDeactivateGuard implements CanDeactivate<CanComponentDeactivate> {
-  canDeactivate(component: CanComponentDeactivate): Observable<boolean> | Promise<boolean> | boolean {
+  canDeactivate(component: CanComponentDeactivate) {
     return component.canDeactivate ? component.canDeactivate() : true;
   }
 }
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center-home.component.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center-home.component.ts
new file mode 100644
index 0000000000..a71d485c02
--- /dev/null
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center-home.component.ts
@@ -0,0 +1,13 @@
+// #docregion
+// #docplaster
+import { Component } from '@angular/core';
+
+// #docregion minus-imports
+@Component({
+  template: `
+    <p>Welcome to the Crisis Center</p>
+  `
+})
+export class CrisisCenterHomeComponent { }
+// #enddocregion minus-imports
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.1.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.1.ts
index a392ccfe04..ab29a0ba22 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.1.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.1.ts
@@ -1,3 +1,4 @@
+// #docplaster
 // #docregion
 import { NgModule }       from '@angular/core';
 import { FormsModule }    from '@angular/forms';
@@ -6,7 +7,8 @@ import { CommonModule }   from '@angular/common';
 import { CrisisService }        from './crisis.service';
 
 import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisListComponent }   from './crisis-list.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
 import { CrisisDetailComponent } from './crisis-detail.component';
 
 import { crisisCenterRouting } from './crisis-center.routing';
@@ -20,13 +22,15 @@ import { crisisCenterRouting } from './crisis-center.routing';
   declarations: [
     CrisisCenterComponent,
     CrisisListComponent,
+    CrisisCenterHomeComponent,
     CrisisDetailComponent
   ],
-// #docregion providers
+
+  // #docregion providers
   providers: [
     CrisisService
   ]
-// #enddocregion providers
+  // #enddocregion providers
 })
 export class CrisisCenterModule {}
 // #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.ts
index 41b31d6aa5..3a66164607 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.module.ts
@@ -9,10 +9,10 @@ import { CrisisService }        from './crisis.service';
 import { CrisisDetailResolve }  from './crisis-detail-resolve.service';
 // #enddocregion crisis-detail-resolve
 
-import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisAdminComponent }  from './crisis-admin.component';
+import { CrisisCenterComponent }     from './crisis-center.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
+import { CrisisDetailComponent }     from './crisis-detail.component';
 
 import { crisisCenterRouting } from './crisis-center.routing';
 
@@ -25,8 +25,8 @@ import { crisisCenterRouting } from './crisis-center.routing';
   declarations: [
     CrisisCenterComponent,
     CrisisListComponent,
-    CrisisDetailComponent,
-    CrisisAdminComponent
+    CrisisCenterHomeComponent,
+    CrisisDetailComponent
   ],
   // #docregion crisis-detail-resolve
 
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.1.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.1.ts
index 7c7b913c31..8ef262c189 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.1.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.1.ts
@@ -1,10 +1,12 @@
+// #docplaster
 // #docregion
 import { ModuleWithProviders }   from '@angular/core';
 import { Routes, RouterModule }  from '@angular/router';
 
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisCenterComponent } from './crisis-center.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterComponent }     from './crisis-center.component';
+import { CrisisDetailComponent }     from './crisis-detail.component';
 
 // #docregion routes
 const crisisCenterRoutes: Routes = [
@@ -12,11 +14,24 @@ const crisisCenterRoutes: Routes = [
     path: 'crisis-center',
     component: CrisisCenterComponent,
     children: [
-      { path: ':id',  component: CrisisDetailComponent },
-      { path: '',     component: CrisisListComponent }
+      {
+        path: '',
+        component: CrisisListComponent,
+        children: [
+          {
+            path: ':id',
+            component: CrisisDetailComponent
+          },
+          {
+            path: '',
+            component: CrisisCenterHomeComponent
+          }
+        ]
+      }
     ]
   }
 ];
 
 export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
-// #enddocregion routes
+// #docregion routes
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.2.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.2.ts
index 07dcf64c81..aab186c878 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.2.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.2.ts
@@ -1,29 +1,65 @@
-// #docregion
+// #docplaster
+// #docregion routes
 import { ModuleWithProviders }   from '@angular/core';
 import { Routes, RouterModule }  from '@angular/router';
 
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisCenterComponent } from './crisis-center.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterComponent }     from './crisis-center.component';
+import { CrisisDetailComponent }     from './crisis-detail.component';
+// #enddocregion routes
 
+// #docregion can-deactivate-guard
+import { CanDeactivateGuard }    from '../can-deactivate-guard.service';
+// #enddocregion can-deactivate-guard
+// #docregion crisis-detail-resolve
+import { CrisisDetailResolve }   from './crisis-detail-resolve.service';
+
+// #enddocregion crisis-detail-resolve
 // #docregion routes
+
 const crisisCenterRoutes: Routes = [
-  // #docregion redirect
+// #enddocregion routes
+  // #docregion redirect, routes
   {
     path: '',
     redirectTo: '/crisis-center',
     pathMatch: 'full'
   },
-  // #enddocregion redirect
+  // #enddocregion redirect, routes
+  // #docregion routes
   {
     path: 'crisis-center',
     component: CrisisCenterComponent,
     children: [
-      { path: ':id',  component: CrisisDetailComponent },
-      { path: '',     component: CrisisListComponent }
+      {
+        path: '',
+        component: CrisisListComponent,
+        children: [
+          {
+            path: ':id',
+            component: CrisisDetailComponent,
+  // #enddocregion routes
+            // #docregion can-deactivate-guard
+            canDeactivate: [CanDeactivateGuard],
+            // #enddocregion can-deactivate-guard
+            // #docregion crisis-detail-resolve
+            resolve: {
+              crisis: CrisisDetailResolve
+            }
+            // #enddocregion crisis-detail-resolve
+  // #docregion routes
+          },
+          {
+            path: '',
+            component: CrisisCenterHomeComponent
+          }
+        ]
+      }
     ]
   }
+  // #docregion routes
 ];
 
 export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
-// #enddocregion routes
+// #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.3.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.3.ts
index 77cddebf0e..e43119d517 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.3.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.3.ts
@@ -3,11 +3,12 @@
 import { ModuleWithProviders }   from '@angular/core';
 import { Routes, RouterModule }  from '@angular/router';
 
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisAdminComponent }  from './crisis-admin.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterComponent }     from './crisis-center.component';
+import { CrisisDetailComponent }     from './crisis-detail.component';
 
+// #docregion can-deactivate-guard
 import { CanDeactivateGuard }    from '../can-deactivate-guard.service';
 
 const crisisCenterRoutes: Routes = [
@@ -20,20 +21,20 @@ const crisisCenterRoutes: Routes = [
     path: 'crisis-center',
     component: CrisisCenterComponent,
     children: [
-      // #docregion admin-route-no-guard
-      {
-        path: 'admin',
-        component: CrisisAdminComponent
-      },
-      // #enddocregion admin-route-no-guard
-      {
-        path: ':id',
-        component: CrisisDetailComponent,
-        canDeactivate: [CanDeactivateGuard]
-      },
       {
         path: '',
-        component: CrisisListComponent
+        component: CrisisListComponent,
+        children: [
+          {
+            path: ':id',
+            component: CrisisDetailComponent,
+            canDeactivate: [CanDeactivateGuard]
+          },
+          {
+            path: '',
+            component: CrisisCenterHomeComponent
+          }
+        ]
       }
     ]
   }
@@ -41,15 +42,3 @@ const crisisCenterRoutes: Routes = [
 
 export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
 // #enddocregion
-
-/*
-// #docregion auth-guard
-import { AuthGuard }             from '../auth.guard';
-
-{
-  path: 'admin',
-  component: CrisisAdminComponent,
-  canActivate: [AuthGuard]
-}
-// #enddocregion auth-guard
-*/
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.4.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.4.ts
deleted file mode 100644
index e21767ecb6..0000000000
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.4.ts
+++ /dev/null
@@ -1,57 +0,0 @@
-// #docplaster
-// #docregion
-import { ModuleWithProviders }   from '@angular/core';
-import { Routes, RouterModule }  from '@angular/router';
-
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisAdminComponent }  from './crisis-admin.component';
-
-import { CanDeactivateGuard }    from '../can-deactivate-guard.service';
-import { AuthGuard }             from '../auth-guard.service';
-
-const crisisCenterRoutes: Routes = [
-  {
-    path: '',
-    redirectTo: '/crisis-center',
-    pathMatch: 'full'
-  },
-  {
-    path: 'crisis-center',
-    component: CrisisCenterComponent,
-    children: [
-      {
-        path: 'admin',
-        component: CrisisAdminComponent,
-        canActivate: [AuthGuard]
-      },
-      {
-        path: ':id',
-        component: CrisisDetailComponent,
-        canDeactivate: [CanDeactivateGuard]
-      },
-      // #docregion default-route
-      {
-        path: '',
-        component: CrisisListComponent
-      }
-      // #enddocregion default-route
-    ]
-  }
-];
-
-export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
-// #enddocregion
-
-/*
-// #docregion auth-guard
-import { AuthGuard }             from '../auth.guard';
-
-{
-  path: 'admin',
-  component: CrisisAdminComponent,
-  canActivate: [AuthGuard]
-}
-// #enddocregion auth-guard
-*/
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.5.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.5.ts
deleted file mode 100644
index a6fbb5bddf..0000000000
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.5.ts
+++ /dev/null
@@ -1,53 +0,0 @@
-// #docplaster
-// #docregion
-import { ModuleWithProviders }   from '@angular/core';
-import { Routes, RouterModule }  from '@angular/router';
-
-import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisAdminComponent }  from './crisis-admin.component';
-
-import { CanDeactivateGuard }    from '../can-deactivate-guard.service';
-import { AuthGuard }             from '../auth-guard.service';
-// #docregion crisis-detail-resolve
-import { CrisisDetailResolve }   from './crisis-detail-resolve.service';
-
-// #enddocregion crisis-detail-resolve
-
-const crisisCenterRoutes: Routes = [
-  {
-    path: '',
-    redirectTo: '/crisis-center',
-    pathMatch: 'full'
-  },
-  {
-    path: 'crisis-center',
-    component: CrisisCenterComponent,
-    children: [
-      // #docregion admin-route
-      {
-        path: 'admin',
-        component: CrisisAdminComponent,
-        canActivate: [AuthGuard]
-      },
-      // #enddocregion admin-route
-      // #docregion crisis-detail-resolve
-      {
-        path: ':id',
-        component: CrisisDetailComponent,
-        canDeactivate: [CanDeactivateGuard],
-        resolve: {
-          crisis: CrisisDetailResolve
-        }
-      },
-      // #enddocregion crisis-detail-resolve
-      {
-        path: '',
-        component: CrisisListComponent
-      }
-    ]
-  }
-];
-
-export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.ts
index 77bc573718..6b4fccde4d 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-center.routing.ts
@@ -3,49 +3,49 @@
 import { ModuleWithProviders }   from '@angular/core';
 import { Routes, RouterModule }  from '@angular/router';
 
-import { CrisisCenterComponent } from './crisis-center.component';
-import { CrisisDetailComponent } from './crisis-detail.component';
-import { CrisisListComponent }   from './crisis-list.component';
-import { CrisisAdminComponent }  from './crisis-admin.component';
+import { CrisisCenterHomeComponent } from './crisis-center-home.component';
+import { CrisisListComponent }       from './crisis-list.component';
+import { CrisisCenterComponent }     from './crisis-center.component';
+import { CrisisDetailComponent }     from './crisis-detail.component';
 
 import { CanDeactivateGuard }    from '../can-deactivate-guard.service';
-import { AuthGuard }             from '../auth-guard.service';
+
 // #docregion crisis-detail-resolve
 import { CrisisDetailResolve }   from './crisis-detail-resolve.service';
 
-// #enddocregion crisis-detail-resolve
-
-// #docregion lazy-load-crisis-center
 const crisisCenterRoutes: Routes = [
+  // #docregion redirect
   {
     path: '',
+    redirectTo: '/crisis-center',
+    pathMatch: 'full'
+  },
+  // #enddocregion redirect
+  {
+    path: 'crisis-center',
     component: CrisisCenterComponent,
     children: [
-      // #docregion admin-route
-      {
-        path: 'admin',
-        component: CrisisAdminComponent,
-        canActivate: [AuthGuard]
-      },
-      // #enddocregion admin-route
-      // #docregion crisis-detail-resolve
-      {
-        path: ':id',
-        component: CrisisDetailComponent,
-        canDeactivate: [CanDeactivateGuard],
-        resolve: {
-          crisis: CrisisDetailResolve
-        }
-      // #enddocregion crisis-detail-resolve
-      },
       {
         path: '',
-        component: CrisisListComponent
+        component: CrisisListComponent,
+        children: [
+          {
+            path: ':id',
+            component: CrisisDetailComponent,
+            canDeactivate: [CanDeactivateGuard],
+            resolve: {
+              crisis: CrisisDetailResolve
+            }
+          },
+          {
+            path: '',
+            component: CrisisCenterHomeComponent
+          }
+        ]
       }
     ]
   }
 ];
 
 export const crisisCenterRouting: ModuleWithProviders = RouterModule.forChild(crisisCenterRoutes);
-// #enddocregion lazy-load-crisis-center
 // #enddocregion
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail-resolve.service.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail-resolve.service.ts
index d0d6d1f192..b4b92f30cc 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail-resolve.service.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail-resolve.service.ts
@@ -2,7 +2,6 @@
 import { Injectable }             from '@angular/core';
 import { Router, Resolve,
          ActivatedRouteSnapshot } from '@angular/router';
-import { Observable }             from 'rxjs/Observable';
 
 import { Crisis, CrisisService } from './crisis.service';
 
@@ -10,7 +9,7 @@ import { Crisis, CrisisService } from './crisis.service';
 export class CrisisDetailResolve implements Resolve<Crisis> {
   constructor(private cs: CrisisService, private router: Router) {}
 
-  resolve(route: ActivatedRouteSnapshot): Observable<any> | Promise<any> | any {
+  resolve(route: ActivatedRouteSnapshot): Promise<Crisis>|boolean {
     let id = +route.params['id'];
 
     return this.cs.getCrisis(id).then(crisis => {
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.1.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.1.ts
index 9d37453cc1..c23c45ab58 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.1.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.1.ts
@@ -1,12 +1,12 @@
 // #docplaster
 // #docregion
-import { Component, OnInit, OnDestroy } from '@angular/core';
-import { ActivatedRoute, Router }       from '@angular/router';
+import { Component, OnInit,
+         HostBinding, trigger, transition,
+         animate, style, state }          from '@angular/core';
+import { ActivatedRoute, Router, Params } from '@angular/router';
 
 import { Crisis, CrisisService }  from './crisis.service';
 import { DialogService }          from '../dialog.service';
-import { Observable }             from 'rxjs/Observable';
-import { Subscription }           from 'rxjs/Subscription';
 
 @Component({
   // #docregion template
@@ -26,16 +26,47 @@ import { Subscription }           from 'rxjs/Subscription';
   </div>
   `,
   // #enddocregion template
-  styles: ['input {width: 20em}']
+  styles: ['input {width: 20em}'],
+  animations: [
+    trigger('routeAnimation', [
+      state('*',
+        style({
+          opacity: 1,
+          transform: 'translateX(0)'
+        })
+      ),
+      transition('void => *', [
+        style({
+          opacity: 0,
+          transform: 'translateX(-100%)'
+        }),
+        animate('0.2s ease-in')
+      ]),
+      transition('* => void', [
+        animate('0.5s ease-out', style({
+          opacity: 0,
+          transform: 'translateY(100%)'
+        }))
+      ])
+    ])
+  ]
 })
 // #docregion cancel-save
-export class CrisisDetailComponent implements OnInit, OnDestroy {
+export class CrisisDetailComponent implements OnInit {
+  @HostBinding('@routeAnimation') get routeAnimation() {
+    return true;
+  }
+
+  @HostBinding('style.display') get display() {
+    return 'block';
+  }
+
+  @HostBinding('style.position') get position() {
+    return 'absolute';
+  }
 
   crisis: Crisis;
   editName: string;
-  // #enddocregion ngOnDestroy
-  private sub: Subscription;
-  // #enddocregion ngOnDestroy
 
 // #enddocregion cancel-save
   constructor(
@@ -47,9 +78,7 @@ export class CrisisDetailComponent implements OnInit, OnDestroy {
 
   // #docregion ngOnInit
   ngOnInit() {
-    this.sub = this.route
-      .params
-      .subscribe(params => {
+    this.route.params.forEach((params: Params) => {
         let id = +params['id'];
         this.service.getCrisis(id)
           .then(crisis => {
@@ -64,14 +93,6 @@ export class CrisisDetailComponent implements OnInit, OnDestroy {
   }
   // #enddocregion ngOnInit
 
-  // #enddocregion ngOnDestroy
-  ngOnDestroy() {
-    if (this.sub) {
-      this.sub.unsubscribe();
-    }
-  }
-  // #enddocregion ngOnDestroy
-
   // #docregion cancel-save
   cancel() {
     this.gotoCrises();
@@ -84,7 +105,7 @@ export class CrisisDetailComponent implements OnInit, OnDestroy {
   // #enddocregion cancel-save
 
   // #docregion cancel-save-only
-  canDeactivate(): Observable<boolean> | Promise<boolean> | boolean {
+  canDeactivate(): Promise<boolean> | boolean {
     // Allow synchronous navigation (`true`) if no crisis or the crisis is unchanged
     if (!this.crisis || this.crisis.name === this.editName) {
       return true;
@@ -95,15 +116,16 @@ export class CrisisDetailComponent implements OnInit, OnDestroy {
   }
   // #enddocregion cancel-save-only
 
-  // #docregion gotoCrises
+  // #docregion gotoCrises, relative-navigation
   gotoCrises() {
     let crisisId = this.crisis ? this.crisis.id : null;
-    // Pass along the hero id if available
-    // so that the CrisisListComponent can select that hero.
+    // Pass along the crisis id if available
+    // so that the CrisisListComponent can select that crisis.
     // Add a totally useless `foo` parameter for kicks.
-    this.router.navigate(['/crisis-center', { id: crisisId, foo: 'foo' }]);
+    // Relative navigation back to the crises
+    this.router.navigate(['../', { id: crisisId, foo: 'foo' }], { relativeTo: this.route });
   }
-  // #enddocregion gotoCrises
+  // #enddocregion gotoCrises, relative-navigation
 // #docregion cancel-save
 }
 // #enddocregion cancel-save
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.ts
index 303f8c6d43..17ae9ff195 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-detail.component.ts
@@ -1,11 +1,12 @@
 // #docplaster
 // #docregion
-import { Component, OnInit }      from '@angular/core';
+import { Component, OnInit, HostBinding,
+         trigger, transition,
+         animate, style, state }  from '@angular/core';
 import { Router, ActivatedRoute } from '@angular/router';
 
 import { Crisis }         from './crisis.service';
 import { DialogService }  from '../dialog.service';
-import { Observable }     from 'rxjs/Observable';
 
 @Component({
   template: `
@@ -23,10 +24,45 @@ import { Observable }     from 'rxjs/Observable';
     </p>
   </div>
   `,
-  styles: ['input {width: 20em}']
+  styles: ['input {width: 20em}'],
+  // #enddocregion template
+  animations: [
+    trigger('routeAnimation', [
+      state('*',
+        style({
+          opacity: 1,
+          transform: 'translateX(0)'
+        })
+      ),
+      transition('void => *', [
+        style({
+          opacity: 0,
+          transform: 'translateX(-100%)'
+        }),
+        animate('0.2s ease-in')
+      ]),
+      transition('* => void', [
+        animate('0.5s ease-out', style({
+          opacity: 0,
+          transform: 'translateY(100%)'
+        }))
+      ])
+    ])
+  ]
 })
-
 export class CrisisDetailComponent implements OnInit {
+  @HostBinding('@routeAnimation') get routeAnimation() {
+    return true;
+  }
+
+  @HostBinding('style.display') get display() {
+    return 'block';
+  }
+
+  @HostBinding('style.position') get position() {
+    return 'absolute';
+  }
+
   crisis: Crisis;
   editName: string;
 
@@ -34,7 +70,7 @@ export class CrisisDetailComponent implements OnInit {
     private route: ActivatedRoute,
     private router: Router,
     public dialogService: DialogService
-    ) { }
+  ) { }
 
 // #docregion crisis-detail-resolve
   ngOnInit() {
@@ -54,7 +90,7 @@ export class CrisisDetailComponent implements OnInit {
     this.gotoCrises();
   }
 
-  canDeactivate(): Observable<boolean> | Promise<boolean> | boolean {
+  canDeactivate(): Promise<boolean> | boolean {
     // Allow synchronous navigation (`true`) if no crisis or the crisis is unchanged
     if (!this.crisis || this.crisis.name === this.editName) {
       return true;
@@ -67,12 +103,12 @@ export class CrisisDetailComponent implements OnInit {
   // #docregion gotoCrises
   gotoCrises() {
     let crisisId = this.crisis ? this.crisis.id : null;
-    // Pass along the hero id if available
-    // so that the CrisisListComponent can select that hero.
+    // Pass along the crisis id if available
+    // so that the CrisisListComponent can select that crisis.
     // Add a totally useless `foo` parameter for kicks.
     // #docregion gotoCrises-navigate
-    // Absolute link
-    this.router.navigate(['/crisis-center', { id: crisisId, foo: 'foo' }]);
+    // Relative navigation back to the crises
+    this.router.navigate(['../', { id: crisisId, foo: 'foo' }], { relativeTo: this.route });
     // #enddocregion gotoCrises-navigate
   }
   // #enddocregion gotoCrises
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.1.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.1.ts
index 2d1df3df33..80fa3483cd 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.1.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.1.ts
@@ -23,10 +23,12 @@ export class CrisisListComponent implements OnInit, OnDestroy {
   selectedId: number;
   private sub: Subscription;
 
+  // #docregion relative-navigation-ctor
   constructor(
     private service: CrisisService,
     private route: ActivatedRoute,
     private router: Router) {}
+  // #enddocregion relative-navigation-ctor
 
   ngOnInit() {
     this.sub = this.route
@@ -45,7 +47,14 @@ export class CrisisListComponent implements OnInit, OnDestroy {
   // #docregion select
   onSelect(crisis: Crisis) {
     // Absolute link
-    this.router.navigate(['/crisis-center', crisis.id]);
+    this.router.navigate([crisis.id]);
   }
   // #enddocregion select
 }
+// #enddocregion
+
+/*
+// #docregion relative-navigation-router-link
+<a [routerLink]="[crisis.id]">{{ crisis.name }}</a>
+// #enddocregion relative-navigation-router-link
+*/
diff --git a/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.ts b/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.ts
index 7a6dcb2e9e..350867adbc 100644
--- a/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.ts
+++ b/public/docs/_examples/router/ts/app/crisis-center/crisis-list.component.ts
@@ -1,10 +1,9 @@
 // #docplaster
 // #docregion
-import { Component, OnInit, OnDestroy } from '@angular/core';
-import { ActivatedRoute, Router }       from '@angular/router';
+import { Component, OnInit }      from '@angular/core';
+import { ActivatedRoute, Router, Params } from '@angular/router';
 
 import { Crisis, CrisisService } from './crisis.service';
-import { Subscription }          from 'rxjs/Subscription';
 
 @Component({
   template: `
@@ -15,38 +14,38 @@ import { Subscription }          from 'rxjs/Subscription';
         <span class="badge">{{crisis.id}}</span> {{crisis.name}}
       </li>
     </ul>
+
+    <router-outlet></router-outlet>
   `
 })
-export class CrisisListComponent implements OnInit, OnDestroy {
+export class CrisisListComponent implements OnInit {
   crises: Crisis[];
-  private selectedId: number;
-  private sub: Subscription;
+  public selectedId: number;
 
   constructor(
     private service: CrisisService,
     private route: ActivatedRoute,
-    private router: Router) { }
+    private router: Router
+  ) { }
 
-  isSelected(crisis: Crisis) { return crisis.id === this.selectedId; }
+  isSelected(crisis: Crisis) {
+    return crisis.id === this.selectedId;
+  }
 
   ngOnInit() {
-    this.sub = this.route
-      .params
-      .subscribe(params => {
-        this.selectedId = +params['id'];
-        this.service.getCrises()
-          .then(crises => this.crises = crises);
-      });
-  }
-
-  ngOnDestroy() {
-    if (this.sub) {
-      this.sub.unsubscribe();
-    }
+    this.route.params.forEach((params: Params) => {
+      this.selectedId = params['id'];
+      this.service.getCrises()
+        .then(crises => this.crises = crises);
+    });
   }
 
+  // #docregion relative-navigation
   onSelect(crisis: Crisis) {
-    // Navigate with Absolute link
-    this.router.navigate(['/crisis-center', crisis.id]);
+    this.selectedId = crisis.id;
+
+    // Navigate with relative link
+    this.router.navigate([crisis.id], { relativeTo: this.route });
   }
+  // #enddocregion relative-navigation
 }
diff --git a/public/docs/_examples/router/ts/app/heroes/hero-detail.component.1.ts b/public/docs/_examples/router/ts/app/heroes/hero-detail.component.1.ts
index 338b9ce3c4..90d0510bd7 100644
--- a/public/docs/_examples/router/ts/app/heroes/hero-detail.component.1.ts
+++ b/public/docs/_examples/router/ts/app/heroes/hero-detail.component.1.ts
@@ -1,10 +1,11 @@
 // #docplaster
 // #docregion
-import { Component, OnInit, OnDestroy } from '@angular/core';
-import { Router, ActivatedRoute }       from '@angular/router';
+import { Component, OnInit } from '@angular/core';
+// #docregion imports
+import { Router, ActivatedRoute, Params } from '@angular/router';
+// #enddocregion imports
 
 import { Hero, HeroService } from './hero.service';
-import { Subscription } from 'rxjs/Subscription';
 
 @Component({
   template: `
@@ -23,34 +24,26 @@ import { Subscription } from 'rxjs/Subscription';
   </div>
   `
 })
-export class HeroDetailComponent implements OnInit, OnDestroy  {
+export class HeroDetailComponent implements OnInit  {
   hero: Hero;
-  // #docregion ngOnInit
-  private sub: Subscription;
 
-  // #enddocregion ngOnInit
   // #docregion ctor
   constructor(
     private route: ActivatedRoute,
     private router: Router,
-    private service: HeroService) {}
+    private service: HeroService
+  ) {}
   // #enddocregion ctor
 
   // #docregion ngOnInit
   ngOnInit() {
-    this.sub = this.route.params.subscribe(params => {
-       let id = +params['id']; // (+) converts string 'id' to a number
-       this.service.getHero(id).then(hero => this.hero = hero);
-     });
+    this.route.params.forEach((params: Params) => {
+      let id = +params['id']; // (+) converts string 'id' to a number
+      this.service.getHero(id).then(hero => this.hero = hero);
+    });
   }
   // #enddocregion ngOnInit
 
-  // #docregion ngOnDestroy
-  ngOnDestroy() {
-    this.sub.unsubscribe();
-  }
-  // #enddocregion ngOnDestroy
-
   // #docregion gotoHeroes
   gotoHeroes() { this.router.navigate(['/heroes']); }
   // #enddocregion gotoHeroes
diff --git a/public/docs/_examples/router/ts/app/heroes/hero-detail.component.ts b/public/docs/_examples/router/ts/app/heroes/hero-detail.component.ts
index 20b851ae6e..a263fe65f0 100644
--- a/public/docs/_examples/router/ts/app/heroes/hero-detail.component.ts
+++ b/public/docs/_examples/router/ts/app/heroes/hero-detail.component.ts
@@ -1,11 +1,15 @@
 // #docplaster
 // #docregion
-import { Component, OnInit, OnDestroy } from '@angular/core';
-import { Router, ActivatedRoute }       from '@angular/router';
+// #docregion route-animation-imports
+import { Component, OnInit, HostBinding,
+         trigger, transition, animate,
+         style, state } from '@angular/core';
+// #enddocregion route-animation-imports
+import { Router, ActivatedRoute, Params } from '@angular/router';
 
 import { Hero, HeroService }  from './hero.service';
-import { Subscription }       from 'rxjs/Subscription';
 
+// #docregion route-animation
 @Component({
   template: `
   <h2>HEROES</h2>
@@ -21,15 +25,48 @@ import { Subscription }       from 'rxjs/Subscription';
       <button (click)="gotoHeroes()">Back</button>
     </p>
   </div>
-  `
+  `,
+  animations: [
+    trigger('routeAnimation', [
+      state('*',
+        style({
+          opacity: 1,
+          transform: 'translateX(0)'
+        })
+      ),
+      transition('void => *', [
+        style({
+          opacity: 0,
+          transform: 'translateX(-100%)'
+        }),
+        animate('0.2s ease-in')
+      ]),
+      transition('* => void', [
+        animate('0.5s ease-out', style({
+          opacity: 0,
+          transform: 'translateY(100%)'
+        }))
+      ])
+    ])
+  ]
 })
-export class HeroDetailComponent implements OnInit, OnDestroy  {
+// #docregion route-animation-host-binding
+export class HeroDetailComponent implements OnInit {
+// #enddocregion route-animation
+  @HostBinding('@routeAnimation') get routeAnimation() {
+    return true;
+  }
+
+  @HostBinding('style.display') get display() {
+    return 'block';
+  }
+
+  @HostBinding('style.position') get position() {
+    return 'absolute';
+  }
+
   hero: Hero;
 
-  // #docregion ngOnInit
-  private sub: Subscription;
-
-  // #enddocregion ngOnInit
   // #docregion ctor
   constructor(
     private route: ActivatedRoute,
@@ -39,19 +76,13 @@ export class HeroDetailComponent implements OnInit, OnDestroy  {
 
   // #docregion ngOnInit
   ngOnInit() {
-    this.sub = this.route.params.subscribe(params => {
+    this.route.params.forEach((params: Params) => {
        let id = +params['id']; // (+) converts string 'id' to a number
        this.service.getHero(id).then(hero => this.hero = hero);
      });
   }
   // #enddocregion ngOnInit
 
-  // #docregion ngOnDestroy
-  ngOnDestroy() {
-    this.sub.unsubscribe();
-  }
-  // #enddocregion ngOnDestroy
-
   // #docregion gotoHeroes-navigate
   gotoHeroes() {
     let heroId = this.hero ? this.hero.id : null;
@@ -60,4 +91,6 @@ export class HeroDetailComponent implements OnInit, OnDestroy  {
     this.router.navigate(['/heroes', { id: heroId, foo: 'foo' }]);
   }
   // #enddocregion gotoHeroes-navigate
+// #docregion route-animation-host-binding
 }
+// #enddocregion route-animation-host-binding
diff --git a/public/docs/_examples/router/ts/app/heroes/hero-list.component.ts b/public/docs/_examples/router/ts/app/heroes/hero-list.component.ts
index 831f24adc4..068c9680d0 100644
--- a/public/docs/_examples/router/ts/app/heroes/hero-list.component.ts
+++ b/public/docs/_examples/router/ts/app/heroes/hero-list.component.ts
@@ -1,13 +1,12 @@
 // #docplaster
 // #docregion
 // TODO SOMEDAY: Feature Componetized like CrisisCenter
-import { Component, OnInit, OnDestroy } from '@angular/core';
+import { Component, OnInit } from '@angular/core';
 // #docregion import-router
-import { Router, ActivatedRoute } from '@angular/router';
+import { Router, ActivatedRoute, Params } from '@angular/router';
 // #enddocregion import-router
 
 import { Hero, HeroService }  from './hero.service';
-import { Subscription }       from 'rxjs/Subscription';
 
 @Component({
   // #docregion template
@@ -23,32 +22,26 @@ import { Subscription }       from 'rxjs/Subscription';
   `
   // #enddocregion template
 })
-export class HeroListComponent implements OnInit, OnDestroy {
+export class HeroListComponent implements OnInit {
   heroes: Hero[];
 
   // #docregion ctor
   private selectedId: number;
-  private sub: Subscription;
 
   constructor(
     private service: HeroService,
     private route: ActivatedRoute,
-    private router: Router) {}
+    private router: Router
+  ) {}
   // #enddocregion ctor
 
   ngOnInit() {
-    this.sub = this.route
-      .params
-      .subscribe(params => {
+    this.route.params.forEach((params: Params) => {
         this.selectedId = +params['id'];
         this.service.getHeroes()
           .then(heroes => this.heroes = heroes);
       });
   }
-
-  ngOnDestroy() {
-    this.sub.unsubscribe();
-  }
   // #enddocregion ctor
 
   // #docregion isSelected
diff --git a/public/docs/_examples/router/ts/app/login.component.ts b/public/docs/_examples/router/ts/app/login.component.ts
index 6dd5605fb1..41c88f4068 100755
--- a/public/docs/_examples/router/ts/app/login.component.ts
+++ b/public/docs/_examples/router/ts/app/login.component.ts
@@ -32,7 +32,7 @@ export class LoginComponent {
       if (this.authService.isLoggedIn) {
         // Get the redirect URL from our auth service
         // If no redirect has been set, use the default
-        let redirect = this.authService.redirectUrl ? this.authService.redirectUrl : '/crisis-center/admin';
+        let redirect = this.authService.redirectUrl ? this.authService.redirectUrl : '/admin';
 
         // #docregion preserve
         // Set our navigation extras object
diff --git a/public/docs/ts/latest/guide/_data.json b/public/docs/ts/latest/guide/_data.json
index 97c35aa8fb..2bd99c1ca6 100644
--- a/public/docs/ts/latest/guide/_data.json
+++ b/public/docs/ts/latest/guide/_data.json
@@ -122,7 +122,7 @@
 
   "router": {
     "title": "Routing & Navigation",
-    "intro": "Discover the basics of screen navigation with the Angular 2 Component Router."
+    "intro": "Discover the basics of screen navigation with the Angular 2 Router."
   },
 
   "security": {
diff --git a/public/docs/ts/latest/guide/router.jade b/public/docs/ts/latest/guide/router.jade
index 64d712697e..0af9b5d1d3 100644
--- a/public/docs/ts/latest/guide/router.jade
+++ b/public/docs/ts/latest/guide/router.jade
@@ -1,7 +1,7 @@
 include ../_util-fns
 
 :marked
-  The Angular ***Component Router*** enables navigation from one [view](./glossary.html#view) to the next
+  The Angular ***Router*** enables navigation from one [view](./glossary.html#view) to the next
   as users perform application tasks.
 
   We cover the router's primary features in this chapter, illustrating them through the evolution
@@ -22,7 +22,7 @@ include ../_util-fns
   We click the browser's back and forward buttons and the browser navigates
   backward and forward through the history of pages we've seen.
 
-  The Angular ***Component Router*** ("the router") borrows from this model.
+  The Angular ***Router*** ("the router") borrows from this model.
   It can interpret a browser URL as an instruction
   to navigate to a client-generated view and pass optional parameters along to the supporting view component
   to help it decide what specific content to present.
@@ -40,15 +40,21 @@ include ../_util-fns
   * the [link parameters array](#link-parameters-array) that propels router navigation
   * navigating when the user clicks a data-bound [RouterLink](#router-link)
   * navigating under [program control](#navigate)
+  * retrieving information from the [route](#activated-route)
+  * [animating](#route-animation) transitions for route components
+  * navigating [relative](#relative-navigation) to our current URL
   * toggling css classes for the [active router link](#router-link-active)
   * embedding critical information in the URL with [route parameters](#route-parameters)
   * providing non-critical information in [optional route parameters](#optional-route-parameters)
   * add [child routes](#child-routing-component) under a feature section
+  * [grouping child routes](#component-less-route) without a component
   * [redirecting](#redirect) from one route to another
   * confirming or canceling navigation with [guards](#guards)
     * [CanActivate](#can-activate-guard) to prevent navigation to a route
+    * [CanActivateChild](#can-activate-child-guard) to prevent navigation to a child route
     * [CanDeactivate](#can-deactivate-guard) to prevent navigation away from the current route
     * [Resolve](#resolve-guard) to pre-fetch data before activating a route
+    * [CanLoad](#can-load-guard) to prevent asynchronous routing
   * providing optional information across routes with [query parameters](#query-parameters)
   * jumping to anchor elements using a [fragment](#fragment)
   * loading feature areas [asynchronously](#asynchronous-routing)
@@ -62,7 +68,7 @@ include ../_util-fns
 .l-main-section
 :marked
   ## The Basics
-  Let's begin with a few core concepts of the Component Router.
+  Let's begin with a few core concepts of the Router.
   Then we can explore the details through a sequence of examples.
 
 :marked
@@ -77,7 +83,7 @@ include ../_util-fns
 
 :marked
   ### Router imports
-  The Angular Component Router is an optional service that presents a particular component view for a given URL.
+  The Angular Router is an optional service that presents a particular component view for a given URL.
   It is not part of the Angular 2 core. It is in its own library package, `@angular/router`.
   We import what we need from it as we would from any other Angular package.
 
@@ -106,23 +112,32 @@ include ../_util-fns
     There are no **leading slashes** in our **path**. The router parses and builds the URL for us,
     allowing us to use relative and absolute paths when navigating between application views.
 
-    The `data` property in the second route is a place to store arbitrary data associated with each
-    specific route. This data is accessible within each activated route and can be used to store
-    items such as page titles, breadcrumb text and other read-only data. We'll use the [resolve guard](#resolve-guard)
-    to retrieve additional data later in the chapter.
-
-    The `:id` in the third route is a token for a route parameter. In a URL such as `/hero/42`, "42"
+    The `:id` in the first route is a token for a route parameter. In a URL such as `/hero/42`, "42"
     is the value of the `id` parameter. The corresponding `HeroDetailComponent`
     will use that value to find and present the hero whose `id` is 42.
     We'll learn more about route parameters later in this chapter.
 
-    The `**` in the fourth route denotes a **wildcard** path for our route. The router will match this route
+    The `data` property in the third route is a place to store arbitrary data associated with each
+    specific route. This data is accessible within each activated route and can be used to store
+    items such as page titles, breadcrumb text and other read-only data. We'll use the [resolve guard](#resolve-guard)
+    to retrieve additional data later in the chapter.
+
+    The `empty path` in the fourth route matches as the default path for each level of routing. It
+    also allows for adding routes without extending the URL path.
+
+    The `**` in the last route denotes a **wildcard** path for our route. The router will match this route
     if the URL requested doesn't match any paths for routes defined in our configuration. This is useful for
     displaying a 404 page or redirecting to another route.
 
+    **The order of the routes in the configuration matters** and this is by design. The router uses a **first-match wins**
+    strategy when matching routes, so more specific routes should be placed above less specific routes. In our
+    configuration above, the routes with a static path are listed first, followed by an empty path route,
+    that matches as the default route. The wildcard route is listed last as it's the most generic route and should be
+    matched **only** if no other routes are matched first.
+
 :marked
     We export the `routing` constant so we can import it into our `app.module.ts` file where we'll add
-    a configured *Router* module to our root NgModule imports.
+    a configured *Router* module to our `AppModule` imports.
 :marked
   Next we open `app.module.ts` where we must register our routing, routing providers, and declare our two route components.
 
@@ -170,6 +185,7 @@ code-example(language="html").
    We define `active` as the CSS class we want toggled to each `RouterLink` when they become
    the current route using the `RouterLinkActive ` directive. We could add multiple classes to
    the `RouterLink` if we so desired.
+
 :marked
   ### Router State
   After the end of each successful navigation lifecycle, the router builds a tree of `ActivatedRoute` objects
@@ -186,7 +202,7 @@ code-example(language="html").
   The component has a `RouterOutlet` where it can display views produced by the router.
   It has `RouterLink`s that users can click to navigate via the router.
 
-  Here are the key *Component Router* terms and their meanings:
+  Here are the key *Router* terms and their meanings:
 table
   tr
     th Router Part
@@ -269,9 +285,10 @@ table
   Our client is the Hero Employment Agency.
   Heroes need work and The Agency finds Crises for them to solve.
 
-  The application has two main feature areas:
+  The application has three main feature areas:
   1. A *Crisis Center* where we maintain the list of crises for assignment to heroes.
   1. A *Heroes* area where we maintain the list of heroes employed by The Agency.
+  1. An *Admin* area where we manage the list of crises and heroes displayed.
 
   Run the <live-example></live-example>.
   It opens in the *Crisis Center*.  We'll come back to that.
@@ -299,14 +316,14 @@ figure.image-display
 figure.image-display
   img(src='/resources/images/devguide/router/crisis-center-detail.png' alt="Crisis Center Detail")
 :marked
-   This is a bit different from the *Hero Detail*. *Hero Detail* saves the changes as we type.
-   In *Crisis Detail* our changes are temporary until we either save or discard them by pressing the "Save" or "Cancel" buttons.
-   Both buttons navigate back to the *Crisis Center* and its list of crises.
+  This is a bit different from the *Hero Detail*. *Hero Detail* saves the changes as we type.
+  In *Crisis Detail* our changes are temporary until we either save or discard them by pressing the "Save" or "Cancel" buttons.
+  Both buttons navigate back to the *Crisis Center* and its list of crises.
 
-   Suppose we click a crisis, make a change, but ***do not click either button***.
-   Maybe we click the browser back button instead. Maybe we click the "Heroes" link.
+  Suppose we click a crisis, make a change, but ***do not click either button***.
+  Maybe we click the browser back button instead. Maybe we click the "Heroes" link.
 
-   Do either. Up pops a dialog box.
+  Do either. Up pops a dialog box.
 figure.image-display
   img(src='/resources/images/devguide/router/confirm-dialog.png' alt="Confirm Dialog" width="300")
 :marked
@@ -331,9 +348,11 @@ figure.image-display
   * including a route parameter (passing the Hero `id` while routing to the "Hero Detail")
   * child routes (the *Crisis Center* has its own routes)
   * the `CanActivate` guard (checking route access)
+  * the `CanActivateChild` guard (checking child route access)
   * the `CanDeactivate` guard (ask permission to discard unsaved changes)
   * the `Resolve` guard (pre-fetching route data)
-  * lazy loading feature area modules
+  * lazy loading feature modules
+  * the `CanLoad` guard (check before loading feature module assets)
 
 <a id="getting-started"></a>
 .l-main-section
@@ -347,7 +366,7 @@ figure.image-display
 a#base-href
 :marked
   ### Set the *&lt;base href>*
-  The Component Router uses the browser's
+  The Router uses the browser's
   [history.pushState](https://developer.mozilla.org/en-US/docs/Web/API/History_API#Adding_and_modifying_history_entries)
   for navigation. Thanks to `pushState`, we can make our in-app URL paths look the way we want them to
   look, e.g. `localhost:3000/crisis-center`. Our in-app URLs can be indistinguishable from server URLs.
@@ -368,7 +387,7 @@ a#base-href
 
 .l-sub-section
   :marked
-    HTML 5 style navigation is the Component Router default.
+    HTML 5 style navigation is the Router default.
     Learn why "HTML 5" style is preferred, how to adjust its behavior, and how to switch to the
     older hash (#) style if necessary in the [Browser URL Styles](#browser-url-styles) appendix below.
 
@@ -389,19 +408,13 @@ a#base-href
 
   We begin by importing some symbols from the router library.
 
-  The Component Router is in its own `@angular/router` package.
+  The Router is in its own `@angular/router` package.
   It's not part of the Angular 2 core. The router is an optional service because not all applications
   need routing and, depending on your requirements, you may need a different routing library.
 
   We teach our router how to navigate by configuring it with routes.
   We recommend creating a separate `app.routing.ts` file dedicated to this purpose.
-.l-sub-section
-  :marked
-    Defining configuration in a separate file paves the way for a future
-    in which we load routing configuration immediately but *delay
-    loading the components themselves* until the user needs them.
 
-    Such [*asynchronous routing*](#asynchronous-routing) can make our application launch more quickly.
 :marked
   Here is our first configuration. We pass the array of routes to the `RouterModule.forRoot` method
   which returns a module containing the configured `Router` service provider ... and some other,
@@ -442,21 +455,21 @@ h4#define-routes Define routes
   :marked
     Learn about *providers* in the [Dependency Injection](dependency-injection.html#!#injector-providers) chapter.
 
-h4#register-providers Register routing in the root NgModule
+h4#register-providers Register routing in the AppModule
 :marked
   Our app launches from the `app.module.ts` file in the `/app` folder.
 
   We import the `routing` token we exported from the `app.routing.ts` file and add it to the `imports` array.
 
   We import our `CrisisListComponent` and `HeroListComponent` components and add them to our *declarations*
-  so they will be registered within our root NgModule.
+  so they will be registered within our `AppModule`.
 
   We also import the `appRoutingProviders` array and add it to the `providers` array.
 
 +makeExcerpt('app/app.module.1.ts')
 
 :marked
-  Providing the router module in our root NgModule makes the Router available everywhere in our application.
+  Providing the router module in our `AppModule` makes the Router available everywhere in our application.
 
 h3#shell The <i>AppComponent</i> shell
 :marked
@@ -488,7 +501,7 @@ a#router-link
   ### *RouterLink* binding
 
   Above the outlet, within the anchor tags, we see [Property Bindings](template-syntax.html#property-binding) to
-  the `RouterLink` directive that look like `routerLink="..."`. We imported `RouterLink` from the router library.
+  the `RouterLink` directive that look like `routerLink="..."`. We use the `RouterLink` from the router library.
 
   The links in this example each have a string path, the path of a route that
   we configured earlier. We don't have route parameters yet.
@@ -589,7 +602,7 @@ h3#router-directives <i>Router Directives</i>
   Now we'll learn some new tricks such as how to
   * organize our app and routes into *feature areas* using modules
   * navigate imperatively from one component to another
-  * pass information in route parameters
+  * pass required and optional information in route parameters
 
   To demonstrate, we'll build out the *Heroes* feature.
 
@@ -614,7 +627,7 @@ figure.image-display
 :marked
   ### Add Heroes functionality
 
-  We want to break our app out into different *submodules* that we then import
+  We want to break our app out into different *feature modules* that we then import
   into our main module so it can make use of them. First, we'll create a `heroes.module.ts`
   in our heroes folder.
 
@@ -672,16 +685,20 @@ figure.image-display
   We use the same techniques we learned for `app.routing.ts`.
 
   We import the two components from their new locations in the `app/heroes/` folder, define the two hero routes.
-  and add export our `heroesRouting` that returns configured `RouterModule` for our submodule.
+  and add export our `heroesRouting` that returns configured `RouterModule` for our feature module.
 
 :marked
   Now that we have routes for our `Heroes` module, we'll need to register them with the *Router*.
-  We'll import the *RouterModule* like we did in the root NgModule, but there is a slight difference here.
-  In our root routing setup, we used the static **forRoot** method to register our routes and application level
-  service providers. Since we are in a submodule, we'll use **Router.forChild** method to only register additional routes. We do this
-  because the *Router* will combine all the provided routes from the submodule together and build our configuration. This allows us to continue defining
-  our feature-specific routes without modifying our main route configuration.
+  We'll import the *RouterModule* like we did in the `app.routing.ts`, but there is a slight difference here.
+  In our `app.routing.ts`, we used the static **forRoot** method to register our routes and application level
+  service providers. In a feature module we use static **forChild** method.
 
+.l-sub-section
+  :marked
+    The **RouterModule.forRoot** should only be provided for the `AppModule`. Since we are in a feature
+    module, we'll use **RouterModule.forChild** method to only register additional routes.
+
+:marked
   We import our `heroesRouting` token from `heroes.routing.ts` into our `Heroes` module and register the routing.
 
 +makeExcerpt('app/heroes/heroes.module.ts (heroes routing)', 'heroes-routes')
@@ -690,7 +707,7 @@ figure.image-display
   ### Route definition with a parameter
   The route to `HeroDetailComponent` has a twist.
 
-+makeExcerpt('app/heroes/heroes.routing.ts (excerpt)', 'hero-detail-route', '')
++makeExcerpt('app/heroes/heroes.routing.ts (excerpt)', 'hero-detail-route')
 
 :marked
   Notice the `:id` token in the path. That creates a slot in the path for a **Route Parameter**.
@@ -738,7 +755,7 @@ a#navigate
   There's a `(click)` [EventBinding](template-syntax.html#event-binding) to the component's `onSelect` method
   which we implement as follows:
 
-+makeExcerpt('app/heroes/hero-list.component.1.ts', 'select', '')
++makeExcerpt('app/heroes/hero-list.component.1.ts', 'select')
 
 :marked
   It calls the router's **`navigate`** method with a **Link Parameters Array**. We can use this same syntax
@@ -752,7 +769,7 @@ h3#route-parameters Setting the route parameters in the list view
   Accordingly, the *link parameters array* has *two* items:  the **path** of the destination route and a **route parameter** that specifies the
   `id` of the selected hero.
 
-+makeExcerpt('app/heroes/hero-list.component.1.ts', 'link-parameters-array', '')
++makeExcerpt('app/heroes/hero-list.component.1.ts', 'link-parameters-array')
 
 :marked
   The router composes the appropriate two-part destination URL from this array:
@@ -760,7 +777,7 @@ h3#route-parameters Setting the route parameters in the list view
 code-example(language="bash").
   localhost:3000/hero/15
 
-a#get-route-parameter 
+a#get-route-parameter
 :marked
   ### Getting the route parameter in the details view
 
@@ -770,6 +787,42 @@ a#get-route-parameter
   The router extracts the route parameter (`id:15`) from the URL and supplies it to
   the `HeroDetailComponent` via the **ActivatedRoute** service.
 
+<a id="activated-route"></a>
+h3#activated-route ActivatedRoute: the one-stop-shop for route information
+:marked
+  Each route contains information about its path, data parameters, URL segment and much more.
+  All of this information is available in an injected service provided by the router called the [ActivatedRoute](../api/router/index/ActivatedRoute-interface.html).
+
+  The `ActivatedRoute` contains all the information you need from the current route component as well as ways to get information
+  about other activated routes in the `RouterState`.
+
+.l-sub-section
+  :marked
+    **`url`**: An `Observable` of the route path(s). The value is provided as an array of strings for each part of the route path.
+
+    **`data`**: An `Observable` that contains the `data` object provided for the route. Also contains any resolved values from the [resolve guard](#resolve-guard).
+
+    **`params`**: An `Observable` that contains the required and [optional parameters](#optional-route-parameters) specific to the route.
+
+    **`queryParams`**: An `Observable` that contains the [query parameters](#query-parameters) available to all routes.
+
+    **`fragment`**:  An `Observable` of the URL [fragment](#fragment) available to all routes.
+
+    **`outlet`**: The name of the `RouterOutlet` used to render the route. For an unnamed outlet, the outlet name is **primary**.
+
+    **`routeConfig`**: The route configuration used for the route that contains the origin path.
+
+    **`parent`**: an `ActivatedRoute` that contains the information from the parent route when using [child routes](#child-routing-component).
+
+    **`firstChild`**: contains the first `ActivatedRoute` in the list of child routes.
+
+    **`children`**: contains all the [child routes](#child-routing-component) activated under the current route.
+
+:marked
+  We import the `Router`, `ActivatedRoute`, and `Params` tokens from the router package.
+
++makeExcerpt('app/heroes/hero-detail.component.1.ts (activated route)', 'imports')
+
 a#hero-detail-ctor
 :marked
   As usual, we write a constructor that asks Angular to inject services
@@ -780,11 +833,10 @@ a#hero-detail-ctor
 :marked
   Later, in the `ngOnInit` method,
   we use the `ActivatedRoute` service to retrieve the parameters for our route.
-  Since our parameters are provided as an `Observable`, we _subscribe_ to them for the `id` parameter by name and
-  tell the `HeroService` to fetch the hero with that `id`. We'll keep a reference to this `Subscription` so we can
-  tidy things up later.
+  Since our parameters are provided as an `Observable`, we use the _forEach_ method to retrieve them for the `id` parameter by name and
+  tell the `HeroService` to fetch the hero with that `id`.
 
-+makeExcerpt('app/heroes/hero-detail.component.ts', 'ngOnInit', '')
++makeExcerpt('app/heroes/hero-detail.component.ts (ngOnInit)', 'ngOnInit')
 
 .l-sub-section
   :marked
@@ -794,25 +846,14 @@ a#hero-detail-ctor
     to improve the component's testability.
     We explore this point in greater detail in the [OnInit appendix](#onInit) below.
 
-:marked
-  Eventually, we'll navigate somewhere else.
-  The router will remove this component from the DOM and destroy it.
-  We need to clean up after ourselves before that happens.
-  Specifically, we **must unsubscribe** before Angular destroys the component.
-  *Failure to do so could create a memory leak.*
-
-  We unsubscribe from our `Observable` in the `ngOnDestroy` method.
-
-+makeExcerpt('app/heroes/hero-detail.component.ts', 'ngOnDestroy', '')
-
 .l-sub-section
   :marked
-    Learn about the `ngOnInit` and `ngOnDestroy` methods in the
+    Learn about the `ngOnInit` method in the
     [Lifecycle Hooks](lifecycle-hooks.html) chapter.
 
 h4#reuse Observable <i>params</i> and component re-use
 :marked
-  In this example, we subscribe to the route params `Observable`.
+  In this example, we retrieve the route params from an `Observable`.
   That implies that the route params can change during the lifetime of this component.
 
   They might. By default, the router reuses a component instance when it re-navigates to the same component type
@@ -843,10 +884,10 @@ h4#snapshot <i>Snapshot</i>: the no-observable alternative
   be re-used. We'll always re-create the component each time we navigate to it.
 
   The router offers a *Snapshot* alternative that gives us the initial value of the route parameters.
-  We don't need to subscribe. We don't have to unsubscribe in `ngOnDestroy`.
+  We don't need to subscribe or unsubscribe.
   It's much simpler to write and read:
 
-+makeExcerpt('app/heroes/hero-detail.component.2.ts (excerpt)', 'snapshot', '')
++makeExcerpt('app/heroes/hero-detail.component.2.ts (ngOnInit snapshot)', 'snapshot')
 
 .l-sub-section
   :marked
@@ -866,29 +907,245 @@ a#nav-to-list
   that we can bind to a `[routerLink]` directive.
   It holds the **path to the `HeroListComponent`**:
 
-+makeExcerpt('app/heroes/hero-detail.component.1.ts (excerpt)', 'gotoHeroes', '')
++makeExcerpt('app/heroes/hero-detail.component.1.ts (excerpt)', 'gotoHeroes')
 
-h3#merge-hero-routes Import hero module into root NgModule
+.l-main-section#optional-route-parameters
 :marked
-  Our heroes feature is ready, but application doesn't know about our heroes module yet.
-  We'll need to import it into the root NgModule we defined in `app.module.ts`.
+  ### Route Parameters
+
+  We use [*route parameters*](#route-parameters) to specify a *required* parameter value *within* the route URL
+  as we do when navigating to the `HeroDetailComponent` in order to view-and-edit the hero with *id:15*.
+code-example(format="." language="bash").
+  localhost:3000/hero/15
+:marked
+  Sometimes we wish to add *optional* information to a route request.
+  For example, the `HeroListComponent` doesn't need help to display a list of heroes.
+  But it might be nice if the previously-viewed hero were pre-selected when returning from the `HeroDetailComponent`.
+figure.image-display
+  img(src='/resources/images/devguide/router/selected-hero.png' alt="Selected hero")
+:marked
+  That becomes possible if we can include hero Magneta's `id` in the URL when we
+  return from the `HeroDetailComponent`, a scenario we'll pursue in a moment.
+
+  Optional information takes other forms. Search criteria are often loosely structured, e.g., `name='wind*'`.
+  Multiple values are common &mdash; `after='12/31/2015' & before='1/1/2017'` &mdash; in no particular order &mdash;
+   `before='1/1/2017' & after='12/31/2015'` &mdash; in a variety of formats &mdash; `during='currentYear'` .
+
+  These kinds of parameters don't fit easily in a URL *path*. Even if we could define a suitable URL token scheme,
+  doing so greatly complicates the pattern matching required to translate an incoming URL to a named route.
+
+  Optional parameters are the ideal vehicle for conveying arbitrarily complex information during navigation.
+  Optional parameters aren't involved in pattern matching and affords enormous flexibility of expression.
+
+  The Router supports navigation with optional parameters as well as required route parameters.
+  We define _optional_ parameters in an *object* after we define our required route parameters.
+
+  ### Route Parameters: Required or Optional?
+
+  There is no hard-and-fast rule. In general,
+
+  *prefer a required route parameter when*
+  * the value is required.
+  * the value is necessary to distinguish one route path from another.
+
+  *prefer an optional parameter when*
+  * the value is optional, complex, and/or multi-variate.
+
+  <a id="route-parameters-object"></a>
+  ### Route parameter
+
+  When navigating to the `HeroDetailComponent` we specified the _required_ `id` of the hero-to-edit in the
+  *route parameter* and made it the second item of the [*link parameters array*](#link-parameters-array).
+
++makeExcerpt('app/heroes/hero-list.component.1.ts', 'link-parameters-array')
+
+:marked
+  The router embedded the `id` value in the navigation URL because we had defined it
+  as a route parameter with an `:id` placeholder token in the route `path`:
+
++makeExcerpt('app/heroes/heroes.routing.ts', 'hero-detail-route')
+
+:marked
+  When the user clicks the back button, the `HeroDetailComponent` constructs another *link parameters array*
+  which it uses to navigate back to the `HeroListComponent`.
+
++makeExcerpt('app/heroes/hero-detail.component.1.ts', 'gotoHeroes')
+
+:marked
+  This array lacks a route parameter because we had no reason to send information to the `HeroListComponent`.
+
+  Now we have a reason. We'd like to send the id of the current hero with the navigation request so that the
+  `HeroListComponent` can highlight that hero in its list. 
+  This is a _nice-to-have_ feature; the list will display perfectly well without it.
+
+  We do that with an object that contains an _optional_ `id` parameter.
+  For demonstration purposes, we also defined a junk parameter (`foo`) that the `HeroListComponent` should ignore.
+  Here's the revised navigation statement:
+
++makeExcerpt('app/heroes/hero-detail.component.ts (go to heroes)', 'gotoHeroes-navigate')
+
+:marked
+  The application still works. Clicking "back" returns to the hero list view.
+
+  Look at the browser address bar.
+.l-sub-section
+  img(src='/resources/images/devguide/plunker-separate-window-button.png' alt="pop out the window" align="right" style="margin-right:-20px")
+  :marked
+    When running in plunker, pop out the preview window by clicking the blue 'X' button in the upper right corner.
+:marked
+ It should look something like this, depending on where you run it:
+
+code-example(language="bash").
+  localhost:3000/heroes;id=15;foo=foo
+
+:marked
+  The `id` value appears in the URL as (`;id=15;foo=foo`), not in the URL path.
+  The path for the "Heroes" route doesn't have an `:id` token.
+
+  The optional route parameters are not separated by "?" and "&" as they would be in the URL query string.
+  They are **separated by semicolons ";"**
+  This is *matrix URL* notation &mdash; something we may not have seen before.
+
+.l-sub-section
+  :marked
+    *Matrix URL* notation is an idea first floated
+    in a [1996 proposal](http://www.w3.org/DesignIssues/MatrixURIs.html) by the founder of the web, Tim Berners-Lee.
+
+    Although matrix notation never made it into the HTML standard, it is legal and
+    it became popular among browser routing systems as a way to isolate parameters
+    belonging to parent and child routes. The Router is such a system and provides
+    support for the matrix notation across browsers.
+
+    The syntax may seem strange to us but users are unlikely to notice or care
+    as long as the URL can be emailed and pasted into a browser address bar
+    as this one can.
+
+:marked
+  ### Route parameters in the *ActivatedRoute* service
+
+  The list of heroes is unchanged. No hero row is highlighted.
+
+.l-sub-section
+  :marked
+    The <live-example></live-example> *does* highlight the selected
+    row because it demonstrates the final state of the application which includes the steps we're *about* to cover.
+    At the moment we're describing the state of affairs *prior* to those steps.
+:marked
+  The `HeroListComponent` isn't expecting any parameters at all and wouldn't know what to do with them.
+  Let's change that.
+
+  Previously, when navigating from the `HeroListComponent` to the `HeroDetailComponent`,
+  we subscribed to the route params `Observable` and made it available to the `HeroDetailComponent`
+  in the `ActivatedRoute` service. We injected that service in the constructor of the `HeroDetailComponent`.
+
+  This time we'll be navigating in the opposite direction, from the `HeroDetailComponent` to the `HeroListComponent`.
+
+  First we extend the router import statement to include the `ActivatedRoute` service symbol;
+
++makeExcerpt('app/heroes/hero-list.component.ts (import)', 'import-router')
+
+:marked
+  Then we use the `ActivatedRoute` to access the `params` _Observable_ so we can subscribe
+  and extract the `id` parameter as the `selectedId`:
+
++makeExcerpt('app/heroes/hero-list.component.ts (constructor)', 'ctor')
+
+.l-sub-section
+  :marked
+    All route/query parameters are strings.
+    The (+) in front of the `params['id']` expression is a JavaScript trick to convert the string to an integer.
+:marked
+  We add an `isSelected` method that returns true when a hero's id matches the selected id.
+
++makeExcerpt('app/heroes/hero-list.component.ts', 'isSelected')
+
+:marked
+  Finally, we update our template with a [Class Binding](template-syntax.html#class-binding) to that `isSelected` method.
+  The binding adds the `selected` CSS class when the method returns `true` and removes it when `false`.
+  Look for it within the repeated `<li>` tag as shown here:
+
++makeExcerpt('app/heroes/hero-list.component.ts', 'template')
+
+:marked
+  When the user navigates from the heroes list to the "Magneta" hero and back, "Magneta" appears selected:
+figure.image-display
+  img(src='/resources/images/devguide/router/selected-hero.png' alt="Selected List" )
+:marked
+  The optional `foo` route parameter is harmless and continues to be ignored.
+
+h3#route-animation Adding animations to the route component
+:marked
+  Our heroes feature module is almost complete, but what is a feature without some smooth transitions?
+  We already know that Angular supports [animations](../guide/animations.html) and we want to take
+  advantage of them by adding some animation to our *Hero Detail* component.
+
+  First, we'll start by importing our animation functions that build our animation triggers,
+  control state and manage transitions between states. We'll use these functions to add transitions
+  to our route component as it moves between states our application view. We'll also import the
+  `HostBinding` decorator for binding to our route component.
+
++makeExcerpt('app/heroes/hero-detail.component.ts (animation imports)', 'route-animation-imports')
+
+:marked
+  Next, we'll use a **host binding** for route animations named *@routeAnimation*. There is nothing special
+  about the choice of the binding name, but since we are controlling route animation, we'll go with `routeAnimation`.
+  The binding value is set to `true` because we only care about the `*` and `void` states which are
+  [entering and leaving](../guide/animations.html#example-entering-and-leaving) animation states.
+
+  We'll also add some display and positioning bindings for styling.
+
++makeExcerpt('app/heroes/hero-detail.component.ts (route animation binding)', 'route-animation-host-binding')
+
+:marked
+  Now we can build our animation trigger, which we'll call *routeAnimation* to match the binding we previously
+  setup. We'll use the **wildcard state** that matches any animation state our route component is in, along with
+  two *transitions*. One transition animates the component as it enters the application view (`void => *`), while the other
+  animates the component as it leaves the application view (`* => void`).
+
+  We could add different transitions to different route components depending on our needs. We'll just animate our `HeroDetailComponent` for this milestone.
+
+.l-sub-section
+  :marked
+    Using route animations on individual components is something we don't want to do throughout our entire application.
+    It would be better to animate routes based on **route paths**, a topic to cover in a future update to this chapter.
+
+:marked
+  Our route component animation looks as such:
+
++makeExcerpt('app/heroes/hero-detail.component.ts (route animation)', 'route-animation')
+
+:marked
+  Simply stated, our `HeroDetailComponent` will ease in from the left when routed to and will slide down when navigating away.
+  We could add more complex animations here, but we'll leave our `HeroDetailComponent` as is for now.
+
+h3#merge-hero-routes Import hero module into AppModule
+:marked
+  Our heroes feature module is ready, but application doesn't know about our heroes module yet.
+  We'll need to import it into the `AppModule` we defined in `app.module.ts`.
 
   Update `app.module.ts` as follows:
 
 +makeExcerpt('app/app.module.2.ts (heroes module import)', 'hero-import')
 
 :marked
-  We imported the `HeroesModule` and added it to our root NgModule `imports`.
+  We imported the `HeroesModule` and added it to our `AppModule`'s `imports`.
 
-  We removed the `HeroListComponent` from the root NgModule's `declarations` because its being provided by the `HeroesModule`
+  We removed the `HeroListComponent` from the `AppModule`'s `declarations` because its being provided by the `HeroesModule`
   now. This is important because their can be only **one** owner for a declared component. In our case, the `Heroes` module is
-  the owner of the `Heroes` components and is making them available to the root NgModule.
+  the owner of the `Heroes` components and is making them available to the `AppModule`.
 
-  As a result, the `app.module.ts` no longer has specific knowledge of the hero feature, its components, or its route details.
+.l-sub-section
+  :marked
+    Routes provided by feature modules will be combined together into their imported module's routes by
+    the router. This allows us to continue defining our feature module routes without
+    modifying our main route configuration.
+
+:marked
+  As a result, the `AppModule` no longer has specific knowledge of the hero feature, its components, or its route details.
   We can evolve the hero feature with more components and different routes.
   That's a key benefit of creating a separate module for each feature area.
 
-  Since our `Heroes` routes are defined within our submodule, we can also remove our initial `heroes` route from the `app.routing.ts`.
+  Since our `Heroes` routes are defined within our feature module, we can also remove our initial `heroes` route from the `app.routing.ts`.
 
 +makeExcerpt('app/app.routing.3.ts (v2)', '')
 
@@ -901,7 +1158,8 @@ h3#merge-hero-routes Import hero module into root NgModule
   * organize our app into *feature areas*
   * navigate imperatively from one component to another
   * pass information along in route parameters and subscribe to them in our component
-  * import our feature area NgModule into our root NgModule
+  * import our feature area NgModule into our `AppModule`
+  * apply animations to our route component
 
   After these changes, the folder structure looks like this:
 .filetree
@@ -937,8 +1195,8 @@ h3#merge-hero-routes Import hero module into root NgModule
   `router/ts/app/app.component.1.ts,
    router/ts/app/app.module.2.ts,
    router/ts/app/app.routing.3.ts,
-   router/ts/app/heroes/hero-list.component.1.ts,
-   router/ts/app/heroes/hero-detail.component.1.ts,
+   router/ts/app/heroes/hero-list.component.ts,
+   router/ts/app/heroes/hero-detail.component.ts,
    router/ts/app/heroes/hero.service.ts,
    router/ts/app/heroes/heroes.module.ts,
    router/ts/app/heroes/heroes.routing.ts`,
@@ -955,7 +1213,7 @@ h3#merge-hero-routes Import hero module into root NgModule
 .l-main-section#crisis-center-feature
 :marked
   ## Milestone #3: The Crisis Center
-  
+
   The *Crisis Center* is a fake view at the moment. Time to make it useful.
 
   The new *Crisis Center* begins as a virtual copy of the *Heroes* module.
@@ -985,7 +1243,7 @@ h3#merge-hero-routes Import hero module into root NgModule
   * Our `CrisisService` is only needed within the *Crisis Center* module.
   We should limit access to it to that module.
 
-  * Changes to a submodule such as *Crisis Center* shouldn't provoke changes to the root `NgModule` or
+  * Changes to a feature module such as *Crisis Center* shouldn't provoke changes to the `AppModule` or
   any other feature's component.
   We need to [*separate our concerns*](https://blog.8thlight.com/uncle-bob/2014/05/08/SingleReponsibilityPrinciple.html).
 
@@ -1016,7 +1274,7 @@ a#child-routing-component
   ### Child Routing Component
 
   Add the following `crisis-center.component.ts` to the `crisis-center` folder:
-  
+
 +makeExcerpt('app/crisis-center/crisis-center.component.ts (minus imports)', 'minus-imports')
 
 :marked
@@ -1044,7 +1302,7 @@ a#child-routing-component
   ### Service isolation
 
   The `CrisisService` is neither needed nor wanted outside the *Crisis Center* domain.
-  Instead of registering it with the root NgModule's providers &mdash;
+  Instead of registering it with the `AppModule`'s providers &mdash;
   which makes it visible everywhere &mdash;
   we register the `CrisisService` in the `CrisisCenterModule` providers array.
 
@@ -1071,6 +1329,11 @@ a#child-routing-component
   The `CrisisCenterComponent` is a *Routing Component* like the `AppComponent`.
   It has its own `RouterOutlet` and its own child routes.
 
+  Add the following `crisis-center-home.component.ts` to the `crisis-center` folder.
+
++makeExcerpt('app/crisis-center/crisis-center-home.component.ts (minus imports)', 'minus-imports')
+
+:marked
   We create a `crisis-center.routing.ts` file as we did the `heroes.routing.ts` file.
   But this time we define **child routes** *within* the parent `crisis-center` route.
 
@@ -1078,43 +1341,56 @@ a#child-routing-component
 
 :marked
   Notice that the parent `crisis-center` route has a `children` property
-  with an array of two routes.
+  with a single route containing our `CrisisListComponent`. The `CrisisListComponent` route
+  also has a `children` array with two routes.
+
   These two routes navigate to the two *Crisis Center* child components,
-  `CrisisListComponent` and `CrisisDetailComponent`.
+  `CrisisCenterHomeComponent` and `CrisisDetailComponent`.
 
   There are some *important differences* in the treatment of these routes.
 
-  First, the router displays the components of these child routes in the `RouterOutlet`
+  The router displays the components of these routes in the `RouterOutlet`
   of the `CrisisCenterComponent`, not in the `RouterOutlet` of the `AppComponent` shell.
 
-  Second, the child paths *extend* the path of their parent route.
+  The `CrisisListComponent` contains the crisis list and a `RouterOutlet` to
+  display the `Crisis Center Home` and `Crisis Detail` route components.
 
-  Normally paths that begin with `/` refer to the root of the application.
-  Here they are appended to the path to the `CrisisCenterComponent`.
+  The `Crisis Detail` route is a child of the `Crisis List`. Since the router [reuses components](#reuse)
+  by default, the `Crisis Detail` component will be re-used as we select different crises.
 
-  To write an URL that navigates to the `CrisisListComponent`, we'd append its child route path,  `/`,
-  to `/crisis-center`.
+  In contrast, back in the `Hero Detail` route, the component was recreated each time we selected a different hero.
 
-  To write an URL that navigates to the `CrisisDetailComponent`, we'd append the child route path,  `/`,
-  followed by the crisis id, yielding something like:
+  At the top level, paths that begin with `/` refer to the root of the application.
+  But these are child routes.
+  They *extend* the path of the parent route.
+  With each step down the route tree, we add a slash followed by the route path (unless the route path is _empty_).
 
+  For example, the parent path to the `CrisisCenterComponent` is `/crisis-center
+  The router appends these child paths to the parent path to the `CrisisCenterComponent` (`/crisis-center).
+
+  * to navigate to the `CrisisCenterHomeComponent, the full URL is `/crisis-center` (/crisis-center` + `''` + `''`).
+
+  * to navigate to the `CrisisDetailComponent` for a crisis with `id=2`, the full URL is
+  `/crisis-center/2` (/crisis-center` + `''` + `'/2'`).
+
+  The absolute URL for the latter example, including the origin, is
 code-example.
   localhost:3000/crisis-center/2
 
 :marked
-  Here's the complete `crisis-center.routing.ts` with its imports.
+  Here's the complete `crisis-center.routing.ts` file with its imports.
 
 +makeExcerpt('app/crisis-center/crisis-center.routing.1.ts', '')
 
-h3#import-crisis-module Import crisis center module into the root NgModule routes
+h3#import-crisis-module Import crisis center module into the AppModule routes
 :marked
-  As with the `Heroes` module, we must import the `Crisis Center` module into the root NgModule:
+  As with the `Heroes` module, we must import the `Crisis Center` module into the `AppModule`:
 
-+makeExcerpt('app/app.module.3.ts (Crisis Center Module)', '')
++makeExcerpt('app/app.module.3.ts (Crisis Center Module)', 'crisis-center-module')
 
 :marked
   We also remove the initial crisis center route from our `app.routing.ts`. Our routes
-  are now being provided by our `HeroesModule` and our `CrisisCenter` submodules. We'll keep our `app.routing.ts` file
+  are now being provided by our `HeroesModule` and our `CrisisCenter` feature modules. We'll keep our `app.routing.ts` file
   for general routes which we'll cover later in the chapter.
 
 +makeExcerpt('app/app.routing.4.ts (v3)', '')
@@ -1171,9 +1447,83 @@ code-example.
 
 +makeExcerpt('app/crisis-center/crisis-center.routing.2.ts (routes v2)' , 'routes')
 
+.l-main-section
+h2#relative-navigation Relative Navigation
+:marked
+  While building out our *Crisis Center* feature, we've navigated to the
+  *Crisis Detail* route using an **absolute path** that begins with a **slash**.
+  This navigation starts from the top of our route configuration to find the
+  matching path to our route.
+
+  We could continue to use absolute paths to navigate inside our *Crisis Center*
+  feature, but that makes our links very rigid. If we changed our parent `/crisis-center`
+  path, we would have to change our link parameters array.
+
+  We can make our links more flexible by using **relative** navigation with the router.
+  * The full path to the route is not required.
+  * Navigation within our feature area remains intact if the parent route path is changed.
+  * The *link parameters array* only contains navigation relative to the current URL.
+
+.l-sub-section
+  :marked
+    The **link parameters array** supports a directory-like syntax for relative navigation.
+
+    `./` or `no leading slash` is relative to the current level.
+
+    `../` to go up one level in the route path.
+
+    The relative navigation syntax can be used in combination with a *path*. If we wanted to navigate
+    from one route path to another sibling route path we could use `../path` convention to go up
+    one level and down to the sibling route path.
+
+:marked
+  In order to navigate relatively using the `Router` service, we use the `ActivatedRoute`
+  to give the router knowledge of where we are in the *RouterState*, which is our tree of
+  activated routes. We do this by adding an object as the second argument in our
+  `router.navigate` method after the *link parameters array* specifying the **relativeTo** property.
+  We set the `relativeTo` property to our `ActivatedRoute` and the router will merge our
+  navigation information into to the current URL.
+
+.l-sub-section
+  :marked
+    When using router's `navigateByUrl` method, the navigation is **always** absolute.
+
+:marked
+  ### Navigate to Crisis Detail relatively
+
+  Let's update our *Crisis List* `onSelect` method to use relative navigation so we don't have
+  to start from the top of our route configuration. We've already injected the `ActivatedRoute`
+  into our constructor that we'll need for the relative navigation.
+
++makeExcerpt('app/crisis-center/crisis-list.component.1.ts (constructor)', 'relative-navigation-ctor')
+
+:marked
+  When we visit the *Crisis Center*, our path is `/crisis-center`, so we just want to add the `id` of the *Crisis Center*
+  to our existing path. When the router navigates, it will use the current path `/crisis-center`,
+  adding on our `id`. If our `id` were `1`, the resulting path would be `/crisis-center/1`.
+
++makeExcerpt('app/crisis-center/crisis-list.component.ts (relative navigation)', 'relative-navigation')
+
+:marked
+  We'll also update the *Crisis Detail* component to navigate back to our *Crisis Center* list. We want to go back up a level
+  in the path, so we use to the `../` syntax. If our current `id` is `1`, the resulting path coming from `/crisis-center/1`
+  would be `/crisis-center`.
+
++makeExcerpt('app/crisis-center/crisis-detail.component.1.ts (relative navigation)', 'relative-navigation')
+
+:marked
+  If we are using a `RouterLink` to navigate instead of the `Router` service, we can use the **same**
+  link parameters array, but we don't have to provide the object with the `relativeTo` property. The `ActivatedRoute`
+  is implicit in the `RouterLink` directive.
+
++makeExcerpt('app/crisis-center/crisis-list.component.1.ts (relative routerLink)', 'relative-navigation-router-link')
+
+<a id="guards"></a>
 .l-main-section
 h2#guards Route Guards
 :marked
+  ## Milestone #4: Route Guards
+
   At the moment, *any* user can navigate *anywhere* in the application *anytime*.
 
   That's not always the right thing to do.
@@ -1200,32 +1550,28 @@ h2#guards Route Guards
   Accordingly, a routing guard can return an `Observable<boolean>` or a `Promise<boolean>` and the
   router will wait for the observable to resolve to `true` or `false`.
 
-  The router supports three kinds of guards:
+  The router supports multiple kinds of guards:
 
   1. [CanActivate](../api/router/index/CanActivate-interface.html) to mediate navigation *to* a route.
 
-  2. [CanDeactivate](../api/router/index/CanDeactivate-interface.html) to mediate navigation *away* from the current route.
+  2. [CanActivateChild](../api/router/index/CanActivateChild-interface.html) to mediate navigation *to* a child route.
 
-  3. [Resolve](../api/router/index/Resolve-interface.html) to perform route data retrieval before *before* route activation.
+  3. [CanDeactivate](../api/router/index/CanDeactivate-interface.html) to mediate navigation *away* from the current route.
+
+  4. [Resolve](../api/router/index/Resolve-interface.html) to perform route data retrieval *before* route activation.
+
+  5. [CanLoad](../api/router/index/CanLoad-interface.html) to mediate navigation *to* a feature module loaded _asynchronously_.
 
-.l-sub-section
-  :marked
-    We'll examine other router guards in a future update to this chapter.
 :marked
   We can have multiple guards at every level of a routing hierarchy.
-  The router checks the `CanDeactivate` guards first, from deepest child route to the top.
-  Then it checks the `CanActivate` guards from the top down to the deepest child route.
+  The router checks the `CanDeactivate` and `CanActivateChild` guards first, from deepest child route to the top.
+  Then it checks the `CanActivate` guards from the top down to the deepest child route. If the feature module
+  is loaded asynchronously, the `CanLoad` guard is checked before the module is loaded.
   If _any_ guard returns false, pending guards that have not completed will be canceled,
   and the entire navigation is canceled.
 
   Let's look at some examples.
 
-.l-main-section#lifecycle-hooks
-:marked
-  ## Router Lifecycle Hooks
-
-  TODO: Pausing activation
-
 a#can-activate-guard
 :marked
   ### *CanActivate*: requiring authentication
@@ -1236,30 +1582,77 @@ a#can-activate-guard
 
   The `CanActivate` guard is the tool to manage these navigation business rules.
 
-  #### Add a crisis admin feature
+  #### Add an admin feature module
 
   We intend to extend the Crisis Center with some new *administrative* features.
-  Those features aren't defined yet. So we add the following placeholder component.
+  Those features aren't defined yet. So we add a new feature module named `AdminModule`.
+  We'll follow our same convention by creating an `admin` folder with a feature
+  module file, route file and supporting components.
 
-+makeExcerpt('app/crisis-center/crisis-admin.component.1.ts')
+  Our admin feature module file structure looks like this:
+
+.filetree
+  .file app/admin
+  .children
+    .file admin-dashboard.component.ts
+    .file admin.component.ts
+    .file admin.module.ts
+    .file admin.routing.ts
+    .file manage-crises.component.ts
+    .file manage-heroes.component.ts
 
 :marked
-  Next, we add a child route to the `crisis-center.routes` with the path, `/admin`.
+  Our admin feature module contains our `AdminComponent` used for routing within our
+  feature module, a dashboard route and two unfinished components to manage crises and heroes.
 
-+makeExcerpt('app/crisis-center/crisis-center.routing.3.ts (admin route)', 'admin-route-no-guard')
++makeTabs(
+   `router/ts/app/admin/admin-dashboard.component.1.ts,
+   router/ts/app/admin/admin.component.ts,
+   router/ts/app/admin/admin.module.ts,
+   router/ts/app/admin/manage-crises.component.ts,
+   router/ts/app/admin/manage-heroes.component.ts
+  `,
+  null,
+   `app/admin/admin-dashboard.component.ts,
+   app/admin/admin.component.ts,
+   app/admin/admin.module.ts,
+   app/admin/manage-crises.component.ts,
+   app/admin/manage-heroes.component.ts
+  `)
+
+.l-sub-section
+  :marked
+    Since our admin dashboard `RouterLink` is an empty path route in our `AdminModule`, it
+    is considered a match to any route within our admin feature area. We only want the `Dashboard`
+    link to be active when we visit that route. We've added an additional binding to our `Dashboard` routerLink,
+    `[routerLinkActiveOptions]="{ exact: true }"` which will only mark the `./` link as active when
+    we navigate the to `/admin` URL and not when we navigate to one the other child routes.
+
+:marked
+  Our initial admin routing configuration:
+
++makeExcerpt('app/admin/admin.routing.1.ts (admin routing)', 'admin-routes')
+
+h3#component-less-route <i>Component-Less Route</i>: grouping routes without a component
+:marked
+  Looking at our child route under the `AdminComponent`, we have a route with a **path** and a **children**
+  property but it's not using a **component**. We haven't made a mistake in our configuration, because we can
+  use a **component-less** route.
+
+  We want to group our `Crisis Center` management routes under the `admin` path, but we don't need a component
+  just to group those routes under an additional `RouterOutlet`. This also allows us to [guard child routes](#can-activate-child-guard).
+
+:marked
+  Next, we'll import the `AdminModule` into our `app.module.ts` and add it to the `imports` array
+  to register our admin routes.
+
++makeExcerpt('app/app.module.3.ts (admin module)', 'admin-module')
 
 :marked
   And we add a link to the `AppComponent` shell that users can click to get to this feature.
 
 +makeExcerpt('app/app.component.4.ts', 'template')
 
-.l-sub-section
-  :marked
-    Since our admin `RouterLink` is a child route of our `Crisis Center`, we only want the `Crisis Center`
-    link to be active when we visit that route. We've added an additional binding to our `/crisis-center` routerLink,
-    `[routerLinkActiveOptions]="{ exact: true }"` which will only mark the `/crisis-center` link as active when
-    we navigate the to `/crisis-center` URL and not when we navigate to one its child routes.
-
 :marked
   #### Guard the admin feature
   Currently every route within our *Crisis Center* is open to everyone.
@@ -1278,10 +1671,10 @@ a#can-activate-guard
 +makeExcerpt('app/auth-guard.service.1.ts')
 
 :marked
-  Next we open `crisis-center.routing.ts `, import the `AuthGuard` class, and
+  Next we open `admin.routing.ts `, import the `AuthGuard` class, and
   update the admin route with a `CanActivate` guard property that references it:
 
-+makeExcerpt('app/crisis-center/crisis-center.routing.ts (guarded admin route)', 'admin-route')
++makeExcerpt('app/admin/admin.routing.2.ts (guarded admin route)', 'admin-route')
 
 :marked
   Our admin feature is now protected by the guard, albeit protected poorly.
@@ -1324,11 +1717,11 @@ a#can-activate-guard
   There is nothing new about this component or the way we wire it into the router configuration.
 
   We'll register a `/login` route in our `app.routing.ts` and add the necessary providers to the `appRoutingProviders`
-  array we created earlier. In our `app.module.ts`, we'll import the `LoginComponent` and add it to our root NgModule `declarations`.
+  array we created earlier. In our `app.module.ts`, we'll import the `LoginComponent` and add it to our `AppModule` `declarations`.
 
 +makeTabs(
    `router/ts/app/app.module.ts,
-   router/ts/app/app.routing.5.ts,
+   router/ts/app/app.routing.6.ts,
    router/ts/app/login.component.1.ts,
    router/ts/app/login.routing.ts
   `,
@@ -1339,6 +1732,35 @@ a#can-activate-guard
    app/login.routing.ts
   `)
 
+.l-sub-section
+  :marked
+    Guards and the service providers they require **must** be provided at the module-level. This allows
+    the Router access to retrieve these services from the `Injector` during the navigation process.
+    The same rule applies for feature modules loaded [asynchronously](#asynchronous-routing).
+
+h3#can-activate-child-guard <i>CanActivateChild</i>: guarding child routes
+:marked
+  As we learned about guarding routes with `CanActivate`, we can also protect child routes with the `CanActivateChild`
+  guard. The `CanActivateChild` guard works similarly to the `CanActivate` guard, but the difference is its run _before_
+  each child route is activated. We protected our admin feature module from unauthorized access, but we could also
+  protect child routes within our feature module.
+
+  Let's extend our `AuthGuard` to protect when navigating between our `admin` routes. First we'll open our
+  `auth-guard.service.ts` and add `CanActivateChild` interface to our imported tokens from the router package.
+
+  Next, we'll implement the `canActivateChild` method with takes the same arguments as the `canActivate` method,
+  an `ActivatedRouteSnapshot` and `RouterStateSnapshot`. The `canActivateChild` behaves the same way the other
+  guards do, returning an `Observable<boolean>` or `Promise<boolean>` for async checks and `boolean` for sync checks.
+  We'll return a `boolean`
+
++makeExcerpt('app/auth-guard.service.3.ts (excerpt)', 'can-activate-child')
+
+:marked
+  We add the same `AuthGuard` to our `component-less` admin route to protect all other child routes at one time
+  instead of adding the `AuthGuard` to each route individually.
+
++makeExcerpt('app/admin/admin.routing.3.ts (excerpt)', 'can-activate-child')
+
 h3#can-deactivate-guard <i>CanDeactivate</i>: handling unsaved changes
 :marked
   Back in the "Heroes" workflow, the app accepts every change to a hero immediately without hesitation or validation.
@@ -1395,7 +1817,7 @@ h3#can-deactivate-guard <i>CanDeactivate</i>: handling unsaved changes
     by waiting for the user's answer asynchronously. Waiting for the user asynchronously
     is like waiting for the server asynchronously.
 :marked
-  The `DialogService` (provided in the root `NgModule` for app-wide use) does the asking.
+  The `DialogService` (provided in the `AppModule` for app-wide use) does the asking.
 
   It returns a [promise](http://exploringjs.com/es6/ch_promises.html) that
   *resolves* when the user eventually decides what to do: either
@@ -1431,12 +1853,12 @@ a#CanDeactivate
 :marked
   We add the `Guard` to our crisis detail route in `crisis-center.routing.ts` using the `canDeactivate` array.
 
-+makeExample('app/crisis-center/crisis-center.routing.4.ts', '')
++makeExcerpt('app/crisis-center/crisis-center.routing.3.ts (can deactivate guard)', '')
 
 :marked
   We also need to add the `Guard` to our main `appRoutingProviders` so the `Router` can inject it during the navigation process.
 
-+makeExample('app/app.routing.5.ts', '', '')
++makeExample('app/app.routing.6.ts', '', '')
 
 :marked
   Now we have given our user a safeguard against unsaved changes.
@@ -1465,7 +1887,7 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
   navigate to an invalid crisis center `:id`, we'll navigate back to our list of existing crises.
 
   Like the `CanActivate` and `CanDeactivate` guards, the **`Resolve`** guard is an interface we can implement as a service
-  to resolve route data synchronously or asynchronously. In our `Crisis Detail` component, we used the `ngOnInit` to retrieve the `Crisis`
+  to resolve route data synchronously or asynchronously. In `CrisisDetailComponent`, we used the `ngOnInit` to retrieve the `Crisis`
   information. We also navigated the user away from the route if the `Crisis` was not found. It would be more efficient to perform this
   action before the route is ever activated.
 
@@ -1489,7 +1911,7 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
 
   Now that our guard is ready, we'll import it in our `crisis-center.routing.ts` and use the `resolve` object in our route configuration.
 
-+makeExcerpt('app/crisis-center/crisis-center.routing.5.ts (resolve)', 'crisis-detail-resolve')
++makeExcerpt('app/crisis-center/crisis-center.routing.ts (resolve)', 'crisis-detail-resolve')
 
 :marked
   We'll add the `CrisisDetailResolve` service to our crisis center module's `providers`, so its available to the `Router` during the navigation process.
@@ -1498,9 +1920,9 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
 
 :marked
   Now that we've added our `Resolve` guard to fetch data before the route loads, we no longer need to do this once we get into our `CrisisDetailComponent`.
-  We'll update the `CrisisDetailComponent` to use the `ActivatedRoute.data`, which is where our `crisis` property from our `Resolve` guard will be provided.
-  Once activated, all we need to do is set our local `crisis` and `editName` properties from our resolved `Crisis` information. We no longer need to subscribe
-  and unsubscribe to the `ActivatedRoute` params to fetch the `Crisis` because it is being provided synchronously at the time the route component is activated.
+  We'll update the `CrisisDetailComponent` to use the `ActivatedRoute` data, which is where our `crisis` property from our `Resolve` guard will be provided.
+  Once activated, all we need to do is set our local `crisis` and `editName` properties from our resolved `Crisis` information. The `Crisis` is being provided
+  at the time the route component is activated.
 
 +makeExcerpt('app/crisis-center/crisis-detail.component.ts (ngOnInit v2)', 'crisis-detail-resolve')
 
@@ -1516,15 +1938,17 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
 
 +makeTabs(
    `router/ts/app/app.component.ts,
+   router/ts/app/crisis-center/crisis-center-home.component.ts,
    router/ts/app/crisis-center/crisis-center.component.ts,
    router/ts/app/crisis-center/crisis-center.routing.ts,
-   router/ts/app/crisis-center/crisis-list.component.1.ts,
+   router/ts/app/crisis-center/crisis-list.component.ts,
    router/ts/app/crisis-center/crisis-detail.component.ts,
    router/ts/app/crisis-center/crisis-detail-resolve.service.ts,
    router/ts/app/crisis-center/crisis.service.ts
   `,
   null,
    `app.component.ts,
+   crisis-center-home.component.ts,
    crisis-center.component.ts,
    crisis-center.routing.ts,
    crisis-list.component.ts,
@@ -1534,7 +1958,7 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
   `)
 
 +makeTabs(
-   `router/ts/app/auth-guard.service.2.ts,
+   `router/ts/app/auth-guard.service.3.ts,
    router/ts/app/can-deactivate-guard.service.ts
   `,
   null,
@@ -1542,169 +1966,6 @@ h3#resolve-guard <i>Resolve</i>: pre-fetching component data
    can-deactivate-guard.service.ts
   `)
 
-
-.l-main-section#optional-route-parameters
-:marked
-  ## Milestone #4: Route Parameters
-
-  We use [*route parameters*](#route-parameters) to specify a *required* parameter value *within* the route URL
-  as we do when navigating to the `HeroDetailComponent` in order to view-and-edit the hero with *id:15*.
-code-example(format="." language="bash").
-  localhost:3000/hero/15
-:marked
-  Sometimes we wish to add *optional* information to a route request.
-  For example, the `HeroListComponent` doesn't need help to display a list of heroes.
-  But it might be nice if the previously-viewed hero were pre-selected when returning from the `HeroDetailComponent`.
-figure.image-display
-  img(src='/resources/images/devguide/router/selected-hero.png' alt="Selected hero")
-:marked
-  That becomes possible if we can include hero Magneta's `id` in the URL when we
-  return from the `HeroDetailComponent`, a scenario we'll pursue in a moment.
-
-  Optional information takes other forms. Search criteria are often loosely structured, e.g., `name='wind*'`.
-  Multiple values are common &mdash; `after='12/31/2015' & before='1/1/2017'` &mdash; in no particular order &mdash;
-   `before='1/1/2017' & after='12/31/2015'` &mdash; in a variety of formats &mdash; `during='currentYear'` .
-
-  These kinds of parameters don't fit easily in a URL *path*. Even if we could define a suitable URL token scheme,
-  doing so greatly complicates the pattern matching required to translate an incoming URL to a named route.
-
-  Optional parameters are the ideal vehicle for conveying arbitrarily complex information during navigation.
-  Optional parameters aren't involved in pattern matching and affords enormous flexibility of expression.
-
-  The Component Router supports navigation with optional parameters as well as required route parameters.
-  We define _optional_ parameters in an *object* after we define our required route parameters.
-
-  ### Route Parameters: Required or Optional?
-
-  There is no hard-and-fast rule. In general,
-
-  *prefer a required route parameter when*
-  * the value is required.
-  * the value is necessary to distinguish one route path from another.
-
-  *prefer an optional parameter when*
-  * the value is complex and/or multi-variate.
-
-  <a id="route-parameters-object"></a>
-  ### Route parameter
-
-  When navigating to the `HeroDetailComponent` we specified the `id` of the hero-to-edit in the
-  *route parameter* and made it the second item of the [*link parameters array*](#link-parameters-array).
-
-+makeExcerpt('app/heroes/hero-list.component.1.ts', 'link-parameters-array', '')
-
-:marked
-  The router embedded the `id` value in the navigation URL because we had defined it
-  as a route parameter with an `:id` placeholder token in the route `path`:
-
-+makeExcerpt('app/heroes/heroes.routing.ts', 'hero-detail-route', '')
-
-:marked
-  When the user clicks the back button, the `HeroDetailComponent` constructs another *link parameters array*
-  which it uses to navigate back to the `HeroListComponent`.
-
-+makeExcerpt('app/heroes/hero-detail.component.1.ts', 'gotoHeroes', '')
-
-:marked
-  This array lacks a route parameter because we had no reason to send information to the `HeroListComponent`.
-
-  Now we have a reason. We'd like to send the id of the current hero with the navigation request so that the
-  `HeroListComponent` can highlight that hero in its list.
-
-  We do that with an object that contains our optional `id` parameter.
-  We also defined a junk parameter (`foo`) that the `HeroListComponent` should ignore.
-  Here's the revised navigation statement:
-
-+makeExcerpt('app/heroes/hero-detail.component.ts', 'gotoHeroes-navigate', '')
-
-:marked
-  The application still works. Clicking "back" returns to the hero list view.
-
-  Look at the browser address bar.
-.l-sub-section
-  img(src='/resources/images/devguide/plunker-separate-window-button.png' alt="pop out the window" align="right" style="margin-right:-20px")
-  :marked
-    When running in plunker, pop out the preview window by clicking the blue 'X' button in the upper right corner.
-:marked
- It should look something like this, depending on where you run it:
-
-code-example(language="bash").
-  localhost:3000/heroes;id=15;foo=foo
-
-:marked
-  The `id` value appears in the URL as (`;id=15;foo=foo`), not in the URL path.
-  The path for the "Heroes" route doesn't have an `:id` token.
-
-  The optional route parameters are not separated by "?" and "&".
-  They are **separated by semicolons (;)**
-  This is *matrix URL* notation &mdash; something we may not have seen before.
-
-.l-sub-section
-  :marked
-    *Matrix URL* notation is an idea first floated
-    in a [1996 proposal](http://www.w3.org/DesignIssues/MatrixURIs.html) by the founder of the web, Tim Berners-Lee.
-
-    Although matrix notation never made it into the HTML standard, it is legal and
-    it became popular among browser routing systems as a way to isolate parameters
-    belonging to parent and child routes. The Angular Component Router is such a system.
-
-    The syntax may seem strange to us but users are unlikely to notice or care
-    as long as the URL can be emailed and pasted into a browser address bar
-    as this one can.
-
-:marked
-  ### Route parameters in the *ActivatedRoute* service
-
-  The list of heroes is unchanged. No hero row is highlighted.
-
-.l-sub-section
-  :marked
-    The <live-example></live-example> *does* highlight the selected
-    row because it demonstrates the final state of the application which includes the steps we're *about* to cover.
-    At the moment we're describing the state of affairs *prior* to those steps.
-:marked
-  The `HeroListComponent` isn't expecting any parameters at all and wouldn't know what to do with them.
-  Let's change that.
-
-  When navigating from the `HeroListComponent` to the `HeroDetailComponent`
-  we subscribed the route params `Observable` and made it available to the `HeroDetailComponent`
-  in the `ActivatedRoute` service. We injected that service in the constructor of the `HeroDetailComponent`.
-
-  This time we'll be navigating in the opposite direction, from the `HeroDetailComponent` to the `HeroListComponent`.
-
-  First we extend the router import statement to include the `ActivatedRoute` service symbol;
-
-+makeExcerpt('app/heroes/hero-list.component.ts (import)', 'import-router')
-
-:marked
-  Then we use the `ActivatedRoute` to access the `params` _Observable_ so we can subscribe
-  and extract the `id` parameter as the `selectedId`:
-
-+makeExcerpt('app/heroes/hero-list.component.ts (constructor)', 'ctor')
-
-.l-sub-section
-  :marked
-    All route/query parameters are strings.
-    The (+) in front of the `params['id']` expression is a JavaScript trick to convert the string to an integer.
-:marked
-  We add an `isSelected` method that returns true when a hero's id matches the selected id.
-
-+makeExcerpt('app/heroes/hero-list.component.ts', 'isSelected')
-
-:marked
-  Finally, we update our template with a [Class Binding](template-syntax.html#class-binding) to that `isSelected` method.
-  The binding adds the `selected` CSS class when the method returns `true` and removes it when `false`.
-  Look for it within the repeated `<li>` tag as shown here:
-
-+makeExcerpt('app/heroes/hero-list.component.ts', 'template')
-
-:marked
-  When the user navigates from the heroes list to the "Magneta" hero and back, "Magneta" appears selected:
-figure.image-display
-  img(src='/resources/images/devguide/router/selected-hero.png' alt="Selected List" )
-:marked
-  The optional `foo` route parameter is harmless and continues to be ignored.
-
 a#query-parameters
 a#fragment
 :marked
@@ -1723,7 +1984,7 @@ a#fragment
 
   We'll add the `NavigationExtras` object to our `router.navigate` method that navigates us to our `/login` route.
 
-+makeExcerpt('app/auth-guard.service.ts (v3)', '')
++makeExcerpt('app/auth-guard.service.4.ts (v3)', '')
 
 :marked
   We can also **preserve** query parameters and fragments across navigations without having to re-provide them
@@ -1734,10 +1995,10 @@ a#fragment
 +makeExcerpt('app/login.component.ts', 'preserve')
 
 :marked
-  Since we'll be navigating to our *Crisis Admin* route after logging in, we'll update it to handle our
+  Since we'll be navigating to our *Admin Dashboard* route after logging in, we'll update it to handle our
   query parameters and fragment.
 
-+makeExcerpt('app/crisis-center/crisis-admin.component.ts (v2)', '')
++makeExcerpt('app/admin/admin-dashboard.component.ts (v2)', '')
 
 :marked
   *Query Parameters* and *Fragments* are also available through the `ActivatedRoute` service available to route components.
@@ -1751,11 +2012,17 @@ a#fragment
     When running in plunker, pop out the preview window by clicking the blue 'X' button in the upper right corner.
 
 :marked
-  Following the steps in this process, we can click on the *Crisis Admin* button, that takes us to the *Login*
+  Following the steps in this process, we can click on the *Admin* button, that takes us to the *Login*
   page with our provided `query params` and `fragment`. After we click the login button, we notice that
-  we have been redirected to the `Crisis Admin` page with our `query params` and `fragment` still intact. We can use
+  we have been redirected to the `Admin Dashboard` page with our `query params` and `fragment` still intact. We can use
   these persistent bits of information for things that need to be provided with across pages interaction like
   authentication tokens or session ids.
+
+.l-sub-section
+  :marked
+    The `query params` and `fragment` can also be preserved using a `RouterLink` with
+    the **preserveQueryParams** and **preserveFragment** bindings respectively.
+
 <a id="asynchronous-routing"></a>
 .l-main-section
 :marked
@@ -1768,48 +2035,52 @@ a#fragment
   So how do we combat this problem? We introduce asynchronous routing into our application and take advantage of loading
   feature areas _lazily_. This buys us multiple things:
 
-  We can continue building out feature areas without increasing our initial bundle.
-  We can load feature areas only when requested by the user.
-  We can speed up load time for users that only visit certain areas of our application.
+  * We can continue building out feature areas without increasing our initial bundle.
+  * We can load feature areas only when requested by the user.
+  * We can speed up load time for users that only visit certain areas of our application.
 
   These are all things we want to have in our application, so let's apply this to our current setup. We've already made
-  great strides by organizing our application into three modules: `AppModule`, `HeroesModule` and `CrisisCenterModule`.
-  Our `CrisisCenterModule` is the most feature-rich area of our application and also the largest, so we'll take advantage
-  of asynchronous routing and only load the `Crisis Center` feature area when requested.
+  great strides by organizing our application into four modules: `AppModule`, `HeroesModule`, `AdminModule` and `CrisisCenterModule`.
+  Our `AdminModule` is the area of our application that would be scoped to a small set of users, so we'll take advantage
+  of asynchronous routing and only load the `Admin` feature area when requested.
 
 :marked
   ### Lazy-Loading route configuration
 
-  We'll start by pulling our `redirect` and `crisis-center` routes out of our `CrisisCenterModule` and including them in our
-  `app.routing.ts` file. We want to load our `Crisis Center` asynchronously, so we'll use the `loadChildren` property in
-  our route config where previously we used the `children` property to include our child routes.
+  We'll start by adding an `admin` route to our `app.routing.ts` file. We want to load our `Admin` module asynchronously,
+  so we'll use the `loadChildren` property in our route config where previously we used the `children` property to include our child routes.
 
-  We'll also change our `crisis-center` **path** in our `crisis-center.routing.ts` to an empty path. The `Router` supports
+  We'll also change our `admin` **path** in our `admin.routing.ts` to an empty path. The `Router` supports
   *empty path* routes, which we can use for grouping routes together without adding anything additional paths to the URL. Our
-  users will still visit `/crisis-center` and our `CrisisCenterComponent` still serves as our *Routing Component* which contains
+  users will still visit `/admin` and our `AdminComponent` still serves as our *Routing Component* which contains
   our child routes.
 
 +makeTabs(
-  `router/ts/app/app.routing.6.ts,
-  router/ts/app/crisis-center/crisis-center.routing.ts`,
-  'lazy-load-crisis-center,lazy-load-crisis-center',
+  `router/ts/app/app.routing.ts,
+  router/ts/app/admin/admin.routing.ts`,
+  'lazy-load-admin,',
   `app.routing.ts (load children),
-  crisis-center.routing.ts (empty path crisis center)
+  app/admin/admin.routing.ts (empty path admin)
   `)
 
-:marked
-  The `loadChildren` property is used by the `Router` to map to our bundle we want to lazy-load, in this case being the `CrisisCenterModule`.
-
-  If we look closer at the `loadChildren` string, we can see that it maps directly to our `crisis-center.module` file where we previously built
-  out our `Crisis Center` feature area. After the path to the file we use a `#` to denote where our file path ends and to tell the `Router` the name
-  of our `CrisisCenter` NgModule. If we look in our `crisis-center.module` file, we can see it matches name of our exported NgModule class.
-
-+makeExcerpt('app/crisis-center/crisis-center.module.ts (export)', 'crisis-center-module-export')
+.l-sub-section
+  :marked
+    We use the ES2015 `spread` feature to flatten the route arrays of our `adminRoutes` and `loginRoutes`
+    into our `appRoutes` array to provide a simple array of routes.
 
 :marked
-  The `loadChildren` property is used by the `Router` to map to our bundle we want to lazy-load, in this case being the `CrisisCenterModule`.
-  The router will take our loadChildren string and dynamically load in our `CrisisCenterModule`, add its routes to our configuration *dynamically*
-  and then load the requested route. This will only happen when route is **first** requested and the module will be immediately be available
+  The `loadChildren` property is used by the `Router` to map to our bundle we want to lazy-load, in this case being the `AdminModule`.
+
+  If we look closer at the `loadChildren` string, we can see that it maps directly to our `admin.module.ts` file where we previously built
+  out our `Admin` feature area. After the path to the file we use a `#` to denote where our file path ends and to tell the `Router` the name
+  of our `AdminModule`. If we look in our `admin.module.ts` file, we can see it matches name of our exported module class.
+
++makeExcerpt('app/admin/admin.module.ts (export)', 'admin-module-export')
+
+:marked
+  The `loadChildren` property is used by the `Router` to map to our bundle we want to lazy-load, in this case being the `AdminModule`.
+  The router will take our loadChildren string and dynamically load in our `AdminModule`, add its routes to our configuration *dynamically*
+  and then load the requested route. This will only happen when the route is **first** requested and the module will be immediately be available
   for subsequent requests.
 
 .l-sub-section
@@ -1819,16 +2090,36 @@ a#fragment
 
 :marked
   We've built our feature area, we've updated our route configuration to take advantage of lazy-loading, now we have to do the final step
-  to break our `CrisisCenterModule` into a completely separate module. In our `app.module.ts`, we'll remove our `CrisisCenterModule` from the
-  `imports` array since we'll be loading it on-demand an we'll remove the imported `CrisisCenterModule`.
+  to break our `AdminModule` into a completely separate module. In our `app.module.ts`, we'll remove our `AdminModule` from the
+  `imports` array since we'll be loading it on-demand an we'll remove the imported `AdminModule`.
 
-+makeExcerpt('app/app.module.ts (final)', '')
++makeExcerpt('app/app.module.ts (async admin module)', '')
+
+h3#can-load-guard <i>CanLoad Guard</i>: guarding against loading of feature modules
+:marked
+  We're already protecting our `AdminModule` with a `CanActivate` guard that prevents the user from
+  accessing the admin feature area unless authorized. We're currently loading the admin routing
+  asynchronously when requested, checking the user access and redirecting to the login page if not
+  authorized. Ideally, we only want to load the `AdminModule` if the user is logged in and prevent
+  the `AdminModule` and its routing from being loaded until then.
+
+  The **CanLoad** guard covers this scenario.
+
+  We can use the `CanLoad` guard to only load the `AdminModule` once the user is logged in **and** attempts
+  to access the admin feature area. We'll update our existing `AuthGuard` to support the `CanLoad` guard. We'll import
+  the `CanLoad` interface and the `Route` the guard provides when called that contains the requested path.
+
+  We'll add the interface to our service, and then we'll implement the interface. Since our `AuthGuard` already
+  checks the user's logged in state, we can pass that access check to our `canLoad` method. The `Route` in
+  the `canLoad` method provides a **path** which comes from our route configuration.
+
++makeExcerpt('app/auth-guard.service.ts (can load guard)', '')
 
 :marked
-  If our initial redirect went to `/heroes` instead of going to `/crisis-center`, the `CrisisCenterModule` would not be loaded until the user
-  visited a `Crisis Center` route. We'll update our redirect in our `app.routing.ts` to make this change.
+  Next, we'll import the `AuthGuard` into our `app.routing.ts` and add the `AuthGuard` to the `canLoad` array for
+  our `admin` route. Now our `admin` feature area is only loaded when the proper access has been granted.
 
-+makeExcerpt('app/app.routing.6.ts (heroes redirect)', 'heroes-redirect')
++makeExcerpt('app/app.routing.ts (can load guard)', 'can-load-guard')
 
 <a id="final-app"></a>
 .l-main-section
@@ -1846,7 +2137,6 @@ a#fragment
 
   The appendix material isn't essential. Continued reading is for the curious.
 
-
 .l-main-section#link-parameters-array
 :marked
   ## Appendix: Link Parameters Array
@@ -1968,7 +2258,7 @@ code-example(format=".", language="bash").
 code-example(format=".", language="bash").
   localhost:3002/src/#/crisis-center/
 :marked
-  The Angular Component Router supports both styles with two `LocationStrategy` providers:
+  The Router supports both styles with two `LocationStrategy` providers:
   1. `PathLocationStrategy` - the default "HTML 5 pushState" style.
   1. `HashLocationStrategy` - the "hash URL" style.
 
@@ -2033,6 +2323,6 @@ code-example(format=".", language="bash").
   ### *HashLocationStrategy*
   We can go old-school with the `HashLocationStrategy` by
   providing the `useHash: true` in an object as the second argument of the `RouterModule.forRoot`
-  in our root NgModule.
+  in our `AppModule`.
 
-+makeExcerpt('app/app.module.4.ts (hash URL strategy)', '')
++makeExcerpt('app/app.module.5.ts (hash URL strategy)', '')