From 7439b46c5a20b78f4c58ccd823b4707a591c9087 Mon Sep 17 00:00:00 2001 From: Stepan Suvorov Date: Wed, 16 Jan 2019 15:11:48 +0100 Subject: [PATCH] docs: fix explanation of Injectable decorator in architecture guide (#27480) PR Close #27480 --- aio/content/guide/architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/architecture.md b/aio/content/guide/architecture.md index 2728f3c09d..97774b74ef 100644 --- a/aio/content/guide/architecture.md +++ b/aio/content/guide/architecture.md @@ -73,7 +73,7 @@ Angular provides predefined pipes for common transformations, and you can also d ## Services and dependency injection -For data or logic that isn't associated with a specific view, and that you want to share across components, you create a *service* class. A service class definition is immediately preceded by the `@Injectable()` decorator. The decorator provides the metadata that allows your service to be *injected* into client components as a dependency. +For data or logic that isn't associated with a specific view, and that you want to share across components, you create a *service* class. A service class definition is immediately preceded by the `@Injectable()` decorator. The decorator provides the metadata that allows other providers to be **injected** as dependencies into your class. *Dependency injection* (DI) lets you keep your component classes lean and efficient. They don't fetch data from the server, validate user input, or log directly to the console; they delegate such tasks to services.