docs(aio): correct abbreviation

[swseverance]

change abbreviation from 'ES' to 'ES2015'. the 'ES2015' abbreviation is used elsewhere in the tutorial.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Other... Please describe: Fix to documentation

What is the current behavior? (You can also link to an open issue here)

What is the new behavior?

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[Toxicable]

You need to re-generate the Docs

[gkalpak]

@Toxicable, not sure what you mean 😕

[Toxicable]

@gkalpak Neither am I. The error in Travis said that the docs that the docs should be regnerated, so I was just reiterating that incase it was missed to try get this through since it's an easy one

[gkalpak]

The Travis failure was a flake 😃 I restarted it and it's all good now.
This looks good to go (cc @wardbell).

[IgorMinar]

Unfortunately I don't think that this change is right. The import keyword is part of the ES (ECMAScript) spec, it just happened to be introduced in ES2015, but that's not really interesting to the reader. We should stay away from listing the versions of any kind anywhere (ES spec or Angular) unless we actually want to point out when that particular feature was introduced.

cc: @wardbell

[swseverance]

If that's the case you may consider replacing the references to 'ES2015' found in toh-pt1.md & toh-pt4.md

[wardbell]

@IgorMinar - @swseverance has a point. We have called out ES2015 all over the place.

Many of us who routinely write about such things have called out features introduced in ES2015 so people who know only old JavaScript become aware of the change. Module support is still shocking to most developers as I write this.

Maybe you're right that it's time to stop doing that and we can just say ES from now on (or why not just say "JavaScript"?). We can start a sweep to replace all "ES2015" as a separate effort in a separate PR.

Meanwhile, I'll approve this in my capacity as "docs editor" and we can discuss a change of policy offline.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}