Corrections policy
How to report a mistake in a guide, what we do about it, and how significant corrections are noted.
We want every guide on Web Design Survivalist to be correct. When one is not, we fix it and say so.
How to report an error
Use our contact page. It helps if you include:
- The guide’s title or web address.
- The step or sentence that is wrong.
- What you expected and what actually happened, including any error message.
- Your setup, if it matters: hosting control panel, server type, WordPress version.
Please do not send passwords, API keys or private keys. We will never ask for them.
What we do
- Verify. We check the report against the official documentation and, where we can, test it.
- Fix. If the guide is wrong or out of date, we correct it.
- Update “Last checked”. The guide gets a new “Last checked” date once the whole guide has been re-checked, not only the corrected line.
- Reply. If you left an email address, we let you know what we changed, or why we did not change anything.
How corrections are shown
Small fixes, such as typos, broken links or clearer wording, are made without a note.
Significant corrections get a note at the bottom of the guide, in this form:
Correction: November 7, 2026. An earlier version of this guide gave the wrong file path for the PHP error log on Nginx servers. Step 3 now shows the correct path.
(The note above is an example of the format, not a real correction.)
A correction is significant if the old version could have caused someone to lose data, weaken their security, waste real time, or misunderstand what went wrong.
Our timeline
Our goal is to reply to error reports within five business days, and to fix confirmed errors that could cause harm as soon as we have verified them. That is a goal, not a promise: some reports take longer to test properly.
If a mistake could put a site at risk while we work on it, we may add a warning to the guide or take the affected step down until the fix is ready.
Read more about how we write and test our guides.