Corrections & Updates

This page is the running log of corrections and material updates to Stack Quarterly pieces. The corrections policy is described on the editorial guidelines page. The short version: we correct in place at the canonical URL and append a dated note at the bottom of the corrected piece. Substantive corrections also get an entry on this page.

How to request a correction

If you spot an error in a piece — a misquoted source, a wrong version number, a misattributed claim, a broken link to a primary record — write to corrections@stackquarterly.com with:

• The URL of the piece.
• The specific sentence or claim you believe is incorrect.
• The correct version, and (if available) a link or source that supports the correction.

We acknowledge correction requests within one business day. We aim to publish the correction (or, if we disagree, a written reply explaining why) within five business days.

We correct typos, broken links, and formatting silently and without a note. Anything that materially changes the reader’s understanding of the piece gets a dated note at the bottom of the piece and an entry below.

What counts as “material”

A change is material when:

• A factual claim in the piece changes (a quote was misattributed, a version number was wrong, a methodology was misstated).
• A source named in the piece is misidentified or wrongly described.
• A conflict of interest that should have been disclosed at publication was missed.
• A code sample does not run as described and the fix is non-trivial.
• A claim about a third party (a vendor, a team, a person) was inaccurate enough to merit a correction in their telling, even if the publication still stands by the broader argument.

A change is not material when it is a typo, a broken link to a piece we still cite, or a style-guide adjustment.

The log

We have not yet shipped a correction at launch. The entry below is the seed entry that explains the corrections-policy itself and serves as a reference for how future entries will be formatted.

2026-05-23 — Inaugural entry: corrections policy established

Piece: This page (/corrections/). What changed: This page was published, formalizing the corrections policy described in the editorial guidelines. Why: A running, dated log is the most accountable form a corrections policy can take. We want the reader to be able to see — at a glance — whether we are issuing corrections at the rate a working publication should, and whether we are correcting the kinds of errors that actually require it.

Future entries will follow the format:

Piece: link to corrected piece. Original publication date: yyyy-mm-dd. Correction date: yyyy-mm-dd. What was wrong: a description of the inaccurate claim. What is correct: the corrected claim. Source for the correction: a link or attribution.

Substantive corrections — ones the writer would not be comfortable having published in the first place if they had had the corrected information — will additionally receive a brief note inside the piece, just below the byline strip, alerting readers entering from a search-engine result that the piece has been corrected since publication.

Retractions

We have not retracted a piece. When and if we do, the retracted piece’s URL will continue to resolve and will display the retraction note (including what the original piece claimed, why we no longer stand by it, and the date of retraction). We do not delete pieces. The reader’s right to see what we previously published — and to judge what we are willing to retract — is more important than our discomfort with old work being legible.

Updates that are not corrections

Some pieces are updated post-publication for reasons that are not corrections: a vendor releases a new version of a tool we covered, an open question we flagged in the piece has been answered, a team we mentioned has since pivoted. These updates appear in an “Update” section at the bottom of the piece with a dated note. They do not show up in this log unless the update materially changes the original claim.

Contact

Corrections inbox: corrections@stackquarterly.com. Editorial inbox (for adjacent inquiries that are not corrections): editorial@stackquarterly.com.