From d6ee9f29e6dba2d85b4966de6b9c4608ffa507ce Mon Sep 17 00:00:00 2001 From: sten-bone <49705989+sten-bone@users.noreply.github.com> Date: Wed, 8 Jun 2022 10:12:06 -0500 Subject: [PATCH] docs: update example hero ID (#46304) The hero ID "11" does not correspond to any hero from the example mock heroes list described at https://angular.io/tutorial/toh-pt2#create-mock-heroes. ID 12 seems to be the more fitting ID to get the hero with name "Dr. Nice". PR Close #46304 --- aio/content/tutorial/toh-pt5.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aio/content/tutorial/toh-pt5.md b/aio/content/tutorial/toh-pt5.md index 27053343dcf..5415fc8c872 100644 --- a/aio/content/tutorial/toh-pt5.md +++ b/aio/content/tutorial/toh-pt5.md @@ -319,7 +319,7 @@ Here's the class after pruning away the dead code. Previously, the parent `HeroesComponent` set the `HeroDetailComponent.hero` property and the `HeroDetailComponent` displayed the hero. `HeroesComponent` doesn't do that anymore. -Now the router creates the `HeroDetailComponent` in response to a URL such as `~/detail/11`. +Now the router creates the `HeroDetailComponent` in response to a URL such as `~/detail/12`. The `HeroDetailComponent` needs a new way to obtain the hero-to-display. This section explains the following: @@ -389,7 +389,7 @@ You'll be able to re-implement `getHero()` as a real `Http` request without havi The browser refreshes and the application is working again. You can click a hero in the dashboard or in the heroes list and navigate to that hero's detail view. -If you paste `localhost:4200/detail/11` in the browser address bar, the router navigates to the detail view for the hero with `id: 11`, "Dr Nice". +If you paste `localhost:4200/detail/12` in the browser address bar, the router navigates to the detail view for the hero with `id: 12`, "Dr Nice".