-
Notifications
You must be signed in to change notification settings - Fork 30k
🌐 [i18n-KO] Translated main_classes/optimizer_schedules.md
to Korean
#39713
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
base: main
Are you sure you want to change the base?
🌐 [i18n-KO] Translated main_classes/optimizer_schedules.md
to Korean
#39713
Conversation
- Add TOC anchors to all section headers - Fix terminology and improve Korean expressions
Changed '가중치 감쇠가 수정된' to '가중치 감쇠가 적용된' for more accurate translation of 'weight decay fixed' in the context of optimization.
Changed '에서 상속받는' to '을 상속받는' to follow natural Korean grammar patterns for inheritance terminology.
Changed '파인튜닝된' to '미세 조정된 모델' to follow the established translation glossary for 'finetuned models' terminology.
main_classes/optimizer schedules.md
to Korean
main_classes/optimizer schedules.md
to Koreanmain_classes/optimizer_schedules.md
to Korean
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.
LGTM! 번역 고생하셨습니다. 🤗
LGTM :D |
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.
LGTM thanks!
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
I'll merge this for you once we've ironed out an issue with the doc-builder, no action is necessary on your part! 🤗 |
Thank you for the information🙂 @stevhliu |
build-doc |
What does this PR do?
Translated the
main_classes/optimizer_schedules.md
file of the documentation to Korean.Thank you in advance for your review.
Part of #20179
Before reviewing
[[lowercased-header]]
)Who can review? (Initial)
May you please review this PR?
@jungnerd, @chelsseeey, @skwh54, @amo33, @maximizemaxwell, @D15M4S
@harheem
@4N3MONE
@yijun-lee
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review? (Final)
@stevhliu May you please review this PR?