@@ -191,7 +191,7 @@ include ../_util-fns
191
191
+ makeExample('upgrade-module/ts/src/app/hero-detail.directive.ts' )
192
192
193
193
:marked
194
- AngularJS.5 introduces the [component API](https://docs.angularjs.org/api/ng/type/angular.Module)
194
+ AngularJS 1 .5 introduces the [component API](https://docs.angularjs.org/api/ng/type/angular.Module)
195
195
that makes it easier to define directives like these. It is a good idea to use
196
196
this API for component directives for several reasons:
197
197
@@ -206,7 +206,7 @@ include ../_util-fns
206
206
207
207
:marked
208
208
Controller lifecycle hook methods `$onInit()`, `$onDestroy()`, and `$onChanges()`
209
- are another convenient feature that AngularJS.5 introduces. They all have nearly
209
+ are another convenient feature that AngularJS 1 .5 introduces. They all have nearly
210
210
exact [equivalents in Angular](lifecycle-hooks.html), so organizing component lifecycle
211
211
logic around them will ease the eventual Angular upgrade process.
212
212
@@ -579,7 +579,7 @@ figure
579
579
[described in the preparation guide above](#using-component-directives).
580
580
Our safest bet for ensuring compatibility is using the
581
581
[component API](https://docs.angularjs.org/api/ng/type/angular.Module)
582
- introduced in AngularJS.5.
582
+ introduced in AngularJS 1 .5.
583
583
584
584
A simple example of an upgradable component is one that just has a template
585
585
and a controller:
@@ -927,7 +927,7 @@ figure
927
927
.file scenarios.js
928
928
929
929
:marked
930
- This is actually a pretty good starting point. The code uses the AngularJS.5
930
+ This is actually a pretty good starting point. The code uses the AngularJS 1 .5
931
931
component API and the organization follows the
932
932
[AngularJS Style Guide](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md),
933
933
which is an important [preparation step](#following-the-angular-style-guide) before
@@ -1040,9 +1040,9 @@ code-example(format="").
1040
1040
1041
1041
.l-sub-section
1042
1042
:marked
1043
- The [AngularJS.x type definitions](https://www.npmjs.com/package/@types/angular)
1043
+ The [AngularJS 1 .x type definitions](https://www.npmjs.com/package/@types/angular)
1044
1044
we installed are not officially maintained by the Angular team,
1045
- but are quite comprehensive. It is possible to make an AngularJS.x application
1045
+ but are quite comprehensive. It is possible to make an AngularJS 1 .x application
1046
1046
fully type-annotated with the help of these definitions.
1047
1047
1048
1048
If this is something we wanted to do, it would be a good idea to enable
@@ -1196,7 +1196,7 @@ code-example(format="").
1196
1196
1197
1197
:marked
1198
1198
The arguments used here are the root element of the application (which is
1199
- the same element we had `ng-app` on earlier), and the AngularJS.x modules
1199
+ the same element we had `ng-app` on earlier), and the AngularJS 1 .x modules
1200
1200
that we want to load. Since we're bootstrapping the app through
1201
1201
an `UpgradeModule`, we're actually now running the app as a **hybrid app**.
1202
1202
0 commit comments