Skip to content

Conversation

@outsideris
Copy link
Contributor

There was some confusion between latest and current in Korean. We discussed it in here. To clarify, we want to change a term for Current. @nodejs/nodejs-ko

Additionally, I updated Korean documents to follow English documents, see changes for more details.

Copy link
Contributor Author

@outsideris outsideris Oct 29, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2016-10-29 9 02 42

어순을 바꿀 수는 없어서 위처럼 기호를 이용했는데 이상할까요?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

굳이 그대로 넣을필요 있나요?

version-schedule-prompt: LTS 일정은
version-schedule-prompt-link-text: 여기서 확인하세요

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

오! 좋은 방법이네요.. 그런 생각은 못했습니다. ㅎ

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

기술적인 기능에 대해 → 기술적인 기능에 대한

@outsideris outsideris force-pushed the change-korean-current branch from f36f6bc to a1d9444 Compare October 30, 2016 14:21
@outsideris
Copy link
Contributor Author

I updated it.

@marocchino marocchino merged commit 7263904 into nodejs:master Oct 31, 2016
@marocchino
Copy link
Contributor

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants