Rename "ES2015" in project

[morkro]

👋 Hey!

I feel like the project isn't only about ES2015 anymore but ES features in general. Does it make sense to rename "Node.js ES2015 Support" and "Node.js ES2015 compatibility tables" from the header of the website and README?

[williamkapke]

Def in the README. On the website, when you scroll down (almost bottom)... the header changes to 2016 and then 2017. That was my quick solution to getting the other version on the page... but yeah- it makes it seem like the site is only about 2015 features. I'm open to ideas on making it better.

[morkro]

Maybe if you rename the website header to "Node.js Feature Support" but still keep the deep links to #2015, #2016, #2017. It would still all make sense, no?

[williamkapke]

I updated the readme like you said. Thanks for the reminder.
.. but on the website-- I'm still unsure how to make it right 🤔

I'll leave this open and continue to think about it.