i18n(ko): automated Crowdin translation import (part 05 of 13)

[minimalsm]

Summary

• Part 05 of 13 — ko translation import split from i18n: automated Crowdin translation import (ko) #17166
• 23 files

Context

Split from the original large import PR for easier review and independent merging.

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	7c7eaf5
🔍 Latest deploy log	https://app.netlify.com/projects/ethereumorg/deploys/6992fd71d215e00008cde051
😎 Deploy Preview	https://deploy-preview-17395.ethereum.it
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 58 (🟢 up 3 from production) Accessibility: 94 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 59 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[minimalsm]

Translation Quality Review

Language: Korean (ko)
Files Reviewed: 23 files
Overall Score: 92/100

Quality by Category

Category	Score	Issues Found
Brand Names	100/100	✓ All brand names correctly preserved (Geth, MetaMask, Frame, Nimbus, Helios, LodeStar, Lighthouse, Lodestar, Prysm, Teku, Grandine, Besu, Erigon, Nethermind, Reth, EthereumJS)
Code/Technical Terms	100/100	✓ Code blocks properly untranslated
Markdown Syntax	95/100	⚠️ Minor issues with sentence endings
Frontmatter	100/100	✓ Tags properly preserved in English
Crowdin Artifacts	85/100	⚠️ Multiple sentence ending issues (함 → 합니다)

Issues Found

1. Incomplete sentence endings (Crowdin artifact)

   • Multiple instances of Korean sentences ending with "함" instead of proper "합니다"
   • Example: "필요함" should be "필요합니다"
   • This is a common Crowdin translation pattern that needs correction

2. Malformed anchor IDs in headers

   • Found "클라이언트-충격" suffixes in section headers (node-architecture/index.md)
   • These appear to be translation artifacts that shouldn't be in the anchor IDs

3. Minor spacing issues

   • Missing spaces in Korean text (e.g., "컴퓨터 (노드) 들" → "컴퓨터(노드)들")
   • "블럭" should be "블록" (correct Korean spelling)

Fixes Applied

✓ Corrected sentence endings from "함" to "합니다" pattern (6 instances)
✓ Removed malformed anchor suffixes "클라이언트-충격" from headers (2 instances)
✓ Fixed spacing conventions in Korean text
✓ Corrected "블럭" to "블록"

Summary

The Korean translation quality is generally excellent with proper preservation of:

• Technical terminology and brand names
• Code blocks and syntax
• Markdown formatting
• Links and references

The main issues were Crowdin-generated sentence ending patterns that needed to be normalized to proper Korean grammar. All identified issues have been corrected and pushed to the branch.

Recommendation: ✅ Approve with fixes applied

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[wackerow]

Closing in lieu of:

• i18n: automated Crowdin translation import (ko) #17166