-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
change Korean term for Current #1001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
version-schedule-prompt: Or have a look at the | ||
version-schedule-prompt-link-text: LTS schedule | ||
version-schedule-prompt: 참고하세요 -> | ||
version-schedule-prompt-link-text: LTS 일정 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
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: 여기서 확인하세요
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
오! 좋은 방법이네요.. 그런 생각은 못했습니다. ㅎ
|
||
### 안내 | ||
|
||
Node.js의 기술적인 기능에 대해 길고 상세한 글 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
기술적인 기능에 대해 → 기술적인 기능에 대한
f36f6bc
to
a1d9444
Compare
I updated it. |
Thanks |
There was some confusion between
latest
andcurrent
in Korean. We discussed it in here. To clarify, we want to change a term forCurrent
. @nodejs/nodejs-koAdditionally, I updated Korean documents to follow English documents, see changes for more details.