[PROOFREADING] min101 - KO

[bitzealot]

Closes #4395

[Asi0Flammeus]

Hi @bitzealot, thanks for working on this proofreading!

Two things I'd like your call on before I merge:

1. Term: target — in ko.md you adopted 목표치 (with one 타겟 and one 목표값 left over), but 8 quiz files still use 타겟: quizz/005, 011, 012, 013, 021, 023, 034, 038. Was the quiz-side intentional (e.g., 타겟 reserved for the technical Bitcoin difficulty target), or should I propagate 목표치 everywhere?

2. Direction of the bilingual gloss — a bigger question. In ko.md you used the form English(한국어): nonce(논스), coinbase(코인베이스), halving(반감기), Hashcash(해시캐시), etc. Looking at how Korean Bitcoin/CS literature actually handles technical terms, the dominant convention seems to be the reverse — 한국어(English) on first occurrence, then Hangul alone:

   • Official Korean Bitcoin whitepaper (Mincheol Im, hosted on bitcoin.org): 작업증명 proof-of-work, 해시캐시 Hashcash, 이중 지급 double-spending — Korean first.
   • TTA 정보통신용어사전 (Korea's authoritative IT terminology dictionary) and 국립국어원 (National Institute of Korean Language) both recommend 한글(원어) on first occurrence of foreign technical terms.
   • Upbit Investor Protection Center: 비트코인 반감기(Halving)란 ….
   • Toss tech blog / developer glossary: 문서 객체 모델(DOM) then DOM thereafter.
   • Naver / Tistory / Velog Bitcoin posts: 논스(Nonce), 코인베이스 트랜잭션(Coinbase transaction), 멤풀(Mempool), 반감기(Halving).

   So the form a Korean reader of "serious" Bitcoin material expects is 논스(Nonce) → then 논스, not nonce(논스) → then nonce. This would also automatically resolve the consistency leaks I see in the quizzes (nonce alone in quizz/010, 011, 029, 037; coinbase alone in quizz/035, 036, 037; Hashcash alone in quizz/015, 018, 019) — they'd all become 논스(Nonce) / 코인베이스(Coinbase) / 해시캐시(Hashcash) per chapter.

   You're the native speaker, so the call is yours — you may have good reasons for the current direction (e.g., wanting beginners to recognize the English term they'll see in mempool.space, Bitcoin Core docs, etc.). But I wanted to surface the convention question before merging. If you agree with switching to 한국어(English), I'll handle the conversion across ko.md + the 55 quizzes myself — you don't need to do anything. If you'd rather keep English(한국어), that's fine but it means this is a convention that needs to be systematic across all future Korean content too.

Just let me know your preference on each point and I'll take care of the propagation before merging. Thanks!

[bitzealot]

@Asi0Flammeus
Hi! I'm leaving a comment here just in case my email reply didn't go through.

1. Regarding 'target': Please change it to "목표치" everywhere for consistency.
2. Regarding the direction: I totally agree with switching to 한국어(English) format.

Thank you so much for handling the conversion for me!