From 3ef4c3edea3a08bc8db1b69d9faff221c558aabf Mon Sep 17 00:00:00 2001 From: Thomas Grainger Date: Mon, 23 Jan 2017 11:08:07 +0000 Subject: [PATCH] component architecture results in many isolate scopes --- docs/content/guide/scope.ngdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/content/guide/scope.ngdoc b/docs/content/guide/scope.ngdoc index 6c1606f85f28..93abb20cd032 100644 --- a/docs/content/guide/scope.ngdoc +++ b/docs/content/guide/scope.ngdoc @@ -109,12 +109,12 @@ to test the behavior without being distracted by the rendering details. ## Scope Hierarchies Each Angular application has exactly one {@link ng.$rootScope root scope}, but -may have several child scopes. +may have many child scopes. -The application can have multiple scopes, because some {@link guide/directive directives} create -new child scopes (refer to directive documentation to see which directives create new scopes). -When new scopes are created, they are added as children of their parent scope. This creates a tree -structure which parallels the DOM where they're attached. +The application can have multiple scopes, because some {@link guide/directive directives} and all +components create new child scopes (refer to directive documentation to see which directives create +new scopes). When new scopes are created, they are added as children of their parent scope. This +creates a tree structure which parallels the DOM where they're attached. When Angular evaluates `{{name}}`, it first looks at the scope associated with the given element for the `name` property. If no such property is found, it searches the parent scope