Backport README.md from master and update README.korean.md

[songe]

Here is the list of all the changes I've made in this PR:

• Merge branch 'korean-translation' into master
• Remove all ^M characters from README.korean.md
• Update 1.1-2.7 & 4 to sound more natural in Korean
• Backport README.md changes from master into README.korean.md

It may look like a large change since I removed all the ^M characters from the file, but the actual changes are much smaller and organized by commits.

👉 Preview

[kevynb]

Hi @songe, nice work! Any reason you are targeting the branch korean-translation instead of master? I'm asking given that the Korean translation is also available on the master branch.

[songe]

@kevynb Thanks! I actually created a PR against master, but then noticed that the guidelines in #94 said to merge changes into korean-translation branch.

Personally, I think it'd make more sense to merge these directly into master, and I'd be happy to update the PR to target master instead.

[songe]

@kevynb I've rebased the branch against master with korean-translation branch merged it. The change is master-ready, and I've also changed the PR base to master.

[kevynb]

I guess we should wait for another maintainer to chime before merging into master since that’s what the contributing docs says. @goldbergyoni for example?

…

On 25 Mar 2020, at 07:00, songe ***@***.***> wrote: @kevynb <https://github.com/kevynb> I've rebased the branch against master with korean-translation branch merged it. The change is master-ready, and I've also changed the PR base to master. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABFWLH4A2HXJDMC3J6K5FJLRJGMXZANCNFSM4LOGWZCA>.

[songe]

@kevynb @goldbergyoni Any updates on this? I want to continue working on this and translate the rest of the document, but I'd like to make sure this gets merged in first since this is a big change.

[goldbergyoni]

@songe Thanks for the great improvements and sorry waiting - was a bit busy due to the crazy & hectic worldwide situation. Going to be much more available now.

@all-contributors please add @songe for content

[allcontributors]

@goldbergyoni

I've put up a pull request to add @songe! 🎉