@@ -178,7 +178,7 @@ figure.image-display
178
178
179
179
Accordingly, dependencies provided in the root `AppComponent` can be injected into *any* component *anywhere* in the application.
180
180
181
- That isn't always desireable .
181
+ That isn't always desirable .
182
182
Sometimes we want to restrict service availability to a particular region of the application.
183
183
184
184
We can limit the scope of an injected service to a *branch* of the application hierarchy
@@ -277,7 +277,7 @@ a(id="qualify-dependency-lookup")
277
277
placing it in the `<ng-content>` slot of the `HeroBioComponent` template:
278
278
+ makeExample('cb-dependency-injection/ts/app/hero-bio.component.ts' ,'template' ,'app/hero-bio.component.ts (template)' )( format ='.' )
279
279
:marked
280
- It looks like this, with the heroe 's telephone number from `HeroContactComponent` projected above the hero description:
280
+ It looks like this, with the hero 's telephone number from `HeroContactComponent` projected above the hero description:
281
281
figure.image-display
282
282
img( src ="/resources/images/cookbooks/dependency-injection/hero-bio-and-content.png" alt ="bio and contact" )
283
283
:marked
@@ -308,7 +308,7 @@ figure.image-display
308
308
:marked
309
309
If we comment out the `@Host()` decorator, Angular now walks up the injector ancestor tree
310
310
until it finds the logger at the `AppComponent` level. The logger logic kicks in and the hero display updates
311
- with the gratuituous "!!!", indicating that the logger was found.
311
+ with the gratuitous "!!!", indicating that the logger was found.
312
312
figure.image-display
313
313
img( src ="/resources/images/cookbooks/dependency-injection/hero-bio-contact-no-host.png" alt ="Without @Host" )
314
314
:marked
@@ -367,7 +367,7 @@ figure.image-display
367
367
368
368
Where did the injector get that value?
369
369
It may already have that value in its internal container.
370
- It it doesn't, it may be able to make one with the help of a ***provider***.
370
+ If it doesn't, it may be able to make one with the help of a ***provider***.
371
371
A *provider* is a recipe for delivering a service associated with a *token*.
372
372
.l-sub-section
373
373
:marked
0 commit comments