Corrections

#The correction process

When a factual or methodological error is identified in a published article — whether found internally or reported by a reader — it is corrected in the article itself, and the correction is recorded in that article's visible revision history. A correction that changes the article's substantive claim also updates dateModified in the article's front matter, which is reflected in the "Updated" date shown on the article.

#How material changes are recorded

Every published article carries a revision history, shown near the end of the piece. A material change — one that alters a claim, a recommendation, or a citation, not a typo fix — gets its own dated entry describing what changed and why. Minor copyediting that does not change meaning is not logged as a separate revision.

#How to report a problem

If you find an error, an outdated claim, a broken reference, or anything else that should be corrected, email info@weavidence.com with the article's URL and a description of the issue. This is the same public contact address used across the rest of the Weavidence site — there is no separate Insights-specific inbox.

#What happens after a report

A reported issue is reviewed against the article's cited sources (or, for a Product Note, against the current state of the Weavidence codebase and documentation it describes). If the report is confirmed, the article is corrected and the revision is logged as described above. If the report identifies a genuine ambiguity rather than an error, the article is clarified rather than left as-is with the ambiguity unaddressed.