Trust and information

Corrections Policy

How to report an inaccurate meaning, origin, native spelling, pronunciation, alias, cultural association, or calculation explanation.

Last reviewed: 17 September 2026

What can be corrected

Corrections can concern canonical spelling, native script, transliteration, pronunciation, gender or regional usage, language, origin, meaning, etymology, variants, aliases, internal links, guide wording, or a reproducible calculation defect.

A different personal preference is not necessarily an error. When two regions or sources use a name differently, the best correction may preserve both interpretations with clear labels.

How to submit a useful correction

Email the page URL, quote the exact text, state the proposed replacement, and explain the relevant language, script, historical period, or region. Include a reliable dictionary, linguistic reference, established name authority, academic source, or strong community documentation where possible.

  1. Identify the affected canonical page or guide.
  2. Separate the factual correction from personal interpretation.
  3. Provide native script and transliteration when they matter.
  4. Share a source that can be independently reviewed.

How reviews are handled

A correction is checked against the existing record, aliases, related pages, and calculation rules. We may ask for context when a source represents one regional usage rather than a universal rule.

Accepted changes can revise a field, add an uncertainty note, add a variant, change a canonical relationship, or correct multiple generated links. Rejected changes should not be treated as proof that another usage is invalid; the evidence may simply be insufficient for a canonical statement.

Technical and harmful errors

Security issues, exposed personal information, severe cultural misrepresentation, or a route returning another person's shared details should be identified clearly in the subject line so the report can be prioritized.

Do not include unnecessary sensitive documents in a report. A page URL, screenshot description, and reproducible steps are normally enough.

0 names selected
Compare