aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorveselinn2013-05-10 14:41:58 +0300
committerPete Bacon Darwin2013-05-10 20:52:44 +0100
commitcc260e786401e4d18d9a9f231225d85163eac479 (patch)
treeb177b05141c58321ebf88f540821de00855046dc
parent42ce8f7f556808da3947aa0bb1c448bbe970bd36 (diff)
downloadangular.js-cc260e786401e4d18d9a9f231225d85163eac479.tar.bz2
docs(guide): fix a typo
-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 b2dd5e53..411384ff 100644
--- a/docs/content/guide/scope.ngdoc
+++ b/docs/content/guide/scope.ngdoc
@@ -165,7 +165,7 @@ Scopes are attached to the DOM as `$scope` data property, and can be retrieved f
purposes. (It is unlikely that one would need to retrieve scopes in this way inside the
application.) The location where the root scope is attached to the DOM is defined by the location
of {@link api/ng.directive:ngApp `ng-app`} directive. Typically
-`ng-app` is placed an the `<html>` element, but it can be placed on other elements as well, if,
+`ng-app` is placed on the `<html>` element, but it can be placed on other elements as well, if,
for example, only a portion of the view needs to be controlled by Angular.
To examine the scope in the debugger: