What makes a correction useful
A good correction includes the page, the issue and a verifiable source.
Read noteNews works better when it is organized by what happened, what is known and what still needs confirmation.
Recent posts collect local notes, corrections, event reminders and background context.
A good correction includes the page, the issue and a verifiable source.
Read noteSeparate confirmed facts, official comments and open questions before sharing.
Read noteDates, locations and contact details should be visible before extra commentary.
Read noteUpdates are grouped by confirmed detail, context and what may change next.
The first section keeps the latest useful note visible before background material.
Short background notes explain why the update matters and what is still unclear.
Upcoming events, deadlines and public notes are grouped for quick scanning.
Article cards make it easier to revisit previous posts without searching.
Readers can send corrections or tips through one contact path.
The copy avoids certainty when details still need confirmation.
Short answers cover corrections, submissions and how updates are handled.
Yes. Use the contact page and include the page, the correction and a source if available.
No. Developing notes may change as better information becomes available.
Yes, but include date, location, organizer and a public contact link.