docs(bike-shed-migration): fix url-based links refs to AUTO module

71 files changed, 243 insertions, 243 deletions

diff --git a/docs/content/error/cacheFactory/iid.ngdoc b/docs/content/error/cacheFactory/iid.ngdoc
index 838ff75e..62e985e8 100644
--- a/docs/content/error/cacheFactory/iid.ngdoc
+++ b/docs/content/error/cacheFactory/iid.ngdoc
@@ -3,6 +3,6 @@
 @fullName Invalid ID
 @description
 
-This error occurs when trying to create a new `cache` object via {@link api/ng.$cacheFactory} with an ID that was already used to create another cache object.
+This error occurs when trying to create a new `cache` object via {@link ng.$cacheFactory} with an ID that was already used to create another cache object.
 
 To resolve the error please use a different cache ID when calling `$cacheFactory`.
diff --git a/docs/content/error/compile/ctreq.ngdoc b/docs/content/error/compile/ctreq.ngdoc
index e3f46532..47c876a3 100644
--- a/docs/content/error/compile/ctreq.ngdoc
+++ b/docs/content/error/compile/ctreq.ngdoc
@@ -3,7 +3,7 @@
 @fullName Missing Required Controller
 @description
 
-This error occurs when {@link api/ng.$compile HTML compiler} tries to process a directive that specifies the {@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object `require` option} in a {@link api/ng.$compile#description_comprehensive-directive-api directive definition},
+This error occurs when {@link ng.$compile HTML compiler} tries to process a directive that specifies the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object `require` option} in a {@link ng.$compile#description_comprehensive-directive-api directive definition},
 but the required directive controller is not present on the current DOM element (or its ancestor element, if `^` was specified).
 
 To resolve this error ensure that there is no typo in the required controller name and that the required directive controller is present on the current element.
@@ -13,7 +13,7 @@ If the required controller is expected to be on a ancestor element, make ensure
 If the required controller is optionally requested, use `?` or `^?` to specify that.
 
 
-Example of a directive that requires {@link api/ng.directive:ngModel ngModel} controller:
+Example of a directive that requires {@link ng.directive:ngModel ngModel} controller:
 ```
 myApp.directive('myDirective', function() {
   return {
@@ -29,7 +29,7 @@ This directive can then be used as:
 ```
 
 
-Example of a directive that optionally requires a {@link api/ng.directive:form form} controller from an ancestor:
+Example of a directive that optionally requires a {@link ng.directive:form form} controller from an ancestor:
 ```
 myApp.directive('myDirective', function() {
   return {
diff --git a/docs/content/error/compile/iscp.ngdoc b/docs/content/error/compile/iscp.ngdoc
index 0bfe216b..1450dec9 100644
--- a/docs/content/error/compile/iscp.ngdoc
+++ b/docs/content/error/compile/iscp.ngdoc
@@ -21,5 +21,5 @@ myModule.directive('directiveName', function factory() {
 });
 ```
 
-Please refer to the {@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object
+Please refer to the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object
 `scope` option} of the directive definition documentation to learn more about the API.
diff --git a/docs/content/error/compile/nonassign.ngdoc b/docs/content/error/compile/nonassign.ngdoc
index 3870c2ed..3a7d996b 100644
--- a/docs/content/error/compile/nonassign.ngdoc
+++ b/docs/content/error/compile/nonassign.ngdoc
@@ -4,7 +4,7 @@
 @description
 
 This error occurs when a directive defines an isolate scope property
-(using the `=` mode in the {@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object
+(using the `=` mode in the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object
 `scope` option} of a directive definition) but the directive is used with an expression that is not-assignable.
 
 In order for the two-way data-binding to work, it must be possible to write new values back into the path defined with the expression.
diff --git a/docs/content/error/compile/selmulti.ngdoc b/docs/content/error/compile/selmulti.ngdoc
index 8154cc67..51221ad8 100644
--- a/docs/content/error/compile/selmulti.ngdoc
+++ b/docs/content/error/compile/selmulti.ngdoc
@@ -3,9 +3,9 @@
 @fullName Binding to Multiple Attribute
 @description
 
-Binding to the `multiple` attribute of `select` element is not supported since switching between multiple and single mode changes the {@link api/ng.directive:ngModel `ngModel`} object type from instance to array of instances which breaks the model semantics.
+Binding to the `multiple` attribute of `select` element is not supported since switching between multiple and single mode changes the {@link ng.directive:ngModel `ngModel`} object type from instance to array of instances which breaks the model semantics.
 
-If you need to use different types of `select` elements in your template based on some variable, please use {@link api/ng.directive:ngIf ngIf} or {@link api/ng.directive:ngSwitch ngSwitch} directives to select one of them to be used at runtime.
+If you need to use different types of `select` elements in your template based on some variable, please use {@link ng.directive:ngIf ngIf} or {@link ng.directive:ngSwitch ngSwitch} directives to select one of them to be used at runtime.
 
 
 Example with invalid usage:
diff --git a/docs/content/error/compile/tpload.ngdoc b/docs/content/error/compile/tpload.ngdoc
index 3e0da4ab..b2b4fb2d 100644
--- a/docs/content/error/compile/tpload.ngdoc
+++ b/docs/content/error/compile/tpload.ngdoc
@@ -3,9 +3,9 @@
 @fullName Error Loading Template
 @description
 
-This error occurs when {@link api/ng.$compile `$compile`} attempts to fetch a template from some URL, and the request fails.
+This error occurs when {@link ng.$compile `$compile`} attempts to fetch a template from some URL, and the request fails.
 
 To resolve this error, ensure that the URL of the template is spelled correctly and resolves to correct absolute URL.
 The [Chrome Developer Tools](https://developers.google.com/chrome-developer-tools/docs/network#network_panel_overview) might also be helpful in determining why the request failed.
 
-If you are using {@link api/ng.$templateCache} to pre-load templates, ensure that the cache was populated with the template.
+If you are using {@link ng.$templateCache} to pre-load templates, ensure that the cache was populated with the template.
diff --git a/docs/content/error/controller/noscp.ngdoc b/docs/content/error/controller/noscp.ngdoc
index 18a01e0c..26257546 100644
--- a/docs/content/error/controller/noscp.ngdoc
+++ b/docs/content/error/controller/noscp.ngdoc
@@ -3,7 +3,7 @@
 @fullName Missing $scope object
 @description
 
-This error occurs when {@link api/ng.$controller $controller} service is called in order to instantiate a new controller but no scope is provided via `$scope` property of the locals map.
+This error occurs when {@link ng.$controller $controller} service is called in order to instantiate a new controller but no scope is provided via `$scope` property of the locals map.
 
 Example of incorrect usage that leads to this error:
 ```
@@ -18,4 +18,4 @@ To fix the example above please provide a scope to the $controller call:
 $controller(MyController, {$scope, newScope});
 ```
 
-Please consult the {@link api/ng.$controller $controller} service api docs to learn more.
+Please consult the {@link ng.$controller $controller} service api docs to learn more.
diff --git a/docs/content/error/injector/cdep.ngdoc b/docs/content/error/injector/cdep.ngdoc
index 0e9769c4..0e6526b8 100644
--- a/docs/content/error/injector/cdep.ngdoc
+++ b/docs/content/error/injector/cdep.ngdoc
@@ -3,7 +3,7 @@
 @fullName Circular Dependency
 @description
 
-This error occurs when the {@link api/angular.injector $injector} tries to get
+This error occurs when the {@link angular.injector $injector} tries to get
 a service that depends on itself, either directly or indirectly. To fix this,
 construct your dependency chain such that there are no circular dependencies.
 
diff --git a/docs/content/error/injector/modulerr.ngdoc b/docs/content/error/injector/modulerr.ngdoc
index db3ca76b..4b92a5de 100644
--- a/docs/content/error/injector/modulerr.ngdoc
+++ b/docs/content/error/injector/modulerr.ngdoc
@@ -8,4 +8,4 @@ message above should provide additional context.
 
 In AngularJS `1.2.0` and later, `ngRoute` has been moved to its own module.
 If you are getting this error after upgrading to `1.2.x`, be sure that you've
-installed {@link api/ngRoute `ngRoute`}.
+installed {@link ngRoute `ngRoute`}.
diff --git a/docs/content/error/injector/nomod.ngdoc b/docs/content/error/injector/nomod.ngdoc
index 66e2a5ad..5f8fb1e6 100644
--- a/docs/content/error/injector/nomod.ngdoc
+++ b/docs/content/error/injector/nomod.ngdoc
@@ -5,7 +5,7 @@
 
 This error occurs when trying to "re-open" a module that has not yet been defined.
 
-To define a new module, call {@link api/angular.module angular.module} with a name
+To define a new module, call {@link angular.module angular.module} with a name
 and an array of dependent modules, like so:
 
 ```
diff --git a/docs/content/error/injector/pget.ngdoc b/docs/content/error/injector/pget.ngdoc
index c195767a..1772d348 100644
--- a/docs/content/error/injector/pget.ngdoc
+++ b/docs/content/error/injector/pget.ngdoc
@@ -22,5 +22,5 @@ angular.module("myApp", [])
   .provider('good', GoodProvider);
 ```
 
-For more information, refer to the {@link api/AUTO.$provide#methods_provider
+For more information, refer to the {@link auto.$provide#methods_provider
 $provide.provider} api doc.
\ No newline at end of file
diff --git a/docs/content/error/interpolate/noconcat.ngdoc b/docs/content/error/interpolate/noconcat.ngdoc
index c611b81a..0853544e 100644
--- a/docs/content/error/interpolate/noconcat.ngdoc
+++ b/docs/content/error/interpolate/noconcat.ngdoc
@@ -9,4 +9,4 @@ it hard to reason about whether some combination of concatenated values are
 unsafe to use and could easily lead to XSS.
 
 For more information about how AngularJS helps keep your app secure, refer to
-the {@link api/ng.$sce $sce} API doc.
\ No newline at end of file
+the {@link ng.$sce $sce} API doc.
\ No newline at end of file
diff --git a/docs/content/error/jqLite/nosel.ngdoc b/docs/content/error/jqLite/nosel.ngdoc
index 7009db6b..65df8f85 100644
--- a/docs/content/error/jqLite/nosel.ngdoc
+++ b/docs/content/error/jqLite/nosel.ngdoc
@@ -3,7 +3,7 @@
 @fullName Unsupported Selector Lookup
 @description
 
-In order to keep Angular small, Angular implements only a subset of the selectors in {@link api/angular.element#description_angulars-jqlite jqLite}.
+In order to keep Angular small, Angular implements only a subset of the selectors in {@link angular.element#description_angulars-jqlite jqLite}.
 This error occurs when a jqLite instance is invoked with a selector other than this subset.
 
 In order to resolve this error, rewrite your code to only use tag name selectors and manually traverse the DOM using the APIs provided by jqLite.
diff --git a/docs/content/error/location/ihshprfx.ngdoc b/docs/content/error/location/ihshprfx.ngdoc
index cb1189dd..8acab933 100644
--- a/docs/content/error/location/ihshprfx.ngdoc
+++ b/docs/content/error/location/ihshprfx.ngdoc
@@ -3,7 +3,7 @@
 @fullName Missing Hash Prefix
 @description
 
-This error occurs when {@link api/ng.$location $location} service is configured to use a hash prefix but this prefix was not present in a url that the `$location` service was asked to parse.
+This error occurs when {@link ng.$location $location} service is configured to use a hash prefix but this prefix was not present in a url that the `$location` service was asked to parse.
 
 For example if you configure `$location` service with prefix `'!'`:
 ```
diff --git a/docs/content/error/location/ipthprfx.ngdoc b/docs/content/error/location/ipthprfx.ngdoc
index afbcda3f..55b75d86 100644
--- a/docs/content/error/location/ipthprfx.ngdoc
+++ b/docs/content/error/location/ipthprfx.ngdoc
@@ -3,6 +3,6 @@
 @fullName Invalid or Missing Path Prefix
 @description
 
-This error occurs when you configure the {@link api/ng.$location `$location`} service in the html5 mode, specify a base url for your application via `<base>` element and try to update the location with a path that doesn't match the base prefix.
+This error occurs when you configure the {@link ng.$location `$location`} service in the html5 mode, specify a base url for your application via `<base>` element and try to update the location with a path that doesn't match the base prefix.
 
 To resolve this issue, please check the base url specified via the `<base>` tag in the head of your main html document, as well as the url that you tried to set the location to.
diff --git a/docs/content/error/location/isrcharg.ngdoc b/docs/content/error/location/isrcharg.ngdoc
index 4f6f4b43..4b60ddd5 100644
--- a/docs/content/error/location/isrcharg.ngdoc
+++ b/docs/content/error/location/isrcharg.ngdoc
@@ -6,4 +6,4 @@
 To resolve this error, ensure that the first argument for the `$location.search` call is a `string` or an object.
 You can use the stack trace associated with this error to identify the call site that caused this issue.
 
-To learn more, please consult the {@link api/ng.$location `$location`} api docs.
+To learn more, please consult the {@link ng.$location `$location`} api docs.
diff --git a/docs/content/error/ngModel/nonassign.ngdoc b/docs/content/error/ngModel/nonassign.ngdoc
index 33894c49..cc6e3f71 100644
--- a/docs/content/error/ngModel/nonassign.ngdoc
+++ b/docs/content/error/ngModel/nonassign.ngdoc
@@ -3,7 +3,7 @@
 @fullName Non-Assignable Expression
 @description
 
-This error occurs when expression the {@link api/ng.directive:ngModel ngModel} directive is bound to is a non-assignable expression.
+This error occurs when expression the {@link ng.directive:ngModel ngModel} directive is bound to is a non-assignable expression.
 
 Examples using assignable expressions include:
 
@@ -24,4 +24,4 @@ Examples of non-assignable expressions include:
 
 Always make sure that the expression bound via `ngModel` directive can be assigned to.
 
-For more information, see the {@link api/ng.directive:ngModel ngModel API doc}.
+For more information, see the {@link ng.directive:ngModel ngModel API doc}.
diff --git a/docs/content/error/ngOptions/iexp.ngdoc b/docs/content/error/ngOptions/iexp.ngdoc
index a4515048..47f387d8 100644
--- a/docs/content/error/ngOptions/iexp.ngdoc
+++ b/docs/content/error/ngOptions/iexp.ngdoc
@@ -10,4 +10,4 @@ Here's an example of correct syntax:
 <select ng-model="color" ng-options="c.name for c in colors">
 ```
 
-For more information on valid expression syntax, see 'ngOptions' in {@link api/ng.directive:select select} directive docs.
+For more information on valid expression syntax, see 'ngOptions' in {@link ng.directive:select select} directive docs.
diff --git a/docs/content/error/ngPattern/noregexp.ngdoc b/docs/content/error/ngPattern/noregexp.ngdoc
index 6adb14db..d9f7b8d8 100644
--- a/docs/content/error/ngPattern/noregexp.ngdoc
+++ b/docs/content/error/ngPattern/noregexp.ngdoc
@@ -4,4 +4,4 @@
 @description
 This error occurs when 'ngPattern' is passed an expression that isn't a regular expression or doesn't have the expected format.
 
-For more information on valid expression syntax, see 'ngPattern' in {@link api/ng.directive:input input} directive docs.
+For more information on valid expression syntax, see 'ngPattern' in {@link ng.directive:input input} directive docs.
diff --git a/docs/content/error/ngRepeat/dupes.ngdoc b/docs/content/error/ngRepeat/dupes.ngdoc
index 175cd676..d3d2186b 100644
--- a/docs/content/error/ngRepeat/dupes.ngdoc
+++ b/docs/content/error/ngRepeat/dupes.ngdoc
@@ -3,7 +3,7 @@
 @fullName Duplicate Key in Repeater
 @description
 
-Occurs if there are duplicate keys in an {@link api/ng.directive:ngRepeat ngRepeat} expression.  Duplicate keys are banned because AngularJS uses keys to associate DOM nodes with items.
+Occurs if there are duplicate keys in an {@link ng.directive:ngRepeat ngRepeat} expression.  Duplicate keys are banned because AngularJS uses keys to associate DOM nodes with items.
 
 By default, collections are keyed by reference which is desirable for most common models but can be problematic for primitive types that are interned (share references).
 
diff --git a/docs/content/error/ngRepeat/iexp.ngdoc b/docs/content/error/ngRepeat/iexp.ngdoc
index ec3c361a..74442b9f 100644
--- a/docs/content/error/ngRepeat/iexp.ngdoc
+++ b/docs/content/error/ngRepeat/iexp.ngdoc
@@ -3,10 +3,10 @@
 @fullName Invalid Expression
 @description
 
-Occurs when there is a syntax error in an {@link api/ng.directive:ngRepeat ngRepeat}'s expression. The expression should be in the form '_item_ in _collection_[ track by _id_]'.
+Occurs when there is a syntax error in an {@link ng.directive:ngRepeat ngRepeat}'s expression. The expression should be in the form '_item_ in _collection_[ track by _id_]'.
 
 Be aware, the ngRepeat directive parses the expression using a regex before sending _collection_ and optionally _id_ to the AngularJS parser.  This error comes from the regex parsing.
 
 To resolve, identify and fix errors in the expression, paying special attention to the 'in' and 'track by' keywords in the expression.
 
-Please consult the api documentation of {@link api/ng.directive:ngRepeat ngRepeat} to learn more about valid syntax.
+Please consult the api documentation of {@link ng.directive:ngRepeat ngRepeat} to learn more about valid syntax.
diff --git a/docs/content/error/ngRepeat/iidexp.ngdoc b/docs/content/error/ngRepeat/iidexp.ngdoc
index 8d9309e2..641f723d 100644
--- a/docs/content/error/ngRepeat/iidexp.ngdoc
+++ b/docs/content/error/ngRepeat/iidexp.ngdoc
@@ -3,7 +3,7 @@
 @fullName Invalid Identifier
 @description
 
-Occurs when there is an error in the identifier part of {@link api/ng.directive:ngRepeat ngRepeat}'s expression.
+Occurs when there is an error in the identifier part of {@link ng.directive:ngRepeat ngRepeat}'s expression.
 
 To resolve, use either a valid identifier or a tuple (_key_, _value_) where both _key_ and _value_ are valid identifiers.
 
@@ -22,4 +22,4 @@ Examples of *valid* syntax:
 <div ng-repeat="(id, user) in userMap"></div>
 ```
 
-Please consult the api documentation of {@link api/ng.directive:ngRepeat ngRepeat} to learn more about valid syntax.
+Please consult the api documentation of {@link ng.directive:ngRepeat ngRepeat} to learn more about valid syntax.
diff --git a/docs/content/error/resource/badargs.ngdoc b/docs/content/error/resource/badargs.ngdoc
index a9a3f213..834c7826 100644
--- a/docs/content/error/resource/badargs.ngdoc
+++ b/docs/content/error/resource/badargs.ngdoc
@@ -3,7 +3,7 @@
 @fullName Too Many Arguments
 @description
 
-This error occurs when specifying too many arguments to a {@link api/ngResource.$resource `$resource`} action, such as `get`, `query` or any user-defined custom action.
+This error occurs when specifying too many arguments to a {@link ngResource.$resource `$resource`} action, such as `get`, `query` or any user-defined custom action.
 These actions may take up to 4 arguments.
 
-For more information, refer to the {@link api/ngResource.$resource `$resource`} API reference documentation.
+For more information, refer to the {@link ngResource.$resource `$resource`} API reference documentation.
diff --git a/docs/content/error/resource/badcfg.ngdoc b/docs/content/error/resource/badcfg.ngdoc
index 82e87504..87e1ed26 100644
--- a/docs/content/error/resource/badcfg.ngdoc
+++ b/docs/content/error/resource/badcfg.ngdoc
@@ -3,9 +3,9 @@
 @fullName Response does not match configured parameter
 @description
 
-This error occurs when the {@link api/ngResource.$resource `$resource`} service expects a response that can be deserialized as an array, receives an object, or vice versa.
+This error occurs when the {@link ngResource.$resource `$resource`} service expects a response that can be deserialized as an array, receives an object, or vice versa.
 By default, all resource actions expect objects, except `query` which expects arrays.
 
 To resolve this error, make sure your `$resource` configuration matches the actual format of the data returned from the server.
 
-For more information, see the {@link api/ngResource.$resource `$resource`} API reference documentation.
+For more information, see the {@link ngResource.$resource `$resource`} API reference documentation.
diff --git a/docs/content/error/rootScope/infdig.ngdoc b/docs/content/error/rootScope/infdig.ngdoc
index 137bc120..e36f1d69 100644
--- a/docs/content/error/rootScope/infdig.ngdoc
+++ b/docs/content/error/rootScope/infdig.ngdoc
@@ -14,4 +14,4 @@ $scope.$watch('foo', function() {
 });
 ```
 
-The maximum number of allowed iterations of the `$digest` cycle is controlled via TTL setting which can be configured via {@link api/ng.$rootScopeProvider $rootScopeProvider}.
+The maximum number of allowed iterations of the `$digest` cycle is controlled via TTL setting which can be configured via {@link ng.$rootScopeProvider $rootScopeProvider}.
diff --git a/docs/content/error/rootScope/inprog.ngdoc b/docs/content/error/rootScope/inprog.ngdoc
index c3f42c12..375f8fe8 100644
--- a/docs/content/error/rootScope/inprog.ngdoc
+++ b/docs/content/error/rootScope/inprog.ngdoc
@@ -71,4 +71,4 @@ myApp.directive('myDirective', function() {
 
 ```
 
-To learn more about Angular processing model please check out the {@link guide/concepts concepts doc} as well as the {@link api/ng.$rootScope.Scope api} doc.
+To learn more about Angular processing model please check out the {@link guide/concepts concepts doc} as well as the {@link ng.$rootScope.Scope api} doc.
diff --git a/docs/content/error/sce/icontext.ngdoc b/docs/content/error/sce/icontext.ngdoc
index 3ce8eccd..e30b6ad4 100644
--- a/docs/content/error/sce/icontext.ngdoc
+++ b/docs/content/error/sce/icontext.ngdoc
@@ -3,6 +3,6 @@
 @fullName Invalid / Unknown SCE context
 @description
 
-The context enum passed to {@link api/ng.$sce#methods_trustAs $sce.trustAs} was not recognized.
+The context enum passed to {@link ng.$sce#methods_trustAs $sce.trustAs} was not recognized.
 
-Please consult the list of {@link api/ng.$sce#contexts supported Strict Contextual Escaping (SCE) contexts}.
+Please consult the list of {@link ng.$sce#contexts supported Strict Contextual Escaping (SCE) contexts}.
diff --git a/docs/content/error/sce/iequirks.ngdoc b/docs/content/error/sce/iequirks.ngdoc
index 8713630b..08afbf66 100644
--- a/docs/content/error/sce/iequirks.ngdoc
+++ b/docs/content/error/sce/iequirks.ngdoc
@@ -3,7 +3,7 @@
 @fullName IE8 in quirks mode is unsupported
 @description
 
-This error occurs when you are using AngularJS with {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode.
+This error occurs when you are using AngularJS with {@link ng.$sce Strict Contextual Escaping (SCE)} mode enabled (the default) on IE8 or lower in quirks mode.
 
 In this mode, IE8 allows one to execute arbitrary javascript by the use of the `expression()` syntax and is not supported.
 Refer
diff --git a/docs/content/error/sce/imatcher.ngdoc b/docs/content/error/sce/imatcher.ngdoc
index 86d27f13..eabdbc53 100644
--- a/docs/content/error/sce/imatcher.ngdoc
+++ b/docs/content/error/sce/imatcher.ngdoc
@@ -3,7 +3,7 @@
 @fullName Invalid matcher (only string patterns and RegExp instances are supported)
 @description
 
-Please see {@link api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist
+Please see {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist
 $sceDelegateProvider.resourceUrlWhitelist} and {@link
 api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the
 list of acceptable items.
diff --git a/docs/content/error/sce/insecurl.ngdoc b/docs/content/error/sce/insecurl.ngdoc
index c8cc7a4c..67bbb2b6 100644
--- a/docs/content/error/sce/insecurl.ngdoc
+++ b/docs/content/error/sce/insecurl.ngdoc
@@ -3,16 +3,16 @@
 @fullName Processing of a Resource from Untrusted Source Blocked
 @description
 
-AngularJS' {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
+AngularJS' {@link ng.$sce Strict Contextual Escaping (SCE)} mode (enabled by default) has blocked loading a resource from an insecure URL.
 
 Typically, this would occur if you're attempting to load an Angular template from an untrusted source.
 It's also possible that a custom directive threw this error for a similar reason.
 
-Angular only loads templates from trusted URLs (by calling {@link api/ng.$sce#methods_getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
+Angular only loads templates from trusted URLs (by calling {@link ng.$sce#methods_getTrustedResourceUrl $sce.getTrustedResourceUrl} on the template URL).
 
 By default, only URLs that belong to the same origin are trusted. These are urls with the same domain and protocol as the application document.
 
-The {@link api/ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL.
+The {@link ng.directive:ngInclude ngInclude} directive and {@link guide/directive directives} that specify a `templateUrl` require a trusted resource URL.
 
 To load templates from other domains and/or protocols, either adjust the {@link
 api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist whitelist}/ {@link
diff --git a/docs/content/error/sce/itype.ngdoc b/docs/content/error/sce/itype.ngdoc
index 04106afa..cc2a6f62 100644
--- a/docs/content/error/sce/itype.ngdoc
+++ b/docs/content/error/sce/itype.ngdoc
@@ -3,6 +3,6 @@
 @fullName String Value is Required for SCE Trust Call
 @description
 
-{@link api/ng.$sce#methods_trustAs $sce.trustAs} requires a string value.
+{@link ng.$sce#methods_trustAs $sce.trustAs} requires a string value.
 
-Read more about {@link api/ng.$sce Strict Contextual Escaping (SCE)} in AngularJS.
+Read more about {@link ng.$sce Strict Contextual Escaping (SCE)} in AngularJS.
diff --git a/docs/content/error/sce/iwcard.ngdoc b/docs/content/error/sce/iwcard.ngdoc
index 4b0b5192..83facf1d 100644
--- a/docs/content/error/sce/iwcard.ngdoc
+++ b/docs/content/error/sce/iwcard.ngdoc
@@ -3,7 +3,7 @@
 @fullName The sequence *** is not a valid pattern wildcard
 @description
 
-The strings in {@link api/ng.$sceDelegateProvider#methods_resourceUrlWhitelist
+The strings in {@link ng.$sceDelegateProvider#methods_resourceUrlWhitelist
 $sceDelegateProvider.resourceUrlWhitelist} and {@link
 api/ng.$sceDelegateProvider#methods_resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not
 contain the undefined sequence `***`.  Only `*` and `**` wildcard patterns are defined.
diff --git a/docs/content/error/sce/unsafe.ngdoc b/docs/content/error/sce/unsafe.ngdoc
index 7ebd2c0c..fdddf61b 100644
--- a/docs/content/error/sce/unsafe.ngdoc
+++ b/docs/content/error/sce/unsafe.ngdoc
@@ -5,7 +5,7 @@
 
 The value provided for use in a specific context was not found to be safe/trusted for use.
 
-Angular's {@link api/ng.$sce Strict Contextual Escaping (SCE)} mode
+Angular's {@link ng.$sce Strict Contextual Escaping (SCE)} mode
 (enabled by default), requires bindings in certain
 contexts to result in a value that is trusted as safe for use in such a context.  (e.g. loading an
 Angular template from a URL requires that the URL is one considered safe for loading resources.)
diff --git a/docs/content/guide/animations.ngdoc b/docs/content/guide/animations.ngdoc
index a9dd6ac6..0cf08eb7 100644
--- a/docs/content/guide/animations.ngdoc
+++ b/docs/content/guide/animations.ngdoc
@@ -11,7 +11,7 @@ triggered, will attempt to perform a CSS Transition, CSS Keyframe Animation or a
 placed on the given directive). Animations can be placed using vanilla CSS by following the naming conventions set in place by AngularJS
 or with JavaScript code when it's defined as a factory.
 
-Animations are not available unless you include the {@link api/ngAnimate `ngAnimate` module} as a dependency within your application.
+Animations are not available unless you include the {@link ngAnimate `ngAnimate` module} as a dependency within your application.
 
 Below is a quick example of animations being enabled for `ngShow` and `ngHide`:
 
@@ -55,7 +55,7 @@ Below is a quick example of animations being enabled for `ngShow` and `ngHide`:
 
 ## Installation
 
-See the {@link api/ngAnimate API docs for `ngAnimate`} for instructions on installing the module.
+See the {@link ngAnimate API docs for `ngAnimate`} for instructions on installing the module.
 
 You may also want to setup a separate CSS file for defining CSS-based animations.
 
@@ -253,15 +253,15 @@ The table below explains in detail which animation events are triggered
 
 | Directive                                                                           | Supported Animations                     |
 |-------------------------------------------------------------------------------------|------------------------------------------|
-| {@link api/ng.directive:ngRepeat#usage_animations ngRepeat}                               | enter, leave, and move                   |
-| {@link api/ngRoute.directive:ngView#usage_animations ngView}                              | enter and leave                          |
-| {@link api/ng.directive:ngInclude#usage_animations ngInclude}                             | enter and leave                          |
-| {@link api/ng.directive:ngSwitch#usage_animations ngSwitch}                               | enter and leave                          |
-| {@link api/ng.directive:ngIf#usage_animations ngIf}                                       | enter and leave                          |
-| {@link api/ng.directive:ngClass#usage_animations ngClass or &#123;&#123;class&#125;&#125;} | add and remove                           |
-| {@link api/ng.directive:ngShow#usage_animations ngShow & ngHide}                          | add and remove (the ng-hide class value) |
+| {@link ng.directive:ngRepeat#usage_animations ngRepeat}                               | enter, leave, and move                   |
+| {@link ngRoute.directive:ngView#usage_animations ngView}                              | enter and leave                          |
+| {@link ng.directive:ngInclude#usage_animations ngInclude}                             | enter and leave                          |
+| {@link ng.directive:ngSwitch#usage_animations ngSwitch}                               | enter and leave                          |
+| {@link ng.directive:ngIf#usage_animations ngIf}                                       | enter and leave                          |
+| {@link ng.directive:ngClass#usage_animations ngClass or &#123;&#123;class&#125;&#125;} | add and remove                           |
+| {@link ng.directive:ngShow#usage_animations ngShow & ngHide}                          | add and remove (the ng-hide class value) |
 
-For a full breakdown of the steps involved during each animation event, refer to the {@link api/ngAnimate.$animate API docs}.
+For a full breakdown of the steps involved during each animation event, refer to the {@link ngAnimate.$animate API docs}.
 
 ## How do I use animations in my own directives?
 
@@ -284,6 +284,6 @@ myModule.directive('my-directive', ['$animate', function($animate) {
 
 ## More about animations
 
-For a full breakdown of each method available on `$animate`, see the {@link api/ngAnimate.$animate API documentation}.
+For a full breakdown of each method available on `$animate`, see the {@link ngAnimate.$animate API documentation}.
 
 To see a complete demo, see the {@link tutorial/step_12 animation step within the AngularJS phonecat tutorial}.
diff --git a/docs/content/guide/bootstrap.ngdoc b/docs/content/guide/bootstrap.ngdoc
index d5098a23..7458762f 100644
--- a/docs/content/guide/bootstrap.ngdoc
+++ b/docs/content/guide/bootstrap.ngdoc
@@ -55,12 +55,12 @@ initialization.
 
 Angular initializes automatically upon `DOMContentLoaded` event or when the `angular.js` script is
 evaluated if at that time `document.readyState` is set to `'complete'`. At this point Angular looks
-for the {@link api/ng.directive:ngApp `ng-app`} directive which designates your application root.
-If the {@link api/ng.directive:ngApp `ng-app`} directive is found then Angular will:
+for the {@link ng.directive:ngApp `ng-app`} directive which designates your application root.
+If the {@link ng.directive:ngApp `ng-app`} directive is found then Angular will:
 
   * load the {@link guide/module module} associated with the directive.
-  * create the application {@link api/AUTO.$injector injector}
-  * compile the DOM treating the {@link api/ng.directive:ngApp
+  * create the application {@link auto.$injector injector}
+  * compile the DOM treating the {@link ng.directive:ngApp
     `ng-app`} directive as the root of the compilation. This allows you to tell it to treat only a
     portion of the DOM as an Angular application.
 
@@ -103,7 +103,7 @@ Here is an example of manually initializing Angular:
 ```
 
 Note that we have provided the name of our application module to be loaded into the injector as the second
-parameter of the {@link api/angular.bootstrap} function. Notice that `angular.bootstrap` will not create modules 
+parameter of the {@link angular.bootstrap} function. Notice that `angular.bootstrap` will not create modules 
 on the fly. You must create any custom {@link guide/module modules} before you pass them as a parameter. 
 
 This is the sequence that your code should follow:
@@ -111,7 +111,7 @@ This is the sequence that your code should follow:
   1. After the page and all of the code is loaded, find the root element of your AngularJS
   application, which is typically the root of the document.
 
-  2. Call {@link api/angular.bootstrap} to {@link compiler compile} the element into an
+  2. Call {@link angular.bootstrap} to {@link compiler compile} the element into an
   executable, bi-directionally bound application.
 
 ## Deferred Bootstrap
@@ -122,7 +122,7 @@ into the DI registry which can replace or augment DI services for
 the purpose of instrumentation or mocking out heavy dependencies.
 
 If `window.name` contains prefix `NG_DEFER_BOOTSTRAP!` when
-{@link api/angular.bootstrap} is called, the bootstrap process will be paused
+{@link angular.bootstrap} is called, the bootstrap process will be paused
 until `angular.resumeBootstrap()` is called.
 
 `angular.resumeBootstrap()` takes an optional array of modules that
diff --git a/docs/content/guide/compiler.ngdoc b/docs/content/guide/compiler.ngdoc
index 8defadcf..8a17bef0 100644
--- a/docs/content/guide/compiler.ngdoc
+++ b/docs/content/guide/compiler.ngdoc
@@ -13,10 +13,10 @@ If you want a deeper look into Angular's compilation process, you're in the righ
 
 # Overview
 
-Angular's {@link api/ng.$compile HTML compiler} allows the developer to teach the
+Angular's {@link 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 elements or attributes with custom behavior. Angular calls these behavior
-extensions {@link api/ng.$compileProvider#methods_directive directives}.
+extensions {@link ng.$compileProvider#methods_directive directives}.
 
 HTML has a lot of constructs for formatting the HTML for static documents in a declarative fashion.
 For example if something needs to be centered, there is no need to provide instructions to the
@@ -48,7 +48,7 @@ process happens in two phases.
   scope model are reflected in the view, and any user interactions with the view are reflected
   in the scope model. This makes the scope model the single source of truth.
 
-Some directives such as {@link api/ng.directive:ngRepeat `ng-repeat`} clone DOM elements once
+Some directives such as {@link ng.directive:ngRepeat `ng-repeat`} clone DOM elements once
 for each item in a 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.
 
@@ -164,7 +164,7 @@ Angular's `$compile` service.
 
 HTML compilation happens in three phases:
 
-  1. {@link api/ng.$compile `$compile`} traverses the DOM and matches directives.
+  1. {@link ng.$compile `$compile`} traverses the DOM and matches directives.
 
   If the compiler finds that an element matches a directive, then the directive is added to the list of
   directives that match the DOM element. A single element may match multiple directives.
@@ -178,7 +178,7 @@ HTML compilation happens in three phases:
 
   3. `$compile` links the template with the scope by calling the combined linking function from the previous step.
   This in turn will call the linking function of the individual directives, registering listeners on the elements
-  and setting up {@link api/ng.$rootScope.Scope#methods_$watch `$watch`s} with the {@link api/ng.$rootScope.Scope `scope`}
+  and setting up {@link ng.$rootScope.Scope#methods_$watch `$watch`s} with the {@link ng.$rootScope.Scope `scope`}
   as each directive is configured to do.
 
 The result of this is a live binding between the scope and the DOM. So at this point, a change in
@@ -240,10 +240,10 @@ Hello {{user}}, you have these actions:
 
 When the above example is compiled, the compiler visits every node and looks for directives.
 
-`{{user}}` matches the {@link api/ng.$interpolate interpolation directive}
-and `ng-repeat` matches the {@link api/ng.directive:ngRepeat `ngRepeat` directive}.
+`{{user}}` matches the {@link ng.$interpolate interpolation directive}
+and `ng-repeat` matches the {@link ng.directive:ngRepeat `ngRepeat` directive}.
 
-But {@link api/ng.directive:ngRepeat ngRepeat} has a dilemma.
+But {@link ng.directive:ngRepeat ngRepeat} has a dilemma.
 
 It needs to be able to clone new `<li>` elements for every `action` in `user.actions`.
 This initially seems trivial, but it becomes more complicated when you consider that `user.actions`
@@ -252,7 +252,7 @@ element for cloning purposes.
 
 As new `action`s are inserted, the template `<li>` element needs to be cloned and inserted into `ul`.
 But cloning the `<li>` element is not enough. It also needs to compile the `<li>` so that its
-directives, like `{{action.description}}`, evaluate against the right {@link api/ng.$rootScope.Scope scope}.
+directives, like `{{action.description}}`, evaluate against the right {@link ng.$rootScope.Scope scope}.
 
 
 A naive approach to solving this problem would be to simply insert a copy of the `<li>` element and
@@ -266,25 +266,25 @@ The solution is to break the compilation process into two phases:
 
 the **compile phase** where all of the directives are identified and sorted by priority,
 and a **linking phase** where any work which "links" a specific instance of the
-{@link api/ng.$rootScope.Scope scope} and the specific instance of an `<li>` is performed.
+{@link ng.$rootScope.Scope scope} and the specific instance of an `<li>` is performed.
 
 <div class="alert alert-warning">
 **Note:** *Link* means setting up listeners on the DOM and setting up `$watch` on the Scope to
 keep the two in sync.
 </div>
 
-{@link api/ng.directive:ngRepeat `ngRepeat`} works by preventing the compilation process from
+{@link ng.directive:ngRepeat `ngRepeat`} works by preventing the compilation process from
 descending into the `<li>` element so it can make a clone of the original and handle inserting
 and removing DOM nodes itself.
 
-Instead the {@link api/ng.directive:ngRepeat `ngRepeat`} directive compiles `<li>` separately.
+Instead the {@link ng.directive:ngRepeat `ngRepeat`} directive compiles `<li>` separately.
 The result 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 the `<li>`
 element.
 
-At runtime the {@link api/ng.directive:ngRepeat `ngRepeat`} watches the expression and as items
+At runtime the {@link ng.directive:ngRepeat `ngRepeat`} watches the expression and as items
 are added to the array it clones the `<li>` element, creates a new
-{@link api/ng.$rootScope.Scope scope} for the cloned `<li>` element and calls the link function
+{@link ng.$rootScope.Scope scope} for the cloned `<li>` element and calls the link function
 on the cloned `<li>`.
 
 
diff --git a/docs/content/guide/concepts.ngdoc b/docs/content/guide/concepts.ngdoc
index 7154da39..105af400 100644
--- a/docs/content/guide/concepts.ngdoc
+++ b/docs/content/guide/concepts.ngdoc
@@ -60,11 +60,11 @@ The loaded, transformed and rendered DOM is then called the <a name="view">"view
 
 The first kind of new markup are the so called <a name="directive">"{@link directive directives}"</a>.
 They apply special behavior to attributes or elements in the HTML. In the example above we use the
-{@link api/ng.directive:ngApp `ng-app`} attribute, which is linked to a directive that automatically
-initializes our application. Angular also defines a directive for the {@link api/ng.directive:input `input`}
+{@link ng.directive:ngApp `ng-app`} attribute, which is linked to a directive that automatically
+initializes our application. Angular also defines a directive for the {@link ng.directive:input `input`}
 element that adds extra behavior to the element. E.g. it is able to automatically validate that the entered
 text is non empty by evaluating the `required` attribute.
-The {@link api/ng.directive:ngModel `ng-model`} directive stores/updates
+The {@link ng.directive:ngModel `ng-model`} directive stores/updates
 the value of the input field into/from a variable and shows the validation state of the input field by
 adding css classes. In the example we use these css classes to mark an empty input field with a red border.
 
@@ -88,7 +88,7 @@ and multiply them together".
 
 The example above also contains a <a name="filter">"{@link filter filter}"</a>.
 A filter formats the value of an expression for display to the user.
-In the example above, the filter {@link api/ng.filter:currency `currency`} formats a number
+In the example above, the filter {@link ng.filter:currency `currency`} formats a number
 into an output that looks like money.
 
 The important thing in the example is that angular provides _live_ bindings:
@@ -157,7 +157,7 @@ More exactly, the file contains a constructor function that creates the actual c
 The purpose of controllers is to expose variables and functionality to expressions and directives.
 
 Besides the new file that contains the controller code we also added a
-{@link api/ng.directive:ngController `ng-controller`} directive to the HTML.
+{@link ng.directive:ngController `ng-controller`} directive to the HTML.
 This directive tells angular that the new `InvoiceController` is responsible for the element with the directive
 and all of the element's children.
 The syntax `InvoiceController as invoice` tells Angular to instantiate the controller
@@ -165,13 +165,13 @@ and save it in the variable `invoice` in the current scope.
 
 We also changed all expressions in the page to read and write variables within that
 controller instance by prefixing them with `invoice.` . The possible currencies are defined in the controller
-and added to the template using {@link api/ng.directive:ngRepeat `ng-repeat`}.
+and added to the template using {@link ng.directive:ngRepeat `ng-repeat`}.
 As the controller contains a `total` function
 we are also able to bind the result of that function to the DOM using `{{ invoice.total(...) }}`.
 
 Again, this binding is live, i.e. the DOM will be automatically updated
 whenever the result of the function changes.
-The button to pay the invoice uses the directive {@link api/ng.directive:ngClick `ngClick`}. This will evaluate the
+The button to pay the invoice uses the directive {@link ng.directive:ngClick `ngClick`}. This will evaluate the
 corresponding expression whenever the button is clicked.
 
 In the new JavaScript file we are also creating a {@link concepts#module module}
@@ -380,7 +380,7 @@ The following example shows how this is done with Angular:
 
 What changed?
 Our `currencyConverter` service of the `finance` module now uses the
-{@link api/ng.$http $http} service, a builtin service provided by Angular
+{@link ng.$http $http} service, a builtin service provided by Angular
 for accessing the backend. It is a wrapper around [`XMLHttpRequest`](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest)
 and [JSONP](http://en.wikipedia.org/wiki/JSONP) transports. Details can be found in the api docs of that service.
 
diff --git a/docs/content/guide/controller.ngdoc b/docs/content/guide/controller.ngdoc
index 01f5299f..04dcf56c 100644
--- a/docs/content/guide/controller.ngdoc
+++ b/docs/content/guide/controller.ngdoc
@@ -7,7 +7,7 @@
 In Angular, a Controller is a JavaScript **constructor function** that is used to augment the 
 {@link scope Angular Scope}.
 
-When a Controller is attached to the DOM via the {@link api/ng.directive:ngController ng-controller}
+When a Controller is attached to the DOM via the {@link ng.directive:ngController ng-controller}
 directive, Angular will instantiate a new Controller object, using the specified Controller's
 **constructor function**.  A new **child scope** will be available as an injectable parameter to the
 Controller's constructor function as `$scope`.
@@ -88,7 +88,7 @@ expression in the template:
 As discussed in the {@link concepts Concepts} section of this guide, any
 objects (or primitives) assigned to the scope become model properties. Any methods assigned to
 the scope are available in the template/view, and can be invoked via angular expressions
-and `ng` event handler directives (e.g. {@link api/ng.directive:ngClick ngClick}).
+and `ng` event handler directives (e.g. {@link ng.directive:ngClick ngClick}).
 
 # Using Controllers Correctly
 
@@ -117,8 +117,8 @@ services} instead.
 
 # Associating Controllers with Angular Scope Objects
 
-You can associate Controllers with scope objects implicitly via the {@link api/ng.directive:ngController ngController
-directive} or {@link api/ngRoute.$route $route service}.
+You can associate Controllers with scope objects implicitly via the {@link ng.directive:ngController ngController
+directive} or {@link ngRoute.$route $route service}.
 
 
 ## Simple Spicy Controller Example
@@ -206,7 +206,7 @@ input box) in the second button.
 ## Scope Inheritance Example
 
 It is common to attach Controllers at different levels of the DOM hierarchy.  Since the 
-{@link api/ng.directive:ngController ng-controller} directive creates a new child scope, we get a
+{@link ng.directive:ngController ng-controller} directive creates a new child scope, we get a
 hierarchy of scopes that inherit from each other.  The `$scope` that each Controller receives will
 have access to properties and methods defined by Controllers higher up the hierarchy.
 See [Understanding Scopes](https://github.com/angular/angular.js/wiki/Understanding-Scopes) for
@@ -267,7 +267,7 @@ examples, all of the properties could be replaced with methods that return strin
 ## Testing Controllers
 
 Although there are many ways to test a Controller, one of the best conventions, shown below,
-involves injecting the {@link api/ng.$rootScope $rootScope} and {@link api/ng.$controller $controller}:
+involves injecting the {@link ng.$rootScope $rootScope} and {@link ng.$controller $controller}:
 
 **Controller Definition:**
 ```js
diff --git a/docs/content/guide/dev_guide.e2e-testing.ngdoc b/docs/content/guide/dev_guide.e2e-testing.ngdoc
index d72cb9b3..da2dc48a 100644
--- a/docs/content/guide/dev_guide.e2e-testing.ngdoc
+++ b/docs/content/guide/dev_guide.e2e-testing.ngdoc
@@ -88,19 +88,19 @@ Returns the window.location.search of the currently loaded page in the test fram
 Returns the window.location.hash (without `#`) of the currently loaded page in the test frame.
 
 ## browser().location().url()
-Returns the {@link api/ng.$location $location.url()} of the currently loaded page in
+Returns the {@link ng.$location $location.url()} of the currently loaded page in
 the test frame.
 
 ## browser().location().path()
-Returns the {@link api/ng.$location $location.path()} of the currently loaded page in
+Returns the {@link ng.$location $location.path()} of the currently loaded page in
 the test frame.
 
 ## browser().location().search()
-Returns the {@link api/ng.$location $location.search()} of the currently loaded page
+Returns the {@link ng.$location $location.search()} of the currently loaded page
 in the test frame.
 
 ## browser().location().hash()
-Returns the {@link api/ng.$location $location.hash()} of the currently loaded page in
+Returns the {@link ng.$location $location.hash()} of the currently loaded page in
 the test frame.
 
 ## expect(future).{matcher}
diff --git a/docs/content/guide/dev_guide.services.$location.ngdoc b/docs/content/guide/dev_guide.services.$location.ngdoc
index 8f7a596a..57739f9f 100644
--- a/docs/content/guide/dev_guide.services.$location.ngdoc
+++ b/docs/content/guide/dev_guide.services.$location.ngdoc
@@ -87,7 +87,7 @@ setter methods that allow you to get or change the current URL in the browser.
 ## $location service configuration
 
 To configure the `$location` service, retrieve the
-{@link api/ng.$locationProvider $locationProvider} and set the parameters as follows:
+{@link ng.$locationProvider $locationProvider} and set the parameters as follows:
 
 
 - **html5Mode(mode)**: {boolean}<br />
@@ -138,7 +138,7 @@ current URL without creating a new browser history record you can call:
 ```
 
 Note that the setters don't update `window.location` immediately. Instead, the `$location` service is
-aware of the {@link api/ng.$rootScope.Scope scope} life-cycle and coalesces multiple `$location`
+aware of the {@link ng.$rootScope.Scope scope} life-cycle and coalesces multiple `$location`
 mutations into one "commit" to the `window.location` object during the scope `$digest` phase. Since
 multiple changes to the $location's state will be pushed to the browser as a single change, it's
 enough to call the `replace()` method just once to make the entire "commit" a replace operation
@@ -509,11 +509,11 @@ In this examples we use `<base href="/base/index.html" />`
 
 The `$location` service allows you to change only the URL; it does not allow you to reload the
 page. When you need to change the URL and reload the page or navigate to a different page, please
-use a lower level API, {@link api/ng.$window $window.location.href}.
+use a lower level API, {@link ng.$window $window.location.href}.
 
 ## Using $location outside of the scope life-cycle
 
-`$location` knows about Angular's {@link api/ng.$rootScope.Scope scope} life-cycle. When a URL changes in
+`$location` knows about Angular's {@link ng.$rootScope.Scope scope} life-cycle. When a URL changes in
 the browser it updates the `$location` and calls `$apply` so that all $watchers / $observers are
 notified.
 When you change the `$location` inside the `$digest` phase everything is ok; `$location` will
@@ -635,7 +635,7 @@ then uses the information it obtains to compose hashbang URLs (such as
 ## Two-way binding to $location
 
 The Angular's compiler currently does not support two-way binding for methods (see [issue](https://github.com/angular/angular.js/issues/404)).  If you should require two-way binding
-to the $location object (using {@link api/ng.directive:input.text
+to the $location object (using {@link ng.directive:input.text
 ngModel} directive on an input field), you will need to specify an extra model property
 (e.g. `locationPath`) with two watchers which push $location updates in both directions. For
 example:
@@ -661,7 +661,7 @@ function LocationController($scope, $location) {
 
 # Related API
 
-* {@link api/ng.$location $location API}
+* {@link ng.$location $location API}
 
 
 
diff --git a/docs/content/guide/dev_guide.services.creating_services.ngdoc b/docs/content/guide/dev_guide.services.creating_services.ngdoc
index c6210cc1..cdcd280b 100644
--- a/docs/content/guide/dev_guide.services.creating_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.creating_services.ngdoc
@@ -4,8 +4,8 @@
 
 While Angular offers several useful services, for any nontrivial application you'll find it useful
 to write your own custom services. To do this you begin by registering a service factory function
-with a module either via the {@link api/angular.module Module#factory api} or directly
-via the {@link api/AUTO.$provide $provide} api inside of module config function.
+with a module either via the {@link angular.module Module#factory api} or directly
+via the {@link auto.$provide $provide} api inside of module config function.
 
 All Angular services participate in {@link di dependency injection (DI)} by registering
 themselves with Angular's DI system (injector) under a `name` (id) as well as by declaring
@@ -17,8 +17,8 @@ testable.
 # Registering Services
 
 To register a service, you must have a module that this service will be part of. Afterwards, you
-can register the service with the module either via the {@link api/angular.Module Module api} or
-by using the {@link api/AUTO.$provide $provide} service in the module configuration
+can register the service with the module either via the {@link angular.Module Module api} or
+by using the {@link auto.$provide $provide} service in the module configuration
 function. The following pseudo-code shows both approaches:
 
 Using the angular.Module api:
@@ -103,4 +103,4 @@ important.
 
 ## Related API
 
-* {@link api/ng Angular Service API}
+* {@link ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc b/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
index 312342b8..3bbbe6b1 100644
--- a/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
+++ b/docs/content/guide/dev_guide.services.injecting_controllers.ngdoc
@@ -118,4 +118,4 @@ dependencies with the `$inject` property.
 
 ## Related API
 
-{@link api/ng Angular Service API}
+{@link ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc b/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
index 726a8bbe..8803eb0d 100644
--- a/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
+++ b/docs/content/guide/dev_guide.services.managing_dependencies.ngdoc
@@ -87,10 +87,10 @@ of which depend on other services that are provided by the Angular framework:
 
 Things to notice in this example:
 
-* The `batchLog` service depends on the built-in {@link api/ng.$interval $interval} and
-{@link api/ng.$log $log} services, and allows messages to be logged into the
+* The `batchLog` service depends on the built-in {@link ng.$interval $interval} and
+{@link ng.$log $log} services, and allows messages to be logged into the
 `console.log` in batches.
-* The `routeTemplateMonitor` service depends on the built-in {@link api/ngRoute.$route
+* The `routeTemplateMonitor` service depends on the built-in {@link ngRoute.$route
 $route} service as well as our custom `batchLog` service.
 * Both of our services use the factory function signature and array notation for inject annotations
 to declare their dependencies. It is important that the order of the string identifiers in the array
@@ -109,5 +109,5 @@ that the injector uses to determine which services and in which order to inject.
 
 ## Related API
 
-* {@link api/ng Angular Service API}
-* {@link api/angular.injector Angular Injector API}
+* {@link ./ng Angular Service API}
+* {@link angular.injector Angular Injector API}
diff --git a/docs/content/guide/dev_guide.services.ngdoc b/docs/content/guide/dev_guide.services.ngdoc
index 725e01e3..cb950b96 100644
--- a/docs/content/guide/dev_guide.services.ngdoc
+++ b/docs/content/guide/dev_guide.services.ngdoc
@@ -17,4 +17,4 @@ objects that are wired together using {@link di dependency injection (DI)}.
 
 ## Related API
 
-* {@link api/ng Angular Service API}
+* {@link ./ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.testing_services.ngdoc b/docs/content/guide/dev_guide.services.testing_services.ngdoc
index 49f10c5a..e79a483a 100644
--- a/docs/content/guide/dev_guide.services.testing_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.testing_services.ngdoc
@@ -59,4 +59,4 @@ it('should clear messages after alert', function() {
 
 ## Related API
 
-* {@link api/ng Angular Service API}
+* {@link ./ng Angular Service API}
diff --git a/docs/content/guide/dev_guide.services.understanding_services.ngdoc b/docs/content/guide/dev_guide.services.understanding_services.ngdoc
index bb02f541..8ebbed63 100644
--- a/docs/content/guide/dev_guide.services.understanding_services.ngdoc
+++ b/docs/content/guide/dev_guide.services.understanding_services.ngdoc
@@ -5,7 +5,7 @@
 ## What are Angular Services?
 
 Angular services are singletons objects or functions that carry out specific tasks common to web apps.
-Angular has a number of built in services, such as the {@link api/ng.$http $http service}, which
+Angular has a number of built in services, such as the {@link ng.$http $http service}, which
 provides access to the browser's `XMLHttpRequest` object for making requests to a server. Like other core
 Angular variables and identifiers, the built-in services always start with `$` (such as `$http` mentioned
 above). You can also create your own custom services.
@@ -49,12 +49,12 @@ dependent on this service gets a reference to the single instance generated by t
 
 ## Related Topics
 
-* {@link di About Angular Dependency Injection}
-* {@link dev_guide.services.creating_services Creating Angular Services}
-* {@link dev_guide.services.managing_dependencies Managing Service Dependencies}
-* {@link dev_guide.services.testing_services Testing Angular Services}
+* {@link guide/di About Angular Dependency Injection}
+* {@link guide/dev_guide.services.creating_services Creating Angular Services}
+* {@link guide/dev_guide.services.managing_dependencies Managing Service Dependencies}
+* {@link guide/dev_guide.services.testing_services Testing Angular Services}
 
 ## Related API
 
-* {@link api/ng Angular Service API}
-* {@link api/angular.injector Injector API}
+* {@link ./ng Angular Service API}
+* {@link angular.injector Injector API}
diff --git a/docs/content/guide/dev_guide.templates.css-styling.ngdoc b/docs/content/guide/dev_guide.templates.css-styling.ngdoc
index c00aa9f7..3d156790 100644
--- a/docs/content/guide/dev_guide.templates.css-styling.ngdoc
+++ b/docs/content/guide/dev_guide.templates.css-styling.ngdoc
@@ -8,7 +8,7 @@ Angular sets these CSS classes. It is up to your application to provide useful s
 # CSS classes used by angular
 
 * `ng-scope`
-  - **Usage:** angular applies this class to any element that where a new {@link api/ng.$rootScope.Scope scope}
+  - **Usage:** angular applies this class to any element that where a new {@link ng.$rootScope.Scope scope}
     is defined. (see {@link guide/scope scope} guide for more information about scopes)
 
 * `ng-binding`
@@ -17,15 +17,15 @@ Angular sets these CSS classes. It is up to your application to provide useful s
 
 * `ng-invalid`, `ng-valid`
   - **Usage:** angular applies this class to an input widget element if that element's input does
-    not pass validation. (see {@link api/ng.directive:input input} directive)
+    not pass validation. (see {@link ng.directive:input input} directive)
 
 * `ng-pristine`, `ng-dirty`
-  - **Usage:** angular {@link api/ng.directive:input input} directive applies `ng-pristine` class
+  - **Usage:** angular {@link ng.directive:input input} directive applies `ng-pristine` class
     to a new input widget element which did not have user interaction. Once the user interacts with
     the input widget the class is changed to `ng-dirty`.
 
 
 ## Related Topics
 
-* {@link templates Angular Templates}
-* {@link forms Angular Forms}
+* {@link guide/templates Angular Templates}
+* {@link guide/forms Angular Forms}
diff --git a/docs/content/guide/dev_guide.unit-testing.ngdoc b/docs/content/guide/dev_guide.unit-testing.ngdoc
index 28779182..6be877e6 100644
--- a/docs/content/guide/dev_guide.unit-testing.ngdoc
+++ b/docs/content/guide/dev_guide.unit-testing.ngdoc
@@ -261,7 +261,7 @@ Notice that the test is not only much shorter, it is also easier to follow what
 that such a test tells a story, rather then asserting random bits which don't seem to be related.
 
 ## Filters
-{@link api/ng.$filterProvider Filters} are functions which transform the data into a user readable
+{@link ng.$filterProvider Filters} are functions which transform the data into a user readable
 format. They are important because they remove the formatting responsibility from the application
 logic, further simplifying the application logic.
 
diff --git a/docs/content/guide/directive.ngdoc b/docs/content/guide/directive.ngdoc
index 39ada01d..95aae48f 100644
--- a/docs/content/guide/directive.ngdoc
+++ b/docs/content/guide/directive.ngdoc
@@ -7,7 +7,7 @@
 <div class="alert alert-warning">
 **Note:** this guide is targeted towards developers who are already familiar with AngularJS basics.
 If you're just getting started, we recommend the {@link tutorial/ tutorial} first.
-If you're looking for the **directives API**, we recently moved it to {@link api/ng.$compile `$compile`}.
+If you're looking for the **directives API**, we recently moved it to {@link ng.$compile `$compile`}.
 </div>
 
 
@@ -18,7 +18,7 @@ how to implement them.
 ## What are Directives?
 
 At a high level, directives are markers on a DOM element (such as an attribute, element
-name, or CSS class) that tell AngularJS's **HTML compiler** ({@link api/ng.$compile `$compile`}) to
+name, or CSS class) that tell AngularJS's **HTML compiler** ({@link ng.$compile `$compile`}) to
 attach a specified behavior to that DOM element or even transform the DOM element and its children.
 
 Angular comes with a set of these directives built-in, like `ngBind`, `ngModel`, and `ngView`.
@@ -120,7 +120,7 @@ Doing so generally makes it easier to determine what directives a given element
 <div class="alert alert-success">
 **Best Practice:** Comment directives were commonly used in places where the DOM API limits the
 ability to create directives that spanned multiple elements (e.g. inside `<table>` elements).
-AngularJS 1.2 introduces {@link api/ng.directive:ngRepeat `ng-repeat-start` and `ng-repeat-end`}
+AngularJS 1.2 introduces {@link ng.directive:ngRepeat `ng-repeat-start` and `ng-repeat-end`}
 as a better solution to this problem. Developers are encouraged to use this over custom comment
 directives when possible.
 </div>
@@ -129,10 +129,10 @@ directives when possible.
 
 ### Text and attribute bindings
 
-During the compilation process the {@link api/ng.$compile compiler} matches text and attributes
-using the {@link api/ng.$interpolate $interpolate} service to see if they contain embedded
-expressions. These expressions are registered as {@link api/ng.$rootScope.Scope#methods_$watch watches}
-and will update as part of normal {@link api/ng.$rootScope.Scope#methods_$digest digest} cycle. An
+During the compilation process the {@link ng.$compile compiler} matches text and attributes
+using the {@link ng.$interpolate $interpolate} service to see if they contain embedded
+expressions. These expressions are registered as {@link ng.$rootScope.Scope#methods_$watch watches}
+and will update as part of normal {@link ng.$rootScope.Scope#methods_$digest digest} cycle. An
 example of interpolation is shown below:
 
 ```html
@@ -174,7 +174,7 @@ For example, we could fix the example above by instead writing:
 
 ## Creating Directives
 
-First let's talk about the {@link api/ng.$compileProvider#methods_directive API for registering directives}. Much like
+First let's talk about the {@link ng.$compileProvider#methods_directive API for registering directives}. Much like
 controllers, directives are registered on modules. To register a directive, you use the
 `module.directive` API. `module.directive` takes the
 {@link guide/directive#creating-custom-directives_matching-directives normalized} directive name
@@ -183,9 +183,9 @@ options to tell `$compile` how the directive should behave when matched.
 
 
 The factory function is invoked only once when the
-{@link api/ng.$compile compiler} matches the directive for the first time. You can perform any
+{@link ng.$compile compiler} matches the directive for the first time. You can perform any
 initialization work here. The function is invoked using
-{@link api/AUTO.$injector#methods_invoke $injector.invoke} which makes it injectable just like a
+{@link auto.$injector#methods_invoke $injector.invoke} which makes it injectable just like a
 controller.
 
 <div class="alert alert-success">
@@ -324,9 +324,9 @@ Let's change our directive to use `restrict: 'E'`:
 </example>
 
 For more on the
-{@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object `restrict`}
+{@link ng.$compile#description_comprehensive-directive-api_directive-definition-object `restrict`}
 property, see the
-{@link api/ng.$compile#description_comprehensive-directive-api_directive-definition-object API docs}.
+{@link ng.$compile#description_comprehensive-directive-api_directive-definition-object API docs}.
 
 <div class="alert alert-info">
 **When should I use an attribute versus an element?**
@@ -912,6 +912,6 @@ point for creating your own directives.
 You might also be interested in an in-depth explanation of the compilation process that's
 available in the {@link guide/compiler compiler guide}.
 
-The {@link api/ng.$compile `$compile` API} page has a comprehensive list of directive options for
+The {@link ng.$compile `$compile` API} page has a comprehensive list of directive options for
 reference.
 
diff --git a/docs/content/guide/expression.ngdoc b/docs/content/guide/expression.ngdoc
index 99cc7514..583fa5fd 100644
--- a/docs/content/guide/expression.ngdoc
+++ b/docs/content/guide/expression.ngdoc
@@ -3,7 +3,7 @@
 @description
 
 Expressions are JavaScript-like code snippets that are usually placed in bindings such as `{{
-expression }}`. Expressions are processed by the {@link api/ng.$parse $parse}
+expression }}`. Expressions are processed by the {@link ng.$parse $parse}
 service. Expressions are often post processed using {@link filter filters} to create a more user-friendly format.
 
 For example, these are all valid expressions in angular:
@@ -30,7 +30,7 @@ You can think of Angular expressions as JavaScript expressions with following di
 
 If, on the other hand, you do want to run arbitrary JavaScript code, you should make it a
 controller method and call the method. If you want to `eval()` an angular expression from
-JavaScript, use the {@link api/ng.$rootScope.Scope#methods_$eval `$eval()`} method.
+JavaScript, use the {@link ng.$rootScope.Scope#methods_$eval `$eval()`} method.
 
 ## Example
 <doc:example>
@@ -87,7 +87,7 @@ You can try evaluating different expressions here:
 # Property Evaluation
 
 Evaluation of all properties takes place against a scope. Unlike JavaScript, where names default
-to global window properties, Angular expressions have to use {@link api/ng.$window
+to global window properties, Angular expressions have to use {@link ng.$window
 `$window`} to refer to the global `window` object. For example, if you want to call `alert()`, which is
 defined on `window`, in an expression you must use `$window.alert()`. This is done intentionally to
 prevent accidental access to the global state (a common source of subtle bugs).
diff --git a/docs/content/guide/filter.ngdoc b/docs/content/guide/filter.ngdoc
index d156009a..4bcde01f 100644
--- a/docs/content/guide/filter.ngdoc
+++ b/docs/content/guide/filter.ngdoc
@@ -5,7 +5,7 @@
 A filter formats the value of an expression for display to the user. They can be used in view templates,
 controllers or services and it is easy to define your own filter.
 
-The underlying API is the {@link api/ng.$filterProvider filterProvider}.
+The underlying API is the {@link ng.$filterProvider filterProvider}.
 
 ## Using filters in view templates
 
@@ -13,7 +13,7 @@ Filters can be applied to expressions in view templates using the following synt
 
         {{ expression | filter }}
 
-E.g. the markup `{{ 12 | currency }}` formats the number 12 as a currency using the {@link api/ng.filter:currency `currency`}
+E.g. the markup `{{ 12 | currency }}` formats the number 12 as a currency using the {@link ng.filter:currency `currency`}
 filter. The resulting value is `$12.00`.
 
 Filters can be applied to the result of another filter. This is called "chaining" and uses
@@ -26,7 +26,7 @@ Filters may have arguments. The syntax for this is
         {{ expression | filter:argument1:argument2:... }}
 
 E.g. the markup `{{ 1234 | number:2 }}` formats the number 1234 with 2 decimal points using the
-{@link api/ng.filter:number `number`} filter. The resulting value is `1,234.00`.
+{@link ng.filter:number `number`} filter. The resulting value is `1,234.00`.
 
 
 ## Using filters in controllers and services
@@ -36,7 +36,7 @@ to your controller or service. E.g. using the dependency `numberFilter` will inj
 The injected argument is a function that takes the value to format as first argument and filter parameters
 starting with the second argument.
 
-The example below uses the filter called {@link api/ng.filter:filter `filter`}.
+The example below uses the filter called {@link ng.filter:filter `filter`}.
 This filter reduces arrays into sub arrays based on
 conditions. The filter can be applied in the view template with markup like
 `{{ctrl.array | filter:'a'}}`, which would do a fulltext search for "a".
@@ -81,7 +81,7 @@ or the filter expression is changed).
 ## Creating custom filters
 
 Writing your own filter is very easy: just register a new filter factory function with
-your module. Internally, this uses the {@link api/ng.$filterProvider `filterProvider`}.
+your module. Internally, this uses the {@link ng.$filterProvider `filterProvider`}.
 This factory function should return a new filter function which takes the input value
 as the first argument. Any filter arguments are passed in as additional arguments to the filter
 function.
diff --git a/docs/content/guide/forms.ngdoc b/docs/content/guide/forms.ngdoc
index 84ee4330..d5f59d18 100644
--- a/docs/content/guide/forms.ngdoc
+++ b/docs/content/guide/forms.ngdoc
@@ -12,9 +12,9 @@ Server-side validation is still necessary for a secure application.
 
 
 # Simple form
-The key directive in understanding two-way data-binding is {@link api/ng.directive:ngModel ngModel}.
+The key directive in understanding two-way data-binding is {@link ng.directive:ngModel ngModel}.
 The `ngModel` directive provides the two-way data-binding by synchronizing the model to the view, as well as view to the model.
-In addition it provides an {@link api/ng.directive:ngModel.NgModelController API} for other directives to augment its behavior.
+In addition it provides an {@link ng.directive:ngModel.NgModelController API} for other directives to augment its behavior.
 
 <doc:example>
 <doc:source>
@@ -113,11 +113,11 @@ This ensures that the user is not distracted with an error until after interacti
 
 # Binding to form and control state
 
-A form is an instance of {@link api/ng.directive:form.FormController FormController}.
+A form is an instance of {@link ng.directive:form.FormController FormController}.
 The form instance can optionally be published into the scope using the `name` attribute.
 
-Similarly, an input control that has the {@link api/ng.directive:ngModel ngModel} directive holds an
-instance of {@link api/ng.directive:ngModel.NgModelController NgModelController}.
+Similarly, an input control that has the {@link ng.directive:ngModel ngModel} directive holds an
+instance of {@link ng.directive:ngModel.NgModelController NgModelController}.
 Such a control instance can be published as a property of the form instance using the `name` attribute
 on the input control.  The name attribute specifies the name of the property on the form instance.
 
@@ -183,19 +183,19 @@ This allows us to extend the above example with these features:
 
 # Custom Validation
 
-Angular provides basic implementation for most common html5 {@link api/ng.directive:input input}
-types: ({@link api/ng.directive:input.text text}, {@link api/ng.directive:input.number number}, {@link api/ng.directive:input.url url}, {@link api/ng.directive:input.email email}, {@link api/ng.directive:input.radio radio}, {@link api/ng.directive:input.checkbox checkbox}), as well as some directives for validation (`required`, `pattern`, `minlength`, `maxlength`, `min`, `max`).
+Angular provides basic implementation for most common html5 {@link ng.directive:input input}
+types: ({@link ng.directive:input.text text}, {@link ng.directive:input.number number}, {@link ng.directive:input.url url}, {@link ng.directive:input.email email}, {@link ng.directive:input.radio radio}, {@link ng.directive:input.checkbox checkbox}), as well as some directives for validation (`required`, `pattern`, `minlength`, `maxlength`, `min`, `max`).
 
-Defining your own validator can be done by defining your own directive which adds a custom validation function to the `ngModel` {@link api/ng.directive:ngModel.NgModelController controller}.
+Defining your own validator can be done by defining your own directive which adds a custom validation function to the `ngModel` {@link ng.directive:ngModel.NgModelController controller}.
 To get a hold of the controller the directive specifies a dependency as shown in the example below.
 The validation can occur in two places:
 
   * **Model to View update** -
-    Whenever the bound model changes, all functions in {@link api/ng.directive:ngModel.NgModelController#properties_$formatters NgModelController#$formatters} array are pipe-lined, so that each of these functions has an opportunity to format the value and change validity state of the form control through {@link api/ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.
+    Whenever the bound model changes, all functions in {@link ng.directive:ngModel.NgModelController#properties_$formatters NgModelController#$formatters} array are pipe-lined, so that each of these functions has an opportunity to format the value and change validity state of the form control through {@link ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.
 
   * **View to Model update** -
-    In a similar way, whenever a user interacts with a control it calls {@link api/ng.directive:ngModel.NgModelController#methods_$setViewValue NgModelController#$setViewValue}.
-This in turn pipelines all functions in the {@link api/ng.directive:ngModel.NgModelController#properties_$parsers NgModelController#$parsers} array, so that each of these functions has an opportunity to convert the value and change validity state of the form control through {@link api/ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.
+    In a similar way, whenever a user interacts with a control it calls {@link ng.directive:ngModel.NgModelController#methods_$setViewValue NgModelController#$setViewValue}.
+This in turn pipelines all functions in the {@link ng.directive:ngModel.NgModelController#properties_$parsers NgModelController#$parsers} array, so that each of these functions has an opportunity to convert the value and change validity state of the form control through {@link ng.directive:ngModel.NgModelController#methods_$setValidity NgModelController#$setValidity}.
 
 In the following example we create two directives.
 
@@ -278,7 +278,7 @@ In the following example we create two directives.
 
 
 # Implementing custom form controls (using `ngModel`)
-Angular implements all of the basic HTML form controls ({@link api/ng.directive:input input}, {@link api/ng.directive:select select}, {@link api/ng.directive:textarea textarea}), which should be sufficient for most cases.
+Angular implements all of the basic HTML form controls ({@link ng.directive:input input}, {@link ng.directive:select select}, {@link ng.directive:textarea textarea}), which should be sufficient for most cases.
 However, if you need more flexibility, you can write your own form control as a directive.
 
 In order for custom control to work with `ngModel` and to achieve two-way data-binding it needs to:
diff --git a/docs/content/guide/i18n.ngdoc b/docs/content/guide/i18n.ngdoc
index 159958f8..9be65c0a 100644
--- a/docs/content/guide/i18n.ngdoc
+++ b/docs/content/guide/i18n.ngdoc
@@ -91,7 +91,7 @@ because an extra script needs to be loaded.
 **Currency symbol "gotcha"**
 
 Angular's [currency filter](http://docs.angularjs.org/#!/api/ng.filter:currency) allows
-you to use the default currency symbol from the {@link api/ng.$locale locale service},
+you to use the default currency symbol from the {@link ng.$locale locale service},
 or you can provide the filter with a custom currency symbol. If your app will be used only in one
 locale, it is fine to rely on the default currency symbol. However, if you anticipate that viewers
 in other locales might use your app, you should provide your own currency symbol to make sure the
diff --git a/docs/content/guide/index.ngdoc b/docs/content/guide/index.ngdoc
index a851e5b6..d975cd0e 100644
--- a/docs/content/guide/index.ngdoc
+++ b/docs/content/guide/index.ngdoc
@@ -27,7 +27,7 @@ In Angular applications, you move the job of filling page templates with data fr
 * {@link guide/databinding Data binding}
 * {@link guide/expression Expressions}
 * {@link guide/directive Directives}
-* {@link api/ngRoute.$route Views and routes (see the example)}
+* {@link ngRoute.$route Views and routes (see the example)}
 * {@link guide/filter Filters}
 * {@link guide/forms Forms} and [Concepts of AngularJS Forms](http://mrbool.com/the-concepts-of-angularjs-forms/29117)
 
@@ -36,14 +36,14 @@ In Angular applications, you move the job of filling page templates with data fr
 * **Blog post: **[When to use directives, controllers or services](http://kirkbushell.me/when-to-use-directives-controllers-or-services-in-angular/)
 * **App wiring:** {@link guide/di Dependency injection}
 * **Exposing model to templates:** {@link guide/scope Scopes}
-* **Communicating with servers:** {@link api/ng.$http $http}, {@link api/ngResource.$resource $resource}
+* **Communicating with servers:** {@link ng.$http $http}, {@link ngResource.$resource $resource}
 
 ### Other AngularJS Features
 
-* **Animation:** {@link guide/animations Core concepts}, {@link api/ngAnimate ngAnimate API}, and [Animation in AngularJS 1.2](http://www.yearofmoo.com/2013/08/remastered-animation-in-angularjs-1-2.html)
-* **Security:** {@link api/ng.$sce Strict Contextual Escaping}, {@link api/ng.directive:ngCsp Content Security Policy}, {@link api/ngSanitize.$sanitize $sanitize}, [video](https://www.youtube.com/watch?v=18ifoT-Id54)
-* **Internationalization and Localization:** {@link guide/i18n Angular Guide to i18n and l10n}, {@link api/ng.filter:date date filter}, {@link api/ng.filter:currency currency filter}, [Creating multilingual support](http://www.novanet.no/blog/hallstein-brotan/dates/2013/10/creating-multilingual-support-using-angularjs/)
-* **Mobile:** {@link api/ngTouch Touch events}
+* **Animation:** {@link guide/animations Core concepts}, {@link ngAnimate ngAnimate API}, and [Animation in AngularJS 1.2](http://www.yearofmoo.com/2013/08/remastered-animation-in-angularjs-1-2.html)
+* **Security:** {@link ng.$sce Strict Contextual Escaping}, {@link ng.directive:ngCsp Content Security Policy}, {@link ngSanitize.$sanitize $sanitize}, [video](https://www.youtube.com/watch?v=18ifoT-Id54)
+* **Internationalization and Localization:** {@link guide/i18n Angular Guide to i18n and l10n}, {@link ng.filter:date date filter}, {@link ng.filter:currency currency filter}, [Creating multilingual support](http://www.novanet.no/blog/hallstein-brotan/dates/2013/10/creating-multilingual-support-using-angularjs/)
+* **Mobile:** {@link ngTouch Touch events}
 
 ### Testing
 
diff --git a/docs/content/guide/migration.ngdoc b/docs/content/guide/migration.ngdoc
index 92e61f67..2a16c9c7 100644
--- a/docs/content/guide/migration.ngdoc
+++ b/docs/content/guide/migration.ngdoc
@@ -361,7 +361,7 @@ See [05772e15](https://github.com/angular/angular.js/commit/05772e15fbecfdc63d49
 
 ## $location.search supports multiple keys
 
-{@link api/ng.$location#methods_search `$location.search`} now supports multiple keys with the
+{@link ng.$location#methods_search `$location.search`} now supports multiple keys with the
 same value provided that the values are stored in an array.
 
 Before this change:
diff --git a/docs/content/guide/module.ngdoc b/docs/content/guide/module.ngdoc
index 417d3837..17cadb77 100644
--- a/docs/content/guide/module.ngdoc
+++ b/docs/content/guide/module.ngdoc
@@ -22,7 +22,7 @@ Ok, I'm in a hurry. How do I get a Hello World module working?
 
 Important things to notice:
 
-  * {@link api/angular.Module Module} API
+  * {@link angular.Module Module} API
   * Notice the reference to the `myApp` module in the `<html ng-app="myApp">`, it is what
     bootstraps the app using your module.
 
diff --git a/docs/content/guide/providers.ngdoc b/docs/content/guide/providers.ngdoc
index f0d33b51..84136563 100644
--- a/docs/content/guide/providers.ngdoc
+++ b/docs/content/guide/providers.ngdoc
@@ -6,7 +6,7 @@
 
 Each web application you build is composed of objects that collaborate to get stuff done. These
 objects need to be instantiated and wired together for the app to work. In Angular apps most of
-these objects are instantiated and wired together automatically by the {@link api/AUTO.$injector
+these objects are instantiated and wired together automatically by the {@link auto.$injector
 injector service}.
 
 The injector creates two types of objects, **services** and **specialized objects**.
@@ -34,7 +34,7 @@ In order for the injector to know how to create and wire together all of these o
 a registry of "recipes". Each recipe has an identifier of the object and the description of how to
 create this object.
 
-Each recipe belongs to an {@link api/angular.Module Angular module}. An Angular module is a bag
+Each recipe belongs to an {@link angular.Module Angular module}. An Angular module is a bag
 that holds one or more recipes. And since manually keeping track of module dependencies is no fun,
 a module can contain information about dependencies on other modules as well.
 
diff --git a/docs/content/guide/scope.ngdoc b/docs/content/guide/scope.ngdoc
index da194977..f13350fa 100644
--- a/docs/content/guide/scope.ngdoc
+++ b/docs/content/guide/scope.ngdoc
@@ -4,17 +4,17 @@
 
 # What are Scopes?
 
-{@link api/ng.$rootScope.Scope scope} is an object that refers to the application
+{@link ng.$rootScope.Scope scope} is an object that refers to the application
 model. It is an execution context for {@link expression expressions}. Scopes are
 arranged in hierarchical structure which mimic the DOM structure of the application. Scopes can
 watch {@link guide/expression expressions} and propagate events.
 
 ## Scope characteristics
 
-  - Scopes provide APIs ({@link api/ng.$rootScope.Scope#methods_$watch $watch}) to observe
+  - Scopes provide APIs ({@link ng.$rootScope.Scope#methods_$watch $watch}) to observe
     model mutations.
 
-  - Scopes provide APIs ({@link api/ng.$rootScope.Scope#methods_$apply $apply}) to
+  - Scopes provide APIs ({@link ng.$rootScope.Scope#methods_$apply $apply}) to
     propagate any model changes through the system into the view from outside of the "Angular
     realm" (controllers, services, Angular event handlers).
 
@@ -32,8 +32,8 @@ watch {@link guide/expression expressions} and propagate events.
 ## Scope as Data-Model
 
 Scope is the glue between application controller and the view. During the template {@link compiler
-linking} phase the {@link api/ng.$compileProvider#methods_directive directives} set up
-{@link api/ng.$rootScope.Scope#methods_$watch `$watch`} expressions on the scope. The
+linking} phase the {@link ng.$compileProvider#methods_directive directives} set up
+{@link ng.$rootScope.Scope#methods_$watch `$watch`} expressions on the scope. The
 `$watch` allows the directives to be notified of property changes, which allows the directive to
 render the updated value to the DOM.
 
@@ -106,7 +106,7 @@ to test the behavior without being distracted by the rendering details.
 
 ## Scope Hierarchies
 
-Each Angular application has exactly one {@link api/ng.$rootScope root scope}, but
+Each Angular application has exactly one {@link ng.$rootScope root scope}, but
 may have several child scopes.
 
 The application can have multiple scopes, because some {@link guide/directive directives} create
@@ -169,7 +169,7 @@ where the `department` property is defined.
 Scopes are attached to the DOM as `$scope` data property, and can be retrieved for debugging
 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
+of {@link ng.directive:ngApp `ng-app`} directive. Typically
 `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.
 
@@ -248,8 +248,8 @@ the `$digest` phase. This delay is desirable, since it coalesces multiple model
 
   1. **Creation**
 
-     The {@link api/ng.$rootScope root scope} is created during the application
-     bootstrap by the {@link api/AUTO.$injector $injector}. During template
+     The {@link ng.$rootScope root scope} is created during the application
+     bootstrap by the {@link auto.$injector $injector}. During template
      linking, some directives create new child scopes.
 
   2. **Watcher registration**
@@ -263,12 +263,12 @@ the `$digest` phase. This delay is desirable, since it coalesces multiple model
      For mutations to be properly observed, you should make them only within the {@link
      api/ng.$rootScope.Scope#methods_$apply scope.$apply()}. (Angular APIs do this
      implicitly, so no extra `$apply` call is needed when doing synchronous work in controllers,
-     or asynchronous work with {@link api/ng.$http $http}, {@link api/ng.$timeout $timeout}
-     or {@link api/ng.$interval $interval} services.
+     or asynchronous work with {@link ng.$http $http}, {@link ng.$timeout $timeout}
+     or {@link ng.$interval $interval} services.
 
   4. **Mutation observation**
 
-     At the end `$apply`, Angular performs a {@link api/ng.$rootScope.Scope#methods_$digest
+     At the end `$apply`, Angular performs a {@link ng.$rootScope.Scope#methods_$digest
      $digest} cycle on the root scope, which then propagates throughout all child scopes. During
      the `$digest` cycle, all `$watch`ed expressions or functions are checked for model mutation
      and if a mutation is detected, the `$watch` listener is called.
@@ -276,7 +276,7 @@ the `$digest` phase. This delay is desirable, since it coalesces multiple model
   5. **Scope destruction**
 
      When child scopes are no longer needed, it is the responsibility of the child scope creator
-     to destroy them via {@link api/ng.$rootScope.Scope#methods_$destroy scope.$destroy()}
+     to destroy them via {@link ng.$rootScope.Scope#methods_$destroy scope.$destroy()}
      API. This will stop propagation of `$digest` calls into the child scope and allow for memory
      used by the child scope models to be reclaimed by the garbage collector.
 
@@ -287,12 +287,12 @@ During the compilation phase, the {@link compiler compiler} matches {@link
 api/ng.$compileProvider#methods_directive directives} against the DOM template. The directives
 usually fall into one of two categories:
 
-  - Observing {@link api/ng.$compileProvider#methods_directive directives}, such as
+  - Observing {@link ng.$compileProvider#methods_directive directives}, such as
     double-curly expressions `{{expression}}`, register listeners using the {@link
     api/ng.$rootScope.Scope#methods_$watch $watch()} method. This type of directive needs
     to be notified whenever the expression changes so that it can update the view.
 
-  - Listener directives, such as {@link api/ng.directive:ngClick
+  - Listener directives, such as {@link ng.directive:ngClick
     ng-click}, register a listener with the DOM. When the DOM listener fires, the directive
     executes the associated expression and updates the view using the {@link
     api/ng.$rootScope.Scope#methods_$apply $apply()} method.
@@ -304,7 +304,7 @@ correctly.
 
 ### Directives that Create Scopes
 
-In most cases, {@link api/ng.$compileProvider#methods_directive directives} and scopes interact
+In most cases, {@link ng.$compileProvider#methods_directive directives} and scopes interact
 but do not create new instances of scope. However, some directives, such as {@link
 api/ng.directive:ngController ng-controller} and {@link
 api/ng.directive:ngRepeat ng-repeat}, create new child scopes
@@ -322,10 +322,10 @@ Scopes and controllers interact with each other in the following situations:
 
    - Controllers define methods (behavior) that can mutate the model (properties on the scope).
 
-   - Controllers may register {@link api/ng.$rootScope.Scope#methods_$watch watches} on
+   - Controllers may register {@link ng.$rootScope.Scope#methods_$watch watches} on
      the model. These watches execute immediately after the controller behavior executes.
 
-See the {@link api/ng.directive:ngController ng-controller} for more
+See the {@link ng.directive:ngController ng-controller} for more
 information.
 
 
@@ -360,23 +360,23 @@ implementing custom event callbacks, or when working with third-party library ca
      api/ng.$rootScope.Scope#methods_$apply $apply}`(stimulusFn)`. Where `stimulusFn` is
      the work you wish to do in Angular execution context.
   2. Angular executes the `stimulusFn()`, which typically modifies application state.
-  3. Angular enters the {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop. The
+  3. Angular enters the {@link ng.$rootScope.Scope#methods_$digest $digest} loop. The
      loop is made up of two smaller loops which process {@link
      api/ng.$rootScope.Scope#methods_$evalAsync $evalAsync} queue and the {@link
      api/ng.$rootScope.Scope#methods_$watch $watch} list. The {@link
      api/ng.$rootScope.Scope#methods_$digest $digest} loop keeps iterating until the model
-     stabilizes, which means that the {@link api/ng.$rootScope.Scope#methods_$evalAsync
-     $evalAsync} queue is empty and the {@link api/ng.$rootScope.Scope#methods_$watch
+     stabilizes, which means that the {@link ng.$rootScope.Scope#methods_$evalAsync
+     $evalAsync} queue is empty and the {@link ng.$rootScope.Scope#methods_$watch
      $watch} list does not detect any changes.
-  4. The {@link api/ng.$rootScope.Scope#methods_$evalAsync $evalAsync} queue is used to
+  4. The {@link ng.$rootScope.Scope#methods_$evalAsync $evalAsync} queue is used to
      schedule work which needs to occur outside of current stack frame, but before the browser's
      view render. This is usually done with `setTimeout(0)`, but the `setTimeout(0)` approach
      suffers from slowness and may cause view flickering since the browser renders the view after
      each event.
-  5. The {@link api/ng.$rootScope.Scope#methods_$watch $watch} list is a set of expressions
+  5. The {@link ng.$rootScope.Scope#methods_$watch $watch} list is a set of expressions
      which may have changed since last iteration. If a change is detected then the `$watch`
      function is called which typically updates the DOM with the new value.
-  6. Once the Angular {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop finishes
+  6. Once the Angular {@link ng.$rootScope.Scope#methods_$digest $digest} loop finishes
      the execution leaves the Angular and JavaScript context. This is followed by the browser
      re-rendering the DOM to reflect any changes.
 
@@ -385,22 +385,22 @@ Here is the explanation of how the `Hello world` example achieves the data-bindi
 user enters text into the text field.
 
   1. During the compilation phase:
-     1. the {@link api/ng.directive:ngModel ng-model} and {@link
+     1. the {@link ng.directive:ngModel ng-model} and {@link
         api/ng.directive:input input} {@link guide/directive
         directive} set up a `keydown` listener on the `<input>` control.
-     2. the {@link api/ng.$interpolate &#123;&#123;name&#125;&#125; } interpolation
-        sets up a {@link api/ng.$rootScope.Scope#methods_$watch $watch} to be notified of
+     2. the {@link ng.$interpolate &#123;&#123;name&#125;&#125; } interpolation
+        sets up a {@link ng.$rootScope.Scope#methods_$watch $watch} to be notified of
         `name` changes.
   2. During the runtime phase:
      1. Pressing an '`X`' key causes the browser to emit a `keydown` event on the input control.
-     2. The {@link api/ng.directive:input input} directive
+     2. The {@link ng.directive:input input} directive
         captures the change to the input's value and calls {@link
         api/ng.$rootScope.Scope#methods_$apply $apply}`("name = 'X';")` to update the
         application model inside the Angular execution context.
      3. Angular applies the `name = 'X';` to the model.
-     4. The {@link api/ng.$rootScope.Scope#methods_$digest $digest} loop begins
-     5. The {@link api/ng.$rootScope.Scope#methods_$watch $watch} list detects a change
-        on the `name` property and notifies the {@link api/ng.$interpolate
+     4. The {@link ng.$rootScope.Scope#methods_$digest $digest} loop begins
+     5. The {@link ng.$rootScope.Scope#methods_$watch $watch} list detects a change
+        on the `name` property and notifies the {@link ng.$interpolate
         &#123;&#123;name&#125;&#125; } interpolation, which in turn updates the DOM.
      6. Angular exits the execution context, which in turn exits the `keydown` event and with it
         the JavaScript execution context.
diff --git a/docs/content/guide/templates.ngdoc b/docs/content/guide/templates.ngdoc
index fdd90b74..bd8bfd89 100644
--- a/docs/content/guide/templates.ngdoc
+++ b/docs/content/guide/templates.ngdoc
@@ -12,7 +12,7 @@ These are the types of Angular elements and element attributes you can use in a
 
 * {@link guide/directive Directive} — An attribute or element that
   augments an existing DOM element or represents a reusable DOM component - a widget.
-* {@link api/ng.$interpolate Markup} — The double
+* {@link ng.$interpolate Markup} — The double
 curly brace notation `{{ }}` to bind expressions to elements is built-in angular markup.
 * {@link filter Filter} — Formats your data for display to the user.
 * {@link forms Form controls} — Lets you validate user input.
@@ -41,8 +41,8 @@ with {@link expression expressions}:
 In a simple single-page app, the template consists of HTML, CSS, and angular directives contained
 in just one HTML file (usually `index.html`). In a more complex app, you can display multiple views
 within one main page using "partials", which are segments of template located in separate HTML
-files.  You "include" the partials in the main page using the {@link api/ngRoute.$route
-$route} service in conjunction with the {@link api/ngRoute.directive:ngView ngView} directive. An
+files.  You "include" the partials in the main page using the {@link ngRoute.$route
+$route} service in conjunction with the {@link ngRoute.directive:ngView ngView} directive. An
 example of this technique is shown in the {@link tutorial/ angular tutorial}, in steps seven and
 eight.
 
@@ -54,4 +54,4 @@ eight.
 
 ## Related API
 
-* {@link api/index API Reference}
+* {@link ./api API Reference}
diff --git a/docs/content/misc/faq.ngdoc b/docs/content/misc/faq.ngdoc
index 18beca12..e416055e 100644
--- a/docs/content/misc/faq.ngdoc
+++ b/docs/content/misc/faq.ngdoc
@@ -79,7 +79,7 @@ in Angular.
 
 Yes, Angular can use [jQuery](http://jquery.com/) if it's present in your app when the
 application is being bootstrapped. If jQuery is not present in your script path, Angular falls back
-to its own implementation of the subset of jQuery that we call {@link api/angular.element  jQLite}.
+to its own implementation of the subset of jQuery that we call {@link angular.element  jQLite}.
 
 Due to a change to use `on()`/`off()` rather than `bind()`/`unbind()`, Angular 1.2 only operates with
 jQuery 1.7.1 or above.
@@ -89,7 +89,7 @@ jQuery 1.7.1 or above.
 
 Very testable and designed this way from ground up. It has an integrated dependency injection
 framework, provides mocks for many heavy dependencies (server-side communication). See
-{@link api/ng service} for details.
+{@link ngMock} for details.
 
 
 ### How can I learn more about Angular?
diff --git a/docs/content/misc/started.ngdoc b/docs/content/misc/started.ngdoc
index a6301fa7..3ea5530d 100644
--- a/docs/content/misc/started.ngdoc
+++ b/docs/content/misc/started.ngdoc
@@ -36,4 +36,4 @@ tutorials.
 ##Read more
 
 The AngularJS documentation includes the {@link guide/index Developer Guide} covering concepts and the
-{@link api/ API Reference} for syntax and usage.
+{@link ./api API Reference} for syntax and usage.
diff --git a/docs/content/tutorial/step_00.ngdoc b/docs/content/tutorial/step_00.ngdoc
index 22bbe158..3a0dc070 100644
--- a/docs/content/tutorial/step_00.ngdoc
+++ b/docs/content/tutorial/step_00.ngdoc
@@ -118,7 +118,7 @@ __`app/index.html`:__
 
   This code downloads the `angular.js` script and registers a callback that will be executed by the
 browser when the containing HTML page is fully downloaded. When the callback is executed, Angular
-looks for the {@link api/ng.directive:ngApp ngApp} directive. If
+looks for the {@link ng.directive:ngApp ngApp} directive. If
 Angular finds the directive, it will bootstrap the application with the root of the application DOM
 being the element on which the `ngApp` directive was defined.
 
@@ -149,9 +149,9 @@ for most cases. In advanced cases, such as when using script loaders, you can us
 
 There are 3 important things that happen during the app bootstrap:
 
-1. The {@link api/AUTO.$injector injector} that will be used for dependency injection is created.
+1. The {@link auto.$injector injector} that will be used for dependency injection is created.
 
-2. The injector will then create the {@link api/ng.$rootScope root scope} that will
+2. The injector will then create the {@link ng.$rootScope root scope} that will
    become the context for the model of our application.
 
 3. Angular will then "compile" the DOM starting at the `ngApp` root element, processing any
diff --git a/docs/content/tutorial/step_02.ngdoc b/docs/content/tutorial/step_02.ngdoc
index efafba91..37e91ef7 100644
--- a/docs/content/tutorial/step_02.ngdoc
+++ b/docs/content/tutorial/step_02.ngdoc
@@ -54,7 +54,7 @@ __`app/index.html`:__
 ```
 
 We replaced the hard-coded phone list with the
-{@link api/ng.directive:ngRepeat ngRepeat directive} and two
+{@link ng.directive:ngRepeat ngRepeat directive} and two
 {@link guide/expression Angular expressions} enclosed in curly braces:
 `{{phone.name}}` and `{{phone.snippet}}`:
 
@@ -105,7 +105,7 @@ for our data model, the controller allows us to establish data-binding between
 the model and the view. We connected the dots between the presentation, data, and logic components
 as follows:
 
-* The {@link api/ng.directive:ngController ngController} directive, located on the `<body>` tag,
+* The {@link ng.directive:ngController ngController} directive, located on the `<body>` tag,
 references the name of our controller, `PhoneListCtrl` (located in the JavaScript file
 `controllers.js`).
 
@@ -122,7 +122,7 @@ contained in the template, data model, and controller, to keep models and views
 sync. Any changes made to the model are reflected in the view; any changes that occur in the view
 are reflected in the model.
 
-To learn more about Angular scopes, see the {@link api/ng.$rootScope.Scope angular scope documentation}.
+To learn more about Angular scopes, see the {@link ng.$rootScope.Scope angular scope documentation}.
 
 
 ## Tests
diff --git a/docs/content/tutorial/step_03.ngdoc b/docs/content/tutorial/step_03.ngdoc
index 8866e49c..02069ebc 100644
--- a/docs/content/tutorial/step_03.ngdoc
+++ b/docs/content/tutorial/step_03.ngdoc
@@ -56,8 +56,8 @@ __`app/index.html`:__
 ```
 
 We added a standard HTML `<input>` tag and used Angular's
-{@link api/ng.filter:filter filter} function to process the input for the
-{@link api/ng.directive:ngRepeat ngRepeat} directive.
+{@link ng.filter:filter filter} function to process the input for the
+{@link ng.directive:ngRepeat ngRepeat} directive.
 
 This lets a user enter search criteria and immediately see the effects of their search on the phone
 list. This new code demonstrates the following:
@@ -72,7 +72,7 @@ the DOM to reflect the current state of the model.
 
 <img  class="diagram" src="img/tutorial/tutorial_03.png">
 
-* Use of the `filter` filter: The {@link api/ng.filter:filter filter} function uses the
+* Use of the `filter` filter: The {@link ng.filter:filter filter} function uses the
 `query` value to create a new array that contains only those records that match the `query`.
 
   `ngRepeat` automatically updates the view in response to the changing number of phones returned
@@ -162,8 +162,8 @@ and title elements:
 
   While using double curlies works fine within the title element, you might have noticed that
 for a split second they are actually displayed to the user while the page is loading. A better
-solution would be to use the {@link api/ng.directive:ngBind
-ngBind} or {@link api/ng.directive:ngBindTemplate
+solution would be to use the {@link ng.directive:ngBind
+ngBind} or {@link ng.directive:ngBindTemplate
 ngBindTemplate} directives, which are invisible to the user while the page is loading:
 
           <title ng-bind-template="Google Phone Gallery: {{query}}">Google Phone Gallery</title>
diff --git a/docs/content/tutorial/step_04.ngdoc b/docs/content/tutorial/step_04.ngdoc
index adf362b6..cffc6319 100644
--- a/docs/content/tutorial/step_04.ngdoc
+++ b/docs/content/tutorial/step_04.ngdoc
@@ -49,7 +49,7 @@ two provided sorting options.
 
 <img class="diagram" src="img/tutorial/tutorial_04.png">
 
-* We then chained the `filter` filter with {@link api/ng.filter:orderBy `orderBy`}
+* We then chained the `filter` filter with {@link ng.filter:orderBy `orderBy`}
 filter to further process the input into the repeater. `orderBy` is a filter that takes an input
 array, copies it and reorders the copy which is then returned.
 
diff --git a/docs/content/tutorial/step_05.ngdoc b/docs/content/tutorial/step_05.ngdoc
index 357bbf5b..f717528d 100644
--- a/docs/content/tutorial/step_05.ngdoc
+++ b/docs/content/tutorial/step_05.ngdoc
@@ -42,7 +42,7 @@ Following is a sample of the file:
 
 ## Controller
 
-We'll use Angular's {@link api/ng.$http $http} service in our controller to make an HTTP
+We'll use Angular's {@link ng.$http $http} service in our controller to make an HTTP
 request to your web server to fetch the data in the `app/phones/phones.json` file. `$http` is just
 one of several built-in {@link guide/dev_guide.services angular services} that handle common operations
 in web apps. Angular injects these services for you where you need them.
@@ -72,7 +72,7 @@ relative to our `index.html` file). The server responds by providing the data in
 browser and our app they both look the same. For the sake of simplicity we used a json file in this
 tutorial.)
 
-The `$http` service returns a {@link api/ng.$q promise object} with a `success`
+The `$http` service returns a {@link ng.$q promise object} with a `success`
 method. We call this method to handle the asynchronous response and assign the phone data to the
 scope controlled by this controller, as a model called `phones`. Notice that angular detected the
 json response and parsed it for us!
@@ -193,15 +193,15 @@ describe('PhoneCat controllers', function() {
 ```
 
 Note: Because we loaded Jasmine and `angular-mocks.js` in our test environment, we got two helper
-methods {@link api/angular.mock.module module} and {@link api/angular.mock.inject inject} that we'll
+methods {@link angular.mock.module module} and {@link angular.mock.inject inject} that we'll
 use to access and configure the injector.
 
 We created the controller in the test environment, as follows:
 
 * We used the `inject` helper method to inject instances of
-{@link api/ng.$rootScope $rootScope},
-{@link api/ng.$controller $controller} and
-{@link api/ng.$httpBackend $httpBackend} services into the Jasmine's `beforeEach`
+{@link ng.$rootScope $rootScope},
+{@link ng.$controller $controller} and
+{@link ng.$httpBackend $httpBackend} services into the Jasmine's `beforeEach`
 function. These instances come from an injector which is recreated from scratch for every single
 test. This guarantees that each test starts from a well known starting point and each test is
 isolated from the work done in other tests.
diff --git a/docs/content/tutorial/step_07.ngdoc b/docs/content/tutorial/step_07.ngdoc
index de3bdae6..4c45f2d4 100644
--- a/docs/content/tutorial/step_07.ngdoc
+++ b/docs/content/tutorial/step_07.ngdoc
@@ -35,8 +35,8 @@ our application. Other "partial templates" are then included into this layout te
 the current "route" — the view that is currently displayed to the user.
 
 Application routes in Angular are declared via the
-{@link api/ngRoute.$routeProvider $routeProvider}, which is the provider of the
-{@link api/ngRoute.$route $route service}. This service makes it easy to wire together
+{@link ngRoute.$routeProvider $routeProvider}, which is the provider of the
+{@link ngRoute.$route $route service}. This service makes it easy to wire together
 controllers, view templates, and the current
 URL location in the browser. Using this feature we can implement [deep linking](http://en.wikipedia.org/wiki/Deep_linking), which lets us utilize the browser's
 history (back and forward navigation) and bookmarks.
@@ -106,7 +106,7 @@ module `phonecatControllers`. By listing these two modules as dependencies of `p
 can use the directives and services they provide.
 
 Thus using the `config` API we request the `$routeProvider` to be injected into our config function
-and use the {@link api/ngRoute.$routeProvider#when `$routeProvider.when`} API to define our routes.
+and use the {@link ngRoute.$routeProvider#when `$routeProvider.when`} API to define our routes.
 
 Our application routes are defined as follows:
 
@@ -126,11 +126,11 @@ address doesn't match either of our routes.
 Note the use of the `:phoneId` parameter in the second route declaration. The `$route` service uses
 the route declaration — `'/phones/:phoneId'` — as a template that is matched against the current
 URL. All variables defined with the `:` notation are extracted into the
-{@link api/ngRoute.$routeParams `$routeParams`} object.
+{@link ngRoute.$routeParams `$routeParams`} object.
 
 
 In order for our application to bootstrap with our newly created module we'll also need to specify
-the module name as the value of the {@link api/ng.directive:ngApp ngApp}
+the module name as the value of the {@link ng.directive:ngApp ngApp}
 directive:
 
 __`app/index.html`:__
@@ -172,7 +172,7 @@ Because our example app is relatively small, we'll add all of our controllers to
 
 ## Template
 
-The `$route` service is usually used in conjunction with the {@link api/ngRoute.directive:ngView
+The `$route` service is usually used in conjunction with the {@link ngRoute.directive:ngView
 ngView} directive. The role of the `ngView` directive is to include the view template for the current
 route into the layout template. This makes it a perfect fit for our `index.html` template.
 
diff --git a/docs/content/tutorial/step_08.ngdoc b/docs/content/tutorial/step_08.ngdoc
index 02c03773..25de2cb8 100644
--- a/docs/content/tutorial/step_08.ngdoc
+++ b/docs/content/tutorial/step_08.ngdoc
@@ -16,7 +16,7 @@ phone in the phone list.
 Now when you click on a phone on the list, the phone details page with phone-specific information
 is displayed.
 
-To implement the phone details view we will use {@link api/ng.$http $http} to fetch
+To implement the phone details view we will use {@link ng.$http $http} to fetch
 our data, and we'll flesh out the `phone-detail.html` view template.
 
 The most important changes are listed below. You can see the full diff on [GitHub](https://github.com/angular/angular-phonecat/compare/step-7...step-8):
diff --git a/docs/content/tutorial/step_09.ngdoc b/docs/content/tutorial/step_09.ngdoc
index 0e32001d..2bac44b8 100644
--- a/docs/content/tutorial/step_09.ngdoc
+++ b/docs/content/tutorial/step_09.ngdoc
@@ -113,7 +113,7 @@ our filter tests execute. This call loads our `phonecatFilters` module into the
 for this test run.
 
 Note that we call the helper function, `inject(function(checkmarkFilter) { ... })`, to get
-access to the filter that we want to test.  See {@link api/angular.mock.inject angular.mock.inject()}.
+access to the filter that we want to test.  See {@link angular.mock.inject angular.mock.inject()}.
 
 You should now see the following output in the Karma tab:
 
@@ -122,7 +122,7 @@ You should now see the following output in the Karma tab:
 
 # Experiments
 
-* Let's experiment with some of the {@link api/ng.$filterProvider built-in Angular filters} and add the
+* Let's experiment with some of the {@link ng.$filterProvider built-in Angular filters} and add the
 following bindings to `index.html`:
   * `{{ "lower cap string" | uppercase }}`
   * `{{ {foo: "bar", baz: 23} | json }}`
diff --git a/docs/content/tutorial/step_10.ngdoc b/docs/content/tutorial/step_10.ngdoc
index b16ceaab..d1d3f9c4 100644
--- a/docs/content/tutorial/step_10.ngdoc
+++ b/docs/content/tutorial/step_10.ngdoc
@@ -65,7 +65,7 @@ __`app/partials/phone-detail.html`:__
 
 We bound the `ngSrc` directive of the large image to the `mainImageUrl` property.
 
-We also registered an {@link api/ng.directive:ngClick `ngClick`}
+We also registered an {@link ng.directive:ngClick `ngClick`}
 handler with thumbnail images. When a user clicks on one of the thumbnail images, the handler will
 use the `setImage` event handler function to change the value of the `mainImageUrl` property to the
 URL of the thumbnail image.
diff --git a/docs/content/tutorial/step_11.ngdoc b/docs/content/tutorial/step_11.ngdoc
index b3308cc6..3d86191b 100644
--- a/docs/content/tutorial/step_11.ngdoc
+++ b/docs/content/tutorial/step_11.ngdoc
@@ -53,7 +53,7 @@ of the service - 'Phone' - and the factory function. The factory function is sim
 controller's constructor in that both can declare dependencies via function arguments. The Phone
 service declared a dependency on the `$resource` service.
 
-The {@link api/ngResource.$resource `$resource`} service makes it easy to create a
+The {@link ngResource.$resource `$resource`} service makes it easy to create a
 [RESTful](http://en.wikipedia.org/wiki/Representational_State_Transfer) client with just a few
 lines of code. This client can then be used in our application, instead of the lower-level {@link
 api/ng.$http $http} service.
@@ -72,8 +72,8 @@ We need to add the 'phonecatServices' module dependency to 'phonecatApp' module'
 ## Controller
 
 We simplified our sub-controllers (`PhoneListCtrl` and `PhoneDetailCtrl`) by factoring out the
-lower-level {@link api/ng.$http $http} service, replacing it with a new service called
-`Phone`. Angular's {@link api/ngResource.$resource `$resource`} service is easier to
+lower-level {@link ng.$http $http} service, replacing it with a new service called
+`Phone`. Angular's {@link ngResource.$resource `$resource`} service is easier to
 use than `$http` for interacting with data sources exposed as RESTful resources. It is also easier
 now to understand what the code in our controllers is doing.
 
@@ -128,7 +128,7 @@ We have modified our unit tests to verify that our new service is issuing HTTP r
 processing them as expected. The tests also check that our controllers are interacting with the
 service correctly.
 
-The {@link api/ngResource.$resource $resource} service augments the response object
+The {@link ngResource.$resource $resource} service augments the response object
 with methods for updating and deleting the resource. If we were to use the standard `toEqual`
 matcher, our tests would fail because the test values would not match the responses exactly. To
 solve the problem, we use a newly-defined `toEqualData` [Jasmine matcher](https://github.com/pivotal/jasmine/wiki/Matchers). When the