What to report
Report unclear explanations, suspected wrong answer keys, confusing distractor notes, outdated source references, broken links, or pages that feel too broad to help a real study decision.
Corrections
Corrections and content updates
Study tools earn trust by making corrections possible. This page explains how reported content issues are handled.
Correction workflow
- 1Review the reported question, explanation, or page against its stated study purpose.
- 2Check whether the issue is a wrong answer, unclear rationale, outdated source context, weak wording, or user misunderstanding.
- 3Rewrite, relabel, hide, or leave unchanged with clearer explanation as appropriate.
- 4Update the changelog or page-level review date when the correction materially changes user-facing content.
What happens next
A report is treated as a review signal, not proof of error. Content may be revised, relabeled, removed from practice, or clarified. Future versions should expose more public item-level review history.
Current limitation
The current public site does not yet show a full public issue queue. Until that exists, question pages and trust pages should be treated as transparent scope statements rather than a complete editorial history.