aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVictor Berchet2014-02-10 15:16:46 +0100
committerCaitlin Potter2014-02-10 18:09:03 -0500
commit27613fd50020e6c9fe36b7622eb881fb34ce7dc6 (patch)
tree870e63a7231a8d7c7db10e38463d2c28e4f06d50
parente645f7cae14618bd8fc7d6b3eadf9307f5a1aeb7 (diff)
downloadangular.js-27613fd50020e6c9fe36b7622eb881fb34ce7dc6.tar.bz2
docs(guide/scope): fix a typo
Signed-off-by: Caitlin Potter <caitpotter88@gmail.com> Closes #6202
-rw-r--r--docs/content/guide/scope.ngdoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/guide/scope.ngdoc b/docs/content/guide/scope.ngdoc
index 4e395328..3d932fd9 100644
--- a/docs/content/guide/scope.ngdoc
+++ b/docs/content/guide/scope.ngdoc
@@ -333,7 +333,7 @@ information.
Dirty checking the scope for property changes is a common operation in Angular and for this reason
the dirty checking function must be efficient. Care should be taken that the dirty checking
-function does not do any DOM access, as DOM access is orders of magnitude slower then property
+function does not do any DOM access, as DOM access is orders of magnitude slower than property
access on JavaScript object.
## Integration with the browser event loop