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

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.

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.
+the {@link ng.$sce $sce} API doc.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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.

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.

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

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.

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

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

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.

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

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.

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.

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