From 9ee29ecdd4fcb7b42194c87a7ad90b923a47a4a1 Mon Sep 17 00:00:00 2001
From: Frederik Schlemmer <Frederik.Schlemmer@adesso.de>
Date: Tue, 28 Aug 2018 06:36:13 +0200
Subject: [PATCH] docs: clarification of hero selection in routing section
 (#25634)

PR Close #25634
---
 aio/content/tutorial/toh-pt5.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/aio/content/tutorial/toh-pt5.md b/aio/content/tutorial/toh-pt5.md
index a1bedcaafe..31eddb0a82 100644
--- a/aio/content/tutorial/toh-pt5.md
+++ b/aio/content/tutorial/toh-pt5.md
@@ -213,8 +213,7 @@ The _class_ is similar to the `HeroesComponent` class.
 * The constructor expects Angular to inject the `HeroService` into a private `heroService` property.
 * The `ngOnInit()` lifecycle hook calls `getHeroes`.
 
-This `getHeroes` reduces the number of heroes displayed to four
-(2nd, 3rd, 4th, and 5th).
+This `getHeroes` returns the sliced list of heroes at positions 1 and 5, returning only four of the Top Heroes (2nd, 3rd, 4th, and 5th).
 
 <code-example path="toh-pt5/src/app/dashboard/dashboard.component.ts" region="getHeroes">
 </code-example>