ngUpgrade documentation appears to self-contradict

[jmwolfe]

Description

First this section says:

So normally a hybrid application begins life as an AngularJS application, and it is AngularJS that processes the root template, for example, the index.html. Angular then steps into the picture when an Angular component is used somewhere in an AngularJS template. The template of that component will then be managed by Angular, and it may contain any number of Angular components and directives.

A little later on it says:

To bootstrap a hybrid application, you must bootstrap each of the Angular and AngularJS parts of the application. You must bootstrap the Angular bits first and then ask the UpgradeModule to bootstrap the AngularJS bits next.

it's very counter-intuitive that if AngularJS reads the initial index.html and starts the application, that you would be bootstrapping Angular first. By "starts life" do you mean it was written years ago in AngularJS?

What is the affected URL?

https://angular.io/guide/upgrade#upgrading-with-ngupgrade

Please provide the steps to reproduce the issue

It's documentation, n/a

Please provide the expected behavior vs the actual behavior you encountered

I would expect all the documentation to not contradict itself

Please provide a screenshot if possible

No response

Please provide the exception or error you saw

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version.

No

[atscott]

Yes, "starts life" refers to an application that was written in AngularJS and is being upgraded to Angular gradually.