Instructions go out of date. Interfaces get renamed, features get removed, and sometimes we simply get something wrong. What matters is whether a publication fixes it openly or quietly pretends it never happened. This page sets out how Tutorils handles that.
Report an error
Send the URL of the page and the specific problem through the Contact page or to contact@tutorils.com.
Useful reports name the thing that is wrong: "Step 4 says Settings › General, but on iOS 19 it is Settings › Privacy." That gets fixed the same week. "This article is wrong" cannot be acted on, and we will have to write back to ask what you meant.
Things worth reporting:
- A factual claim that is incorrect
- A step that no longer matches the current interface
- A screenshot showing a version that no longer exists
- A broken, redirected, or wrong outbound link
- An image with a misleading caption or alt text
- A missing or inadequate commercial disclosure
- A safety or privacy caveat we should have included and did not
You do not need to be certain. If something looks wrong, tell us and we will check it.
How we assess a report
Every report is checked against evidence rather than taken on trust — and rather than dismissed on trust either. We go back to primary sources: official documentation, vendor release notes, the software itself where we can run it.
Three outcomes are possible:
Confirmed. The claim is wrong, or the steps no longer work. We correct it.
Not reproducible. We cannot make the problem appear. Often the honest explanation is that behaviour differs by version, region, carrier, device, or account tier. In that case the fix is usually not to change the instruction but to state the condition — so the next reader knows why their screen looks different.
Correct as published. Sometimes the original stands. We will say so and explain why, rather than editing an accurate article to end an argument.
How we correct things
Material errors — anything that changes what a reader should do or conclude — are corrected promptly, and we add a visible note to the article stating what was wrong and what changed. We do not delete the fact that we got it wrong.
Minor fixes — typos, punctuation, formatting, a dead link swapped for its current destination — are made without a separate notice. Logging every comma would bury the corrections that matter.
Routine updates are different from corrections. When software changes and we refresh a guide to match, that is maintenance, not an admission of error, and it is reflected in the article's updated date rather than in a correction note.
Withdrawal is reserved for the rare case where an article cannot be salvaged — where the premise itself was wrong, or where following it could cause harm. We say that the piece was withdrawn and why, rather than making the URL disappear.
What we will not do
We will not silently reverse a conclusion. If a recommendation changes, the article says it changed and why. Editing history to look consistently right is dishonest.
We will not remove accurate material because someone objects. A vendor who dislikes a documented limitation, or an advertiser who dislikes a comparison, does not get an edit. Commercial relationships do not reach editorial judgement — see the Advertising Policy.
We will not update an article purely to game its ranking or affiliate performance. Changing a date, shuffling paragraphs, or swapping a recommendation to a better-paying product without a genuine editorial reason is not maintenance.
We will not fabricate a review. If nobody checked a claim, we do not describe it as verified.
Legal, privacy, and safety requests
Copyright and takedown requests are handled under the DMCA Policy. Personal-data requests fall under the GDPR Privacy Policy. Requests to remove personal information for safety reasons are reviewed individually and treated seriously; we will not publish somebody's private details, and we will act on a credible report that we have.
These requests are assessed on their merits, not on how forcefully they are made.
If we get it wrong twice
If you report an error and we decline to change it, and you still believe we are wrong, write back and say so. Include what you think the evidence is. A second look by a person who has not already formed a view costs us very little and is worth the correction when we have made a mistake.
Escalating
Editorial questions, disputed corrections, and concerns about how a report was handled all go to contact@tutorils.com. Accountability for what appears on this site sits with the editor named on the Authors and Reviewers page — there is a person at the end of that address, not a queue.