docs(*): simplify doc urls

we now have two types of namespaces:

- true namespace: angular.* - used for all global apis
- virtual namespace: ng.*, ngMock.*, ... - used for all DI modules

the virual namespaces have services under the second namespace level (e.g. ng.)
and filters and directives prefixed with filter: and directive: respectively
(e.g. ng.filter:orderBy, ng.directive:ngRepeat)

this simplifies urls and makes them a lot shorter while still avoiding name collisions

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/content/guide/compiler.ngdoc b/docs/content/guide/compiler.ngdoc
index 493b611f..afd4d115 100644
--- a/docs/content/guide/compiler.ngdoc
+++ b/docs/content/guide/compiler.ngdoc
@@ -4,10 +4,10 @@
 
 # Overview
 
-Angular's {@link api/angular.module.ng.$compile HTML compiler} allows the developer to teach the
+Angular's {@link api/ng.$compile HTML compiler} allows the developer to teach the
 browser new HTML syntax. The compiler allows you to attach behavior to any HTML element or attribute
 and even create new HTML element or attributes with custom behavior. Angular calls these behavior
-extensions {@link api/angular.module.ng.$compileProvider.directive directives}.
+extensions {@link api/ng.$compileProvider.directive directives}.
 
 HTML has a lot of constructs for formatting the HTML for static documents in declarative fashion.
 For example if something needs to be centered, there is no need to provide instructions to the
@@ -17,7 +17,7 @@ element to achieve the desired behavior. Such is the power of declarative langua
 
 But the declarative language is also limited, since it does not allow you to teach the browser new
 syntax. For example there is no easy way to get the browser to align the text at 1/3 the position
-instead of 1/2. What is needed is a way to teach browser new HTML syntax. 
+instead of 1/2. What is needed is a way to teach browser new HTML syntax.
 
 Angular comes pre-bundled with common directives which are useful for building any app. We also
 expect that you will create directives that are specific to your app. These extension become a
@@ -29,7 +29,7 @@ involved.
 
 # Compiler
 
-Compiler is an angular service which traverses the DOM looking for attributes. The compilation 
+Compiler is an angular service which traverses the DOM looking for attributes. The compilation
 process happens into two phases.
 
   1. **Compile:** traverse the DOM and collect all of the directives. The result is a linking
@@ -39,7 +39,7 @@ process happens into two phases.
   scope model are reflected in the view, and any user interactions with the view are reflected
   in the scope model. Making the scope model a single source of truth.
 
-Some directives such {@link api/angular.module.ng.$compileProvider.directive.ngRepeat
+Some directives such {@link api/ng.directive:ngRepeat
 `ng-repeat`} clone DOM elements once for each item in collection. Having a compile and link phase
 improves performance since the cloned template only needs to be compiled once, and then linked
 once for each clone instance.
@@ -50,7 +50,7 @@ once for each clone instance.
 Directive is a behavior which should be triggered when specific HTML constructs are encountered in
 compilation process. The directives can be placed in element names, attributes, class names, as
 well as comments. Here are some equivalent examples of invoking {@link
-api/angular.module.ng.$compileProvider.directive.ngBind `ng-bind`} directive.
+api/ng.directive:ngBind `ng-bind`} directive.
 
 <pre>
   <span ng-bind="exp"></span>
@@ -60,7 +60,7 @@ api/angular.module.ng.$compileProvider.directive.ngBind `ng-bind`} directive.
 </pre>
 
 Directive is just a function which executes when the compiler encounters it in the DOM. See {@link
-api/angular.module.ng.$compileProvider.directive directive API} for in depth documentation on how
+api/ng.$compileProvider.directive directive API} for in depth documentation on how
 to write directives.
 
 Here is a directive which makes any element draggable. Notice the `draggable` attribute on the
@@ -115,9 +115,9 @@ principles.
 
 # Understanding View
 
-There are many templating systems out there. Most of them consume a static string template and 
+There are many templating systems out there. Most of them consume a static string template and
 combine it with data, resulting in a new string. The resulting text is then `innerHTML`ed into
-an element. 
+an element.
 
 <img src="img/One_Way_Data_Binding.png">