5 files changed, 9 insertions, 9 deletions
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.