From 5d9e573b3e3d8880238f412c1f886085c7d12a49 Mon Sep 17 00:00:00 2001 From: Matthew Hill Date: Mon, 4 May 2015 16:50:50 +0100 Subject: [PATCH] docs(annotations): differentiate between component definitions and component instances Closes #1661 --- modules/angular2/src/core/annotations_impl/annotations.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/angular2/src/core/annotations_impl/annotations.js b/modules/angular2/src/core/annotations_impl/annotations.js index ccde9f28bf..6b88d1a282 100644 --- a/modules/angular2/src/core/annotations_impl/annotations.js +++ b/modules/angular2/src/core/annotations_impl/annotations.js @@ -24,9 +24,9 @@ import {DEFAULT} from 'angular2/change_detection'; * - The terminal {@link Injector} cannot resolve dependencies. It either throws an error or, if the dependency was * specified as `@Optional`, returns `null`. * - The platform injector resolves browser singleton resources, such as: cookies, title, location, and others. - * - *Component Injectors*: Each `@Component` has its own {@link Injector}, and they follow the same parent-child hierarchy - * as the components in the DOM. - * - *Element Injectors*: Each component has a Shadow DOM. Within the Shadow DOM each element has an `ElementInjector` + * - *Component Injectors*: Each component instance has its own {@link Injector}, and they follow the same parent-child hierarchy + * as the component instances in the DOM. + * - *Element Injectors*: Each component instance has a Shadow DOM. Within the Shadow DOM each element has an `ElementInjector` * which follow the same parent-child hierarchy as the DOM elements themselves. * * When a template is instantiated, it also must instantiate the corresponding directives in a depth-first order. The