aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/guide
diff options
context:
space:
mode:
authorveselinn2013-05-10 14:41:58 +0300
committerPete Bacon Darwin2013-05-10 20:52:18 +0100
commitac8ba104d4f8a20d107d184d81be83b2eaefec91 (patch)
treee81c565b20b8ddada572090448071fe8e300471e /docs/content/guide
parent67a4a25b890fada0043c1ff98e5437d793f44d0c (diff)
downloadangular.js-ac8ba104d4f8a20d107d184d81be83b2eaefec91.tar.bz2
docs(guide): fix a typo
Diffstat (limited to 'docs/content/guide')
-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: