# Corrections and contributions

These pages are derived from a private repository through a publication
checklist, and this GitHub repository is a mirror of the public result. That
shapes how a correction travels.

**Open an issue** for anything factual, unclear or broken: a wrong figure, a
contradiction between pages, a dead link, a lesson whose rule does not follow
from its story, a bug in one of the tools. Say which page or file, the capture
date or lesson dates it carries, what you believe is wrong, and what you are
going by. Issues are read by the maintainers and notify them.

**What happens next.** A correction is checked against the private source. If the
source is wrong, it is fixed there and the page is republished from it, marked as
a correction to the capture it belongs to; if the page mis-stated a correct
source, the page is fixed and republished the same way. Either way the fix
arrives here through the next push, with the issue linked.

**Patches.** You are welcome to propose a change as a patch or a pull request,
and it will be read as a suggestion. Nothing is merged into this mirror
directly, because the mirror is overwritten from the origin on every push; a
proposal that is taken is applied at the origin and credited in the commit.

**Tools.** The two tools under `tools/` are MIT-licensed and meant to be copied.
A bug report on them is welcome as an issue; a fix as a patch, read the same
way. The gate's tests must stay green.

**Scope.** This is not a help desk for building your own site. The pages are
meant to be exactly that, and a question they fail to answer is itself a good
issue: say what you were trying to do and where the page lost you.

**Something that should not have been published** is not an issue. See
[`SECURITY.md`](SECURITY.md).