@@ -115,7 +115,7 @@ To understand this, lets look at a real world example with repeater:
115115<pre>
116116 Hello {{user}}, you have these actions:
117117 <ul>
118- <li ng: repeat="action in user.actions">
118+ <li ng- repeat="action in user.actions">
119119 {{action.description}}
120120 </li>
121121 </ul>
@@ -126,8 +126,8 @@ a change in DOM structure such as in repeaters.
126126
127127When the above example is compiled, the compiler visits every node and looks for directives. The
128128`{{user}}` is an example of {@link angular.module.ng.$interpolate interpolation} directive. {@link
129- angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat} is another directive. But {@link
130- angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat} has a dilemma. It needs to be
129+ angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat} is another directive. But {@link
130+ angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat} has a dilemma. It needs to be
131131able to quickly stamp out new `li`s for every `action` in `user.actions`. This means that it needs
132132to save a clean copy of the `li` element for cloning purposes and as new `action`s are inserted,
133133the template `li` element needs to be cloned and inserted into `ul`. But cloning the `li` element
@@ -143,12 +143,12 @@ the directives are identified and sorted by priority, and a linking phase where
143143links a specific instance of the {@link angular.module.ng.$rootScope.Scope scope} and the specific
144144instance of an `li` is performed.
145145
146- {@link angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat} works by preventing the
146+ {@link angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat} works by preventing the
147147compilation process form descending into `li` element. Instead the {@link
148- angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat} directive compiles `li`
148+ angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat} directive compiles `li`
149149seperatly. The result of of the `li` element compilation is a linking function which contains all
150150of the directives contained in the `li` element ready to be attached to a specific clone of `li`
151- element. At runtime the {@link angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat}
151+ element. At runtime the {@link angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat}
152152watches the expression and as items are added to the array it clones the `li` element, creates a
153153new {@link angular.module.ng.$rootScope.Scope scope} for the cloned `li` element and calls the
154154link function on the cloned `li`.
@@ -415,8 +415,8 @@ compiler}. The attributes are:
415415 append the template to the element.
416416
417417 * `transclude` - compile the content of the element and make it available to the directive.
418- Typically used with {@link api/angular.module.ng.$compileProvider.directive.ng: transclude
419- ng: transclude}. The advantage of transclusion is that the linking function receives a
418+ Typically used with {@link api/angular.module.ng.$compileProvider.directive.ng- transclude
419+ ng- transclude}. The advantage of transclusion is that the linking function receives a
420420 transclusion function which is pre-bound to the correct scope. In a typical setup the widget
421421 creates an `isolate` scope, but the transclusion is not a child, but a sibling of the `isolate`
422422 scope. This makes it possible for the widget to have private state, and the transclusion to
@@ -440,8 +440,8 @@ compiler}. The attributes are:
440440Compile function deals with transforming the template DOM. Since most directives do not do
441441template transformation, it is not used often. Examples which require compile functions are
442442directives which transform template DOM such as {@link
443- angular.module.ng.$compileProvider.directive.ng: repeat ng: repeat} or load the contents
444- asynchronously such as {@link angular.module.ng.$compileProvider.directive.ng: view ng: view}. The
443+ angular.module.ng.$compileProvider.directive.ng- repeat ng- repeat} or load the contents
444+ asynchronously such as {@link angular.module.ng.$compileProvider.directive.ng- view ng- view}. The
445445compile functions takes the following arguments.
446446
447447 * `tElement` - template element - The element where the directive has been declared. It is
0 commit comments