Improve Korean README for natural, native phrasing

[atmigtnca]

Summary

• Improve Korean README (README.ko.md) for natural, native-sounding Korean
• Replace stiff machine-translated expressions with idiomatic Korean (Toss-style 해요체)
• Fix unnatural word choices: 리스닝 포트→수신 포트, 구축→제작, 양식을 작성→양식을 채우다, etc.

Testing

• Reviewed all changes line-by-line for natural Korean phrasing
• No code changes — translation/copy only

Demo Video

N/A (text-only change)

Review Trigger (Copy/Paste as PR comment)

@codex review
@coderabbitai review
@greptile-apps review
@cubic-dev-ai review

Checklist

• I tested the change locally
• I added or updated tests for behavior changes
• I updated docs/changelog if needed
• I requested bot reviews after my latest commit (copy/paste block above or equivalent)
• All code review bot comments are resolved
• All human review comments are resolved

---

Summary by cubic

Rewrote the Korean README (README.ko.md) in natural, idiomatic 해요체 to replace stiff machine-translated text and improve clarity. Updated key terms and phrasing (e.g., 리스닝 포트→수신 포트, 구축→제작, 양식을 작성→양식을 채우다); docs-only change.

^{Written for commit 13d8d56. Summary will update on new commits.}

Summary by CodeRabbit

• Documentation
  • Enhanced Korean README with modernized wording and improved phrasing for better clarity and readability throughout the documentation.

[vercel]

@atmigtnca is attempting to deploy a commit to the Manaflow Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 97bf3cbf-e8eb-42cd-a4b5-7c44fc32b2aa

📥 Commits

Reviewing files that changed from the base of the PR and between 71ab591 and 13d8d56.

📒 Files selected for processing (1)

• README.ko.md

---

📝 Walkthrough

Walkthrough

The Korean README receives stylistic and wording refinements to modernize phrasing across UI terminology, tooltips, and usage instructions. The changes improve natural expression without introducing functional alterations or API modifications.

Changes

Cohort / File(s)	Summary
Korean README Documentation README.ko.md	Stylistic and wording tweaks modernizing phrasing for UI descriptions, button/keyboard text, and installation notes. Content-only updates with no functional or logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 한글 문서 다듬어 반짝반짝,
말 고르고 또 골라 자연스럽게,
우리의 설명이 더욱 아름다워,
사용자들 만날 날을 기대하며! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: improving the Korean README for natural, native phrasing. It directly matches the changeset content.
Description check	✅ Passed	The description covers all required sections: Summary (what changed and why), Testing (how validated), Demo Video (appropriately marked N/A), Review Trigger, and Checklist. All critical information is provided.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR improves the Korean README (README.ko.md) by replacing stiff, machine-translated phrasing with natural, idiomatic Korean using the conversational 해요체 register (Toss-style), making the document feel friendlier and more approachable to Korean readers. No code or functional changes are made.

Key changes:

• Converted formal ~합니다/~입니다 endings to natural ~해요/~어요 endings throughout
• Improved technical terminology: 리스닝 포트 → 수신 포트, 양식을 작성 → 양식을 채우고, 구축 → 만들었어요, 스크립트 가능 → 스크립팅
• Rewrote the subtitle and feature descriptions for conciseness and clarity (e.g., 기능을 갖춘 → 을 지원하는)
• License section name switched from a Korean translation (GNU Affero 일반 공중 사용 허가서) to the standard English name (GNU Affero General Public License), which aligns with common Korean technical writing conventions
• All changes are translation/copy only with no accuracy or factual regressions identified

Confidence Score: 5/5

• This PR is safe to merge — it is a documentation-only change with no code modifications.
• All changes are confined to a single Markdown README file with no code, configuration, or logic alterations. The Korean phrasing improvements are accurate, idiomatic, and introduce no factual errors or meaning changes relative to the original content.
• No files require special attention.

Important Files Changed

Filename	Overview
README.ko.md	Korean README updated from formal machine-translated 합쇼체/습니다체 to natural, idiomatic 해요체 (Toss-style); terminology improvements include 리스닝 포트→수신 포트 and 양식을 작성→양식을 채우고; no factual or structural errors introduced.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Original README.ko.md\nMachine-translated 합쇼체/습니다체] --> B{Review changes}
    B --> C[Terminology fixes\n리스닝 포트 → 수신 포트\n양식을 작성 → 양식을 채우고\n구축 → 만들었어요]
    B --> D[Register shift\n~합니다/~입니다 → ~해요/~어요\nToss-style 해요체]
    B --> E[Conciseness improvements\n기능을 갖춘 → 을 지원하는\n모든 대기 중인 → 대기 중인]
    C --> F[Updated README.ko.md\nNatural, idiomatic Korean]
    D --> F
    E --> F

Loading

_{Last reviewed commit: 13d8d56}

[cubic-dev-ai]

No issues found across 1 file

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Add one-off context when rerunning by tagging @cubic-dev-ai with guidance or docs links (including llms.txt)
• Ask questions if you need clarification on any suggestion

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[lawrencecchen]

Thank you!