How we work / Corrections
Corrections
A site that promises to quote the terms owes you a list of the times it quoted them wrong. This is that list. Nothing is removed from it.
How corrections work here
A correction is a change to a fact we published: a dollar figure, a date, a deadline, an eligibility rule, or a claim about whether a program exists. Rewording, design changes and updates that follow a company changing its terms are not corrections; those move a guide’s Examined date instead.
When we find one, or a reader does, we fix the guide the same day, re-read the source document end to end, move the guide’s Examined date, and add an entry below with the wrong text, the right text, and how the error happened. The guide itself gets a dated note at the point of the change for thirty days.
Tell us about an error at /contact. Include the page, the sentence, and the document you read. We reply to every report that names a source.
The list
2026-09-11 · /moomoo
- We said
- This page said the moomoo welcome bonus ends August 31, 2026, and repeated that date in the glance strip, the steps, the deadline note and the disclosure.
- Correct
- Moomoo's own terms give a promotion period of January 1, 2026 to December 31, 2026. The offer was live the whole time we were telling readers it had closed.
- How it happened
- We recorded the August 31 date from an earlier reading and never re-read the document when that date passed. The verification gate did flag the offer as expired on every build, but the warning was read as 'this offer is over' rather than 'go and check', so for eleven days the page told readers a live offer had ended. The gate now derives an offer's live-or-ended status from its own end date, so a lapsed date can no longer sit on the page looking current, and re-reading the terms is what the warning means.
2026-07-27 · /blockchain-com
- We said
- This page stated that Blockchain.com published no referral program at all.
- Correct
- Blockchain.com's referral program exists and its own overview article says it is temporarily paused for maintenance and operational improvements.
- How it happened
- On July 25 support.blockchain.com was refusing our requests. The main domain showed no referral page, no referral entry in its own site index and no referral clause in its terms, so we concluded the programme did not exist and rewrote the page to say so. That was an over-correction: our original July 24 reading had been right. On July 27 a tool that could reach the support subdomain read the article live. The lesson is the one we apply to everybody else and had not applied to ourselves: when the pages that matter live on a subdomain you cannot reach, finding nothing on the domain you can reach is not evidence that nothing is there.