honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(api): remove extra the

Browse Source
This commit is contained in:
Wassim Chegham 2015-11-25 23:06:06 +01:00 committed by Jeremy Elbourn
parent c08d76c7f8
commit cf3ceba2cc
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
modules/angular2/src/router/location_strategy.ts
View File

@ -3,7 +3,7 @@ import {OpaqueToken} from 'angular2/core';
/** /**
* `LocationStrategy` is responsible for representing and reading route state * `LocationStrategy` is responsible for representing and reading route state
* from the the browser's URL. Angular provides two strategies: * from the browser's URL. Angular provides two strategies:
* {@link HashLocationStrategy} (default) and {@link PathLocationStrategy}. * {@link HashLocationStrategy} (default) and {@link PathLocationStrategy}.
* *
* This is used under the hood of the {@link Location} service. * This is used under the hood of the {@link Location} service.

2
modules/angular2/src/upgrade/upgrade_adapter.ts
View File

@ -68,7 +68,7 @@ var upgradeCount: number = 0;
* Angular v2 directive, which bootstraps the AngularJS v1 component directive in that location. * Angular v2 directive, which bootstraps the AngularJS v1 component directive in that location.
* 6. An Angular v2 component can be downgraded to an AngularJS v1 component directive. This creates * 6. An Angular v2 component can be downgraded to an AngularJS v1 component directive. This creates
* an AngularJS v1 directive, which bootstraps the Angular v2 component in that location. * an AngularJS v1 directive, which bootstraps the Angular v2 component in that location.
* 7. Whenever an adapter component is instantiated the host element is owned by the the framework * 7. Whenever an adapter component is instantiated the host element is owned by the framework
* doing the instantiation. The other framework then instantiates and owns the view for that * doing the instantiation. The other framework then instantiates and owns the view for that
* component. This implies that component bindings will always follow the semantics of the * component. This implies that component bindings will always follow the semantics of the
* instantiation framework. The syntax is always that of Angular v2 syntax. * instantiation framework. The syntax is always that of Angular v2 syntax.