Corrections make the tools better.
Use the public project tracker to report a textual, technical, accessibility, attribution, or usability issue.
Where to send feedback
Bible Original Languages uses the project's public GitHub issue tracker for contact. A public tracker keeps each correction connected to the relevant source file, makes the status visible, and prevents the same problem from being reported repeatedly.
What makes a useful report
Include the page address, the exact Hebrew, Greek, English, button, or browser behavior involved, and what you expected instead. For a textual correction, cite a critical edition, lexicon, grammar, dataset record, or other checkable source whenever possible. For a technical problem, include your device, browser, and the steps that reproduce it.
- Text, gloss, morphology, transliteration, or pronunciation corrections
- Broken links, inaccessible controls, contrast, keyboard, or screen-reader problems
- Mobile layout failures, browser errors, lost study data, or print issues
- Missing attribution, licensing concerns, or privacy questions
Scope
The tracker is for concrete improvements to this free study site. It is not a private counseling channel, a venue for doctrinal disputes, or a substitute for instruction from a qualified language teacher. Questions that depend on theology rather than a verifiable textual or technical issue may not receive a project response.
Before reporting
Refresh the page once, confirm the issue still occurs, and search existing reports for the relevant word or page name. Please do not include passwords, private verse-deck exports, personal records, or other sensitive information. Reports are public and may be quoted in commit history when a correction is made. For general background, sources, and project limitations, read the About page and Resources page first.