aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/api
diff options
context:
space:
mode:
authorIgor Minar2011-05-18 12:17:16 -0700
committerIgor Minar2011-06-06 22:52:00 -0700
commit924ffafc51cf53ddf97f13ad748bbbf6d80caf13 (patch)
tree39c5766ec887df80c3525d89aad1f4451f016c02 /docs/content/api
parent3616716615c058756a3ead9808275ce9d72b1707 (diff)
downloadangular.js-924ffafc51cf53ddf97f13ad748bbbf6d80caf13.tar.bz2
fixing broken links
Diffstat (limited to 'docs/content/api')
-rw-r--r--docs/content/api/angular.directive.ngdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/content/api/angular.directive.ngdoc b/docs/content/api/angular.directive.ngdoc
index 9a08e4c7..277830b9 100644
--- a/docs/content/api/angular.directive.ngdoc
+++ b/docs/content/api/angular.directive.ngdoc
@@ -32,8 +32,8 @@ attribute. So why have two different ways to do the same thing? The answer is th
matters, but we have no control over the order in which attributes are read. To solve this
we apply attribute widget before the directive.
-For example, consider this piece of HTML, which uses the directives `ng:repeat`, `ng:init`,
-and `ng:bind`:
+For example, consider this piece of HTML, which uses the `ng:repeat`, `ng:init`,
+and `ng:bind` widget and directives:
<pre>
<ul ng:init="people=['mike', 'mary']">
<li ng:repeat="person in people" ng:init="a=a+1" ng:bind="person"></li>
@@ -41,7 +41,7 @@ and `ng:bind`:
</pre>
Notice that the order of execution matters here. We need to execute
-{@link angular.directive.ng:repeat ng:repeat} before we run the
+{@link angular.widget.@ng:repeat ng:repeat} before we run the
{@link angular.directive.ng:init ng:init} and `ng:bind` on the `<li/>;`. This is because we
want to run the `ng:init="a=a+1` and `ng:bind="person"` once for each person in people. We
could not have used directive to create this template because attributes are read in an