[Fix] Fix typo errors

[ghost]

[Senario]
Someone is now accessing the home page with a root path / ( Such as https://nodejs.org/)：

The current is now guiding you to an English page.

Now I guide you to a page where you like according to your local system language from accept-language, which looks better and more friendly.

[Notices]
Please run npm i to install a 3-rd party accept-language before you run or deploy this.

[ghost]

LGTM!

[lpinca]

This would not work in production as the server is only used for development. Not sure how useful this feature is for development.

[ghost]

@lpinca：
I had a test before submitting here, and everything goes fine with me.

For FF and Chrome, it can read out accept-language and guide me where I actually want to go.
For IE, some IEs cannot pre-set the accept-Language so the default is still English.

All in all, I only check when you are accessing the root without a default language, it will try to fetch your pre-set lang from the browser (Maybe according to your localization system) and guide you to a correct website of a lang. Because I didn't change any rules but just attach dynamically lang to the root

E.g:
If you are accessing——https://nodejs.org/ => It will guide to https://nodejs.org/lang , if some lang is checked.

And This would not work in production as the server is only used for development. What does this mean? Have u got any special things on your server? So have you got any suggestions or ideas?
Is it possible to make the same function on the deployment?

Thanks anyway!

[fhemberger]

@Maledong Files in production are served pre-gzipped through nginx (using npm run deploy) for performance reasons. Config can be found here: https://github.com/nodejs/build/blob/master/setup/www/resources/config/nodejs.org

We already had a discussion about this in: #806 (comment) (and even in the io.js days: nodejs/iojs.org#235)

Unfortunately, there's only a 3rd party module for nginx. So this has to be addressed by the @nodejs/build team.

[ghost]

Well thanks all!

I changed my commit to fix a typo error instead. Language will be discussed with all of you later after I read your discussion first.