Goal
Native-speaker review of the four translated READMEs for tone, idiom, and technical-term consistency. Open a PR with edits, or comment with section-by-section feedback.
The READMEs were initially machine-translated. A native review for audit-worthy phrasing makes a real difference for non-English speakers landing on the repo.
Languages
What to look for
- Awkward machine-translation phrasing
- Technical terms that don't match local convention (e.g., "policy-as-code" → 한국어 / 中文 / 日本語 / हिन्दी standard term)
- Regulatory terms (EU AI Act, NIST AI RMF) — should match how local press / govt translates them
- Anything that reads as ChatGPT output rather than how a practitioner would write
Acceptance criteria
Per language:
Sub-PRs per language are welcome — feel free to handle just one and leave the rest for someone else.
Get help
Comment with the language you want to take and we'll coordinate to avoid overlap.
Goal
Native-speaker review of the four translated READMEs for tone, idiom, and technical-term consistency. Open a PR with edits, or comment with section-by-section feedback.
The READMEs were initially machine-translated. A native review for audit-worthy phrasing makes a real difference for non-English speakers landing on the repo.
Languages
What to look for
Acceptance criteria
Per language:
Sub-PRs per language are welcome — feel free to handle just one and leave the rest for someone else.
Get help
Comment with the language you want to take and we'll coordinate to avoid overlap.