CSK vs MI probable XI — confidence label corrected
The original probable XI carried a "Confirmed" label on the seam-bowling slot. The label was corrected to "Strong indication" pending the toss.
Affected page: Match Centre
Corrections log
Corrections log
The public record of substantive corrections to iplplaynow coverage. Trivial typographical errors are corrected without a dated note.
Recent corrections
Each entry records the date of the correction, the page affected, and a summary of the change.
Chinnaswamy venue brief — boundary size update
The published boundary size for the straight was updated to reflect the latest ground authority measurement. The previous value was 65m; the corrected value is 64m.
Affected page: Chinnaswamy pitch brief
Tournament format note
The published format note referred to a 72-match season. The correct figure is 74 matches across the 10-team league stage plus playoffs.
Affected page: IPL 2026 reference
Player profile — role clarification
A player profile on the players desk carried an incorrect role description. The profile was updated to reflect the correct batting slot.
Affected page: Players desk
Send a correction
If you spot an error in our coverage, please send the URL of the page, the section in question, and the source that contradicts the published claim. Substantive corrections are added to this log.
Contact the editors
How to read the log
What the corrections log tells you
The corrections log is the public record of substantive corrections to our coverage. It is not a list of every change — typographical fixes are made without a dated note — but it does include every correction that affects a claim, a statistic, a role label, or an attribution.
A corrections log is a useful signal because it tells you what the publication got wrong and how it handled the error. A publication that publishes corrections openly is one that takes its standards seriously; a publication that silently amends text is one that does not.
The log is updated whenever a substantive correction is made. If you spot an error that isn't on the log, send the URL of the page, the section in question, and the source that contradicts the published claim.
Why corrections matter
Why we publish corrections openly
Trust
A reader who can see that the publication corrects its own work is a reader who can trust the publication's other claims.
Transparency
Corrections show our working — what we got right, what we got wrong, and how the right and wrong were distributed across the season.
Improvement
The accumulation of corrections over a season is the clearest signal of where our editorial process needs to improve. We use the log internally to update our editorial workflow.