From d91ea2c49968d92ffbd2c17687aff2545b2ae266 Mon Sep 17 00:00:00 2001 From: Nikita Potapenko Date: Fri, 8 Feb 2019 14:03:34 +0200 Subject: [PATCH] docs(core): fixed typo (#28618) PR Close #28618 --- aio/content/guide/hierarchical-dependency-injection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/hierarchical-dependency-injection.md b/aio/content/guide/hierarchical-dependency-injection.md index ceedcae7f6..72a101a4da 100644 --- a/aio/content/guide/hierarchical-dependency-injection.md +++ b/aio/content/guide/hierarchical-dependency-injection.md @@ -42,7 +42,7 @@ Learn more about dependency resolution through the injector hierarchy: *NgModule-level* providers can be specified with `@NgModule()` `providers` metadata option, or in the `@Injectable()` `providedIn` option (with some module other than the root `AppModule`). -Use the `@NgModule()` `provides` option if a module is [lazy loaded](guide/lazy-loading-ngmodules). The module's own injector is configured with the provider when that module is loaded, and Angular can inject the corresponding services in any class it creates in that module. If you use the `@Injectable()` option `providedIn: MyLazyloadModule`, the provider could be shaken out at compile time, if it is not used anywhere else in the app. +Use the `@NgModule()` `providers` option if a module is [lazy loaded](guide/lazy-loading-ngmodules). The module's own injector is configured with the provider when that module is loaded, and Angular can inject the corresponding services in any class it creates in that module. If you use the `@Injectable()` option `providedIn: MyLazyloadModule`, the provider could be shaken out at compile time, if it is not used anywhere else in the app. * Learn more about [tree-shakable providers](guide/dependency-injection-providers#tree-shakable-providers).