docs: refine English and Korean docs for clarity and consistency

Merged
SE
4mo ago
+90-90

Summary

A "polish once more" pass over the documentation content (English + Korean), continuing the i18n work from #8. I distilled a shared style guide from three references — Vite's concise, active voice; the technical-writing.dev review principles; and Toss's Korean 존댓말 conventions — and applied it across all 57 topic pairs via a multi-agent workflow, with every change adversarially verified against its own diff.

Changes

Korean (41 files)

  • Fixed 19 josa errors — 번들 ends in ㄹ, so it takes 은/을/이, but Webview Bundle는 / Bundle를 were incorrect.
  • Unified terminology — 첫 페인트→첫 화면, 미리보기→미리 보기, 내려받다→다운로드, and the builtin source 내장→빌트인 (generic "built-in signing / SHA check" stays 내장).
  • Removed translationese (번역투) and unnecessary passive constructions.

English (7 files)

  • Passive→active voice, split run-on sentences, tightened wording; grammatical over-the-air (adjective) vs over the air (adverb).

Guardrails

  • No code, commands, API signatures, config keys, URLs, versions, or frontmatter titles changed.
  • English and Korean kept in structural lockstep; net diff is 89/89 balanced (in-place edits only, no lines added or removed).

Validation

  • ✅ yarn gen:fumadocs — all MDX parses
  • ✅ yarn build — full production build passes (all pages incl. Korean variants compile)

🤖 Generated with Claude Code

Summary by cubic

Polished the English and Korean docs for clarity and consistency. Standardized terminology, tightened phrasing, and aligned pages across commands and platforms with no behavior changes.

  • Refactors
    • Korean: fixed 19 josa errors; unified terms (첫 화면, 미리 보기, 다운로드, and 빌트인 for the builtin source); trimmed passives and translationese; corrected one title josa (“Webview Bundle를”→“Webview Bundle을”).
    • English: moved to active voice and shorter sentences; corrected “over-the-air” (adj.) vs “over the air” (adv.); clearer command phrasing (e.g., “omit it”).
    • Cross-pages: aligned wording across command pages (wvb download, wvb pack, wvb builtin/deploy) and platform docs (Electron Builder/Forge, Tauri, Android, Deno, iOS); consistent “built‑in fallback” in KO.
    • Guardrails: no code, commands, API signatures, config keys, or URLs changed; EN/KO kept in structural lockstep; MDX generation and production build pass.