Corrections
Data Corrections for Ono.Jepang.org
Clear, specific reports help Ono.Jepang.org improve Japanese onomatopoeia entries, examples, translations, readings, categories, types, links, and public copy.
1. Correction Overview
Email [email protected]. Include the page URL first, then the word, example, reading, category, type, search result, or public copy that may need correction.
A report can be short. The most useful reports show the exact location, explain why something seems wrong, and suggest a fix when you have one.
2. How to Send a Correction
Use a recognizable email subject, such as Ono.Jepang.org correction: ドキドキ or Example sentence feels stiff.
Corrections are handled by email. Ono.Jepang.org currently has no public correction form, phone number, user account, or guaranteed reply time.
3. What We Can Review
We can review inaccurate translations, definitions that miss nuance, unnatural examples, incorrect furigana or readings, confusing romanization, semantic categories that may be off, onomatopoeia type labels that need checking, related words, typos, and internal links.
You may also report pages that feel too technical, confusing, or less useful for learners. The goal is to make explanations more accurate, clear, and helpful.
4. What Makes a Useful Report
A useful report usually includes the URL, Japanese word, current text, the problematic part, a suggested change, and a reason or supporting source.
Dictionaries, textbooks, corpora, and clear usage examples are helpful but not required. For technical issues, include the device, browser, and what you did before the problem appeared.
5. Review Limits and Updates
Every report is reviewed before a public change is applied. We compare suggestions against available data and keep evidence boundaries clear, especially for nuance between sound, state, movement, texture, and feeling.
Not every suggestion can be accepted, and we do not promise a specific reply or update time. Some reports need extra checking before they can be used.
6. Related Pages
For general questions, technical reports, or messages that are not directly about entry content, use the Contact page.
To understand data scope and claim limits, read the Editorial Policy and Data Sources. For email and technical data questions, see Privacy.