Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Commit 8df47db

Browse files
docs(guide/scope): fix typo
Closes #10289
1 parent 013b522 commit 8df47db

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/content/guide/scope.ngdoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -345,7 +345,7 @@ access on JavaScript object.
345345
Dirty checking can be done with three strategies: By reference, by collection contents, and by value. The strategies differ in the kinds of changes they detect, and in their performance characteristics.
346346

347347
- Watching *by reference* ({@link
348-
ng.$rootScope.Scope#$watch scope.$watch} `(watchExpression, listener)`) detects a change when the whole value returned by the watch expression switches to a new value. If the value is an array or an object, changes inside it are not detected. This is the most efficient stategy.
348+
ng.$rootScope.Scope#$watch scope.$watch} `(watchExpression, listener)`) detects a change when the whole value returned by the watch expression switches to a new value. If the value is an array or an object, changes inside it are not detected. This is the most efficient strategy.
349349
- Watching *collection contents* ({@link
350350
ng.$rootScope.Scope#$watchCollection scope.$watchCollection} `(watchExpression, listener)`) detects changes that occur inside an array or an object: When items are added, removed, or reordered. The detection is shallow - it does not reach into nested collections. Watching collection contents is more expensive than watching by reference, because copies of the collection contents need to be maintained. However, the strategy attempts to minimize the amount of copying required.
351351
- Watching *by value* ({@link

0 commit comments

Comments
 (0)