Corrections

Clear cycling guidance depends on readers telling us when something is wrong, outdated, inaccessible, or easy to misunderstand. We welcome specific correction reports, especially when an error could affect safety or equipment compatibility.

What to include

• The URL and section heading where you found the issue.
• The exact statement, image, interaction, or link involved.
• Why you believe it is inaccurate or unclear.
• A primary or authoritative source when one is available.
• Whether the issue could create an immediate safety risk.

How to report it

Until a dedicated editorial mailbox is published, open a report in the SIKLIST GitHub issue tracker. GitHub issues are public, so do not include personal, medical, financial, location, or other sensitive information.

If a report contains sensitive information, wait for the dedicated private contact channel rather than posting it publicly.

What happens next

1. We identify the precise claim or behavior and assess urgency.
2. We check the page, its sources, and the most appropriate current primary evidence.
3. We correct confirmed errors and retest affected links, images, or interactions.
4. We update the page date when the change is material.
5. We explain substantial corrections when the original error could meaningfully change a reader’s decision or safety.

Corrections are not disagreements by default

Cycling advice often involves tradeoffs. A different preference is not necessarily an error, but it may show that a page needs clearer assumptions, alternatives, or boundaries. We consider those reports editorially even when the original statement remains.