docs: rename heros to heroes

public/docs/_examples/cb-component-communication/ts/app/app.component.html

@@ -1,6 +1,6 @@
 <h1 id="top">Component Communication Cookbook</h1>
 
-<a href="#parent-to-child">Pass data from parent to child with input binding ("Heros")</a><br/>
+<a href="#parent-to-child">Pass data from parent to child with input binding ("Heroes")</a><br/>
 <a href="#parent-to-child-setter">Intercept input property changes with a setter ("Master")</a><br/>
 <a href="#parent-to-child-on-changes">Intercept input property changes with <i>ngOnChanges</i> ("Source code version")</a><br/>
 <a href="#child-to-parent">Parent listens for child event ("Colonize Universe")</a><br/>

public/docs/_examples/cb-dependency-injection/ts/app/hero.service.ts

@@ -6,17 +6,17 @@ import {Hero}       from './hero';
 export class HeroService {
 
   //TODO move to database
-  private _heros:Array<Hero> = [
+  private _heroes:Array<Hero> = [
     new Hero(1, 'RubberMan','Hero of many talents', '123-456-7899'),
     new Hero(2, 'Magma','Hero of all trades', '555-555-5555'),
     new Hero(3, 'Mr. Nice','The name says it all','111-222-3333')
  ];
 
   getHeroById(id:number):Hero{
-    return this._heros.filter(hero => hero.id === id)[0];
+    return this._heroes.filter(hero => hero.id === id)[0];
   }
 
   getAllHeroes():Array<Hero>{
-    return this._heros;
+    return this._heroes;
   }
 }

public/docs/_examples/dependency-injection/e2e-spec.js

@@ -170,7 +170,7 @@ describe('Dependency Injection Tests', function () {
       });
     });
 
-    it('unauthorized user should have no authorized heros listed', function () {
+    it('unauthorized user should have no authorized heroes listed', function () {
       expect(element.all(by.css('#authorized hero-list div')).count()).toEqual(0);
     });
 
@@ -205,7 +205,7 @@ describe('Dependency Injection Tests', function () {
         });
       });
 
-      it('authorized user should have no unauthorized heros listed', function () {
+      it('authorized user should have no unauthorized heroes listed', function () {
         expect(element.all(by.css('#unauthorized hero-list div')).count()).toEqual(0);
       });
     });

public/docs/_examples/hierarchical-dependency-injection/e2e-spec.js

@@ -9,7 +9,7 @@ describe('Hierarchical dependency injection', function () {
       "edit button should be displayed");
   });
 
-  it('should have multiple heros listed', function () {
+  it('should have multiple heroes listed', function () {
     expect(element.all(by.css('heroes-list li')).count()).toBeGreaterThan(1);
   });
 

public/docs/ts/latest/guide/router-aux.jade

@@ -24,7 +24,7 @@
     
   :marked
     In this auxiliary chat experience, it overlays the current screen and persists.
-    If you navigate from the Heros to Crisis Center, the chat auxiliary route remains
+    If you navigate from the Heroes to Crisis Center, the chat auxiliary route remains
     active and in view. 
     
     Therefore the auxiliary routing is truly independent of the other
@@ -73,7 +73,7 @@
     In the chat components, we can use `RouterLink` to reference routes just the same as 
     a normal route. Since this is inside of an Auxiliary route, these relative links will
     resolve within the chat component and not change the primary route (the Crisis Center or 
-    Heros pages).
+    Heroes pages).
     
   +_makeExample('router/ts/app/chat/chat-init.component.ts', 'chat-links')