docs(chore): fix bad links in the API docs

This commit is contained in:
Naomi Black 2015-09-16 23:28:16 -07:00
parent a588d4894b
commit 563fffd9b0
4 changed files with 6 additions and 5 deletions

View File

@ -99,7 +99,7 @@ export function applicationDomBindings(): Array<Type | Binding | any[]> {
*
* If no bindings are provided, calling {@link platform}() is idempotent,
* and will use the default platform bindings (which can be obtained from
* {@link rootBindings}).
* {@link ApplicationRef/rootBindings}).
*/
export function platform(bindings?: Array<Type | Binding | any[]>): PlatformRef {
return platformCommon(bindings, () => {

View File

@ -308,7 +308,7 @@ export class ApplicationRef {
get injector(): Injector { return this._injector; }
/**
* Retrieve the application {@link Zone}.
* Retrieve the application {@link NgZone}.
*/
get zone(): NgZone { return this._zone; }

View File

@ -148,7 +148,7 @@ export interface DirectiveFactory {
}
/**
* {@link ComponentAnnotation} factory for creating annotations, decorators or DSL.
* {@link ComponentMetadata} factory for creating annotations, decorators or DSL.
*
* ## Example as TypeScript Decorator
*
@ -220,7 +220,7 @@ export interface ComponentFactory {
}
/**
* {@link ViewAnnotation} factory for creating annotations, decorators or DSL.
* {@link ViewMetadata} factory for creating annotations, decorators or DSL.
*
* ## Example as TypeScript Decorator
*

View File

@ -84,7 +84,8 @@ function stringifyAux(instruction: Instruction): string {
* to route lifecycle hooks, like {@link CanActivate}.
*
* `ComponentInstruction`s are [https://en.wikipedia.org/wiki/Hash_consing](hash consed). You should
* never construct one yourself with "new." Instead, rely on {@link PathRecognizer} to construct
* never construct one yourself with "new." Instead, rely on {@link Router/PathRecognizer} to
* construct
* `ComponentInstruction`s.
*
* You should not modify this object. It should be treated as immutable.