Skip to content

Commit aa99df9

Browse files
lgalfasopetebacondarwin
lgalfaso
authored and
petebacondarwin
committed
docs(*): fix dangling links
Fix many dangling links
1 parent 257a3f3 commit aa99df9

31 files changed

Lines changed: 87 additions & 87 deletions

‎docs/content/api/index.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -242,7 +242,7 @@ Use ngSanitize to securely parse and manipulate HTML data in your application.
242242
</tr>
243243
<tr>
244244
<td>
245-
{@link ngTouch#filter Filters}
245+
{@link ngSanitize#filter Filters}
246246
</td>
247247
<td>
248248
The {@link ngSanitize.filter:linky linky filter} is used to turn URLs into HTML links within the provided string.

‎docs/content/error/$compile/ctreq.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Missing Required Controller
44
@description
55

6-
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},
6+
This error occurs when {@link ng.$compile HTML compiler} tries to process a directive that specifies the {@link ng.$compile#directive-definition-object `require` option} in a {@link ng.$compile#comprehensive-directive-api directive definition},
77
but the required directive controller is not present on the current DOM element (or its ancestor element, if `^` was specified).
88

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

‎docs/content/error/$compile/iscp.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,5 +21,5 @@ myModule.directive('directiveName', function factory() {
2121
});
2222
```
2323

24-
Please refer to the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object
24+
Please refer to the {@link ng.$compile#directive-definition-object
2525
`scope` option} of the directive definition documentation to learn more about the API.

‎docs/content/error/$compile/nonassign.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
@description
55

66
This error occurs when a directive defines an isolate scope property
7-
(using the `=` mode in the {@link ng.$compile#description_comprehensive-directive-api_directive-definition-object
7+
(using the `=` mode in the {@link ng.$compile#directive-definition-object
88
`scope` option} of a directive definition) but the directive is used with an expression that is not-assignable.
99

1010
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/$injector/strictdi.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,4 @@ angular.module("myApp", [])
5151
```
5252

5353
For more information about strict-di mode, see {@link ng.directive:ngApp ngApp}
54-
and {@link api/angular.bootstrap angular.bootstrap}.
54+
and {@link angular.bootstrap angular.bootstrap}.

‎docs/content/error/$location/nobase.ngdoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
@description
55

66
If you configure {@link ng.$location `$location`} to use
7-
{@link api/ng.provider.$locationProvider `html5Mode`} (`history.pushState`), you need to specify the base URL for the application with a [`<base href="">`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base) tag or configure
7+
{@link $locationProvider `html5Mode`} (`history.pushState`), you need to specify the base URL for the application with a [`<base href="">`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base) tag or configure
88
`$locationProvider` to not require a base tag by passing a definition object with
99
`requireBase:false` to `$locationProvider.html5Mode()`:
1010

@@ -60,4 +60,4 @@ API](http://caniuse.com/#feat=history), the fallback mechanism provided by `$loc
6060
won't work well without specifying the base url of the application.
6161

6262
In order to make it easier to migrate from hashbang mode to html5 mode, we require that the base
63-
URL is always specified when `$location`'s `html5mode` is enabled.
63+
URL is always specified when `$location`'s `html5mode` is enabled.

‎docs/content/error/$sce/imatcher.ngdoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Invalid matcher (only string patterns and RegExp instances are supported)
44
@description
55

6-
Please see {@link ng.$sceDelegateProvider#resourceUrlWhitelist
6+
Please see {@link $sceDelegateProvider#resourceUrlWhitelist
77
$sceDelegateProvider.resourceUrlWhitelist} and {@link
8-
api/ng.$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the
8+
$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} for the
99
list of acceptable items.

‎docs/content/error/$sce/iwcard.ngdoc‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName The sequence *** is not a valid pattern wildcard
44
@description
55

6-
The strings in {@link ng.$sceDelegateProvider#resourceUrlWhitelist
6+
The strings in {@link $sceDelegateProvider#resourceUrlWhitelist
77
$sceDelegateProvider.resourceUrlWhitelist} and {@link
8-
api/ng.$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not
8+
$sceDelegateProvider#resourceUrlBlacklist $sceDelegateProvider.resourceUrlBlacklist} may not
99
contain the undefined sequence `***`. Only `*` and `**` wildcard patterns are defined.

‎docs/content/error/jqLite/nosel.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
@fullName Unsupported Selector Lookup
44
@description
55

6-
In order to keep Angular small, Angular implements only a subset of the selectors in {@link angular.element#description_angulars-jqlite jqLite}.
6+
In order to keep Angular small, Angular implements only a subset of the selectors in {@link angular.element#angular-s-jqlite jqLite}.
77
This error occurs when a jqLite instance is invoked with a selector other than this subset.
88

99
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/ng/cpi.ngdoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
@description
55

66
This error occurs when attempting to copy an object to itself. Calling {@link
7-
api/angular.copy angular.copy} with a `destination` object deletes
7+
angular.copy angular.copy} with a `destination` object deletes
88
all of the elements or properties on `destination` before copying to it. Copying
99
an object to itself is not supported. Make sure to check your calls to
1010
`angular.copy` and avoid copying objects or arrays to themselves.

0 commit comments

Comments
 (0)