docs(aio): correct abbreviation - #16295

You need to re-generate the Docs

@Toxicable, not sure what you mean 😕

@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

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

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

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

@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.

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.}