Corrections
When a page gets something wrong, it is fixed in public with a record of what changed. This page explains how corrections work and holds the running log of substantive changes to published pages.
Please note. This log is currently empty. We are publishing it before we need it rather than after — an empty log with a stated policy is more honest than a log created the first time someone catches a mistake.
In short
Substantive corrections are noted on the affected page and logged here with a date and a description of what changed. Typos and formatting fixes are not logged. Corrections to safety-relevant content are treated as urgent.
What gets logged
| Change | Logged? |
|---|---|
| A number, temperature, time, or percentage was wrong | Yes, and flagged on the page |
| A source was misattributed or superseded | Yes |
| A safety statement was incomplete or incorrect | Yes, urgently, and the page is unpublished until fixed |
| A claim about a named business or product was inaccurate | Yes |
| A worked example's arithmetic was wrong | Yes, and flagged on the page |
| A conclusion changed based on new evidence | Yes |
| Typo, punctuation, broken link, layout fix | No |
| Routine addition of new sections | No |
How a correction is handled
For anything safety-relevant, the page comes down first and goes back up after review. We do not leave incorrect safety guidance live while we work out the fix.
For everything else, the page is corrected, a dated note appears on the page describing what changed, and an entry is added here. We do not quietly overwrite and move on.
Where a correction changes the practical advice — a different hydration range, a different bake condition, a different conclusion — the note says so explicitly, because a reader who acted on the old version needs to know.
Why we publish an empty log
An empty corrections page looks like a page nobody needed. It is actually a commitment made in advance.
Publications that add a corrections process after their first public mistake tend to design it to minimise the mistake. Designing it while there is nothing at stake produces a better policy, and it means the first correction goes into an existing structure rather than becoming a decision.
Over time, a log with entries in it is a better signal than an empty one. A technical reference that has never corrected anything is either very new or not looking very hard.
Checking a claim yourself
Boccalone does not currently publish a reader inbox, so there is no reporting queue to join. If a figure looks wrong, open the source it links to and compare; the source is the authority, not this page.
Questions about your own oven or food safety belong with the manufacturer or the relevant authority. The contact page lists them.
Where to go next
Frequently asked questions
How quickly are errors fixed?
Safety-relevant corrections come first, and the page is unpublished in the meantime. Other corrections are made once the problem has been verified against the source.
What if the source and the page disagree?
The source wins. The page is corrected, a dated note says what changed, and the change is logged here.
Do you update old pages when the underlying source changes?
Yes. When a cited specification is revised, the pages that cite it are re-read against the new version, and any substantive change is logged here.
Is every change a correction?
No. Typos, punctuation, broken links, and layout fixes are not logged. A change that alters a figure, a source, a safety statement, or a conclusion is.
Check a claim at its source
Every figure on the site links to the source it came from, which is the fastest way to confirm or rule out an error.