Corrections log — published revisions and additions
The Lvlup corrections log is updated as revisions ship. Every entry cites the article URL, the original item, the corrected item and the source the desk re-verified against. Mean correction turnaround is 14 hours.
Recent corrections
Published revisions, last 14 days
LIVE LOG| Date | Article | Item | Citation |
|---|---|---|---|
| 2026-08-01 | Tournaments / APAC Major | Upper-bracket seeds re-verified against publisher qualifier feed; B1/B2 projected (not verified). | Publisher feed · A |
| 2026-07-31 | News / Patch 7.42 | Editorial impact ranking re-anchored against two coach interviews (Hydra, Wolves). | Coach interview · B |
| 2026-07-30 | Teams / Northwind Hydra | Roster verified against team's own published page. | Team page · A |
| 2026-07-29 | Tournaments / EMEA Championship | Stated attendance figure retained as publisher-published, no on-desk override. | Editor's read · C |
Three fields the desk needs
URL
The full URL of the article you are correcting.
Item
The sentence or row you believe is wrong.
Source
A pointer to a publisher or governing body source.
How the desk classifies a correction
The desk classifies every correction into one of four categories. Below is the working method.
Category one — bracket correction
A bracket correction is a change to a bracket position, seed, round number or stage. The desk publishes the correction on the corrections log within 6 hours of the bracket motion.
Category two — score correction
A score correction is a change to a verified score. The desk publishes the correction on the corrections log within 6 hours of the score change.
Category three — story correction
A story correction is a change to a story's claim, citation or framing. The desk publishes the correction on the corrections log within 14 hours on average.
Category four — coverage correction
A coverage correction is a change to a hub's structural surface — a hub card, a sidebar rail, a navigation path. The desk publishes the correction on the corrections log within 14 hours.
Corrections FAQ
How the corrections log is published
Below is the desk's working method for publishing the corrections log. The method is published on this page for editorial transparency.
Daily corrections
The desk publishes daily corrections at 06:00 UTC. The daily entry covers all bracket, score and story corrections published in the previous 24 hours.
Weekly summary
The desk publishes a weekly summary every Monday at 06:00 UTC. The weekly summary groups the prior week's corrections by category.
Quarterly review
The desk publishes a quarterly review at the end of each calendar quarter. The quarterly review groups the prior quarter's corrections by beat.
Annual audit
The desk publishes an annual audit at the end of each calendar year. The annual audit groups the year's corrections by impact — corrections that improved the editorial surface, corrections that introduced a new procedure, corrections that retired a section.
What the corrections log is not
The corrections log is not a corrections forum. The log carries the desk's published revisions; the log is not a comment thread.
The corrections log is not a controversy tracker. The log carries the desk's revisions; the log is not a public disputes page.
Reader questions on the corrections log
Below is the desk's working method for the most common reader questions on the corrections log.
How do I find the most recent correction?
The corrections log is published in reverse chronological order. The most recent correction is at the top of the page. The desk recommends the reader bookmark the page for ease of access.
How do I find a correction older than the current page?
Corrections are archived in editorial archive. A reader who wants a deeper archive uses the editorial archive's search.
How do I send a correction request?
A correction request is sent to the corrections inbox. The desk walks the request within 14 hours on average and publishes the correction on the corrections log.
How do I disagree with a published correction?
A disagreement is sent to the corrections inbox. The desk publishes the disagreement on the corrections log with a timestamp.
How do I request a retraction?
A retraction request is sent to the corrections inbox with the prefix "RETRACT:" in the subject. The desk reviews the request within 14 hours.
How do I report a correction dispute?
A correction dispute is sent to the corrections inbox. The desk publishes the dispute on the corrections log within 14 hours.
How do I read the corrections log offline?
The corrections log is published at a stable public URL. The log can be read offline via a browser's "save as" feature; the log is also exported in the corrections log's archive.
Working method — what the editor on duty does, hour by hour
Below is the desk's hour-by-hour working method for a corrections editor on duty. The method is published on this page for editorial transparency.
Hour one — open the shift
The corrections editor on duty opens the shift by reviewing the publisher feed lock, the bracket structure and the open corrections. The review takes 15 to 30 minutes.
Hour two — process morning corrections
The editor processes morning corrections. The editor walks each request against the live source ladder and publishes the verification result.
Hour three to five — bracket row updates
The editor updates bracket rows where scores have been verified. The updates are tagged with the shift number and timestamped.
Hour six — mid-day correction review
The editor reviews the day's corrections against the corrections log. The mid-day review catches any error caught after the morning publication.
Hour seven to nine — post-match film notes
The editor publishes post-match film notes for any bracket-stage matches where the score has been verified. The notes are filed within 24 hours of the in-game end.
Hour ten — corrections inbox reply
The editor replies to the day's corrections inbox. The replies are on the desk's published SLA.
Hour eleven — daily summary
The editor publishes the daily summary. The summary groups the day's corrections by category.
Hour twelve — handover
The editor prepares the handover note for the next shift. The handover carries the open corrections, the bracket structure, and the next shift's priorities.
What the editor does not do
The editor does not run editorial decisions outside the desk's editorial standard.
The editor does not run commercial decisions on the publisher's product.
The editor does not run a public dispute on the corrections log.