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

Author: petebacondarwin

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`.

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 {

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.

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.

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:

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.

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.

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.
 

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`}.

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:
 
 ```