한국어 코스 구조 및 노트북 링크 수정 (Fix Korean course structure and notebook links) #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes several structural and linking issues in the Korean translation of the Hugging Face Course that were affecting the user experience for Korean learners.
Issues Fixed
1. Duplicate Chapter Titles in Table of Contents
The Korean
_toctree.ymlfile contained duplicate entries for "3. 🤗 사전훈련된 모델 미세조정" (Fine-tuning a pretrained model), which caused navigation confusion:Before:
After:
2. Incorrect Notebook Links
All Korean course files were linking to English notebooks (
course/en/chapter*) instead of Korean ones (course/ko/chapter*), preventing Korean users from accessing localized notebook content.Before:
After:
Files Changed
chapters/ko/_toctree.yml: Fixed duplicate chapter structureen) to Korean (ko)Validation
This improvement ensures Korean learners have a consistent and properly structured learning experience with access to the correct language-specific resources.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.