Corrections policy
Tool coverage goes stale and mistakes happen. This is how both get fixed, visibly.
Technical writing about fast-moving tools gets things wrong. What matters is what happens next. This page explains how corrections work on Hamzify.
How to report something#
Email hamzajadoon71@gmail.com with the page URL and what looks wrong. Every article footer has a "Send a correction" link that pre-fills this for you.
You do not need to be polite about it, and you do not need to be certain. A "this looks off" message that turns out to be right is worth more than a wrong claim staying up.
What counts as a correction#
Factual errors — a wrong version number, a misattributed feature, an incorrect price, a broken code sample, a mischaracterisation of what a tool does. These get fixed.
Things that have changed — a tool ships a feature that a review said was missing, or pricing changes. These are updates rather than corrections: the article gets revised and its "Updated" date changes.
Disagreement about a conclusion — genuinely welcome, but a difference of opinion is not an error. If your experience contradicts what is published, that is useful context and may be added to the article with credit.
How corrections are handled#
| Severity | What happens |
|---|---|
| Typo, broken link, formatting | Fixed silently |
| Factual error that does not change the conclusion | Fixed, and a correction note added at the end of the article with the date |
| Factual error that changes the conclusion | Fixed, correction note at the top of the article, and the "Updated" date changed |
| Article is fundamentally wrong | Article is retracted with an explanation left in place at the same URL |
The target is to respond within a few days and to fix confirmed errors as soon as they are verified.
What will not happen#
- Quiet rewriting. A conclusion will not be changed without saying that it changed.
- Deleting the URL. Retracted articles keep their address with an explanation, because breaking a link that people have shared hides the mistake instead of owning it.
- Removing a correction later to make the archive look cleaner.
Public history#
This site is built from files in a public repository, so the full edit history of every article is available and independently checkable. That is deliberate: it makes the corrections process verifiable rather than a promise.
Updates versus corrections#
An "Updated" date means the article was revisited and revised — usually because the tool changed. It does not imply an error was found. Where a substantive claim changed, the note in the article says what and why.