fix(docs): change all directive references to use the normalized names

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/content/api/angular.module.ng.$compileProvider.directive.ngdoc b/docs/content/api/angular.module.ng.$compileProvider.directive.ngdoc
index f66aa9a1..722372b2 100644
--- a/docs/content/api/angular.module.ng.$compileProvider.directive.ngdoc
+++ b/docs/content/api/angular.module.ng.$compileProvider.directive.ngdoc
@@ -126,8 +126,8 @@ a change in DOM structure such as in repeaters.
 
 When the above example is compiled, the compiler visits every node and looks for directives. The
 `{{user}}` is an example of {@link angular.module.ng.$interpolate interpolation} directive. {@link
-angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat} is another directive. But {@link
-angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat} has a dilemma. It needs to be
+angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat} is another directive. But {@link
+angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat} has a dilemma. It needs to be
 able to quickly stamp out new `li`s for every `action` in `user.actions`. This means that it needs
 to save a clean copy of the `li` element for cloning purposes and as new `action`s are inserted,
 the 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
 links a specific instance of the {@link angular.module.ng.$rootScope.Scope scope} and the specific
 instance of an `li` is performed.
 
-{@link angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat} works by preventing the
+{@link angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat} works by preventing the
 compilation process form descending into `li` element. Instead the {@link
-angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat} directive compiles `li`
+angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat} directive compiles `li`
 seperatly. The result of of the `li` element compilation is a linking function which contains all
 of the directives contained in the `li` element ready to be attached to a specific clone of `li`
-element. At runtime the {@link angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat}
+element. At runtime the {@link angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat}
 watches the expression and as items are added to the array it clones the `li` element, creates a
 new {@link angular.module.ng.$rootScope.Scope scope} for the cloned `li` element and calls the
 link function on the cloned `li`.
@@ -415,8 +415,8 @@ compiler}. The attributes are:
     append the template to the element.
 
   * `transclude` - compile the content of the element and make it available to the directive.
-    Typically used with {@link api/angular.module.ng.$compileProvider.directive.ng-transclude
-    ng-transclude}. The advantage of transclusion is that the linking function receives a
+    Typically used with {@link api/angular.module.ng.$compileProvider.directive.ngTransclude
+    ngTransclude}. The advantage of transclusion is that the linking function receives a
     transclusion function which is pre-bound to the correct scope. In a typical setup the widget
     creates an `isolate` scope, but the transclusion is not a child, but a sibling of the `isolate`
     scope. This makes it possible for the widget to have private state, and the transclusion to
@@ -440,8 +440,8 @@ compiler}. The attributes are:
 Compile function deals with transforming the template DOM. Since most directives do not do
 template transformation, it is not used often. Examples which require compile functions are
 directives which transform template DOM such as {@link
-angular.module.ng.$compileProvider.directive.ng-repeat ng-repeat} or load the contents
-asynchronously such as {@link angular.module.ng.$compileProvider.directive.ng-view ng-view}. The
+angular.module.ng.$compileProvider.directive.ngRepeat ngRepeat} or load the contents
+asynchronously such as {@link angular.module.ng.$compileProvider.directive.ngView ngView}. The
 compile functions takes the following arguments.
 
   * `tElement` - template element - The element where the directive has been declared. It is