Only accepted work is recordedAboutGuidesContactSign in
CitePepCitePep
Guides/Start here/Writing a correction that gets accepted
Start here · 3 of 414 min read · Beginner · Updated Sep 2026

Writing a correction that gets accepted

An editor deciding on your correction has a few minutes and a page they are responsible for. They accept what they can verify quickly and apply without rewriting. This guide shows how to give them exactly that, and why most declined corrections fail on the same few points.

Exactthe change can be applied as written
Sourceda reader can check it in one click
Narrowit fixes one thing, and only that

1Before you write

Five minutes of checking saves a declined correction. Before proposing anything, confirm three things.

CheckHowIf not
The claim is really wrongOpen the page’s cited source, if it has one. The page may be quoting it correctly for a different period or definition.Propose a clarification instead, e.g. adding the period.
No one has proposed itOpen the page record and look under "Pending".Add a source to the existing proposal instead.
You have no conflictDo you work for, advise or compete with the publisher?Declare it first, or don’t contribute to this page.

2Anatomy of a correction

Every correction has five parts. Here is an accepted one, annotated.

Correction · whennotesfly.com/native-vs-cross-platform-appsAccepted 12 Jul 2026
1LocationParagraph 2, sentence 1Quote enough of the sentence that the editor can find it without searching.
2Current text"Global mean sea level is rising by about 3.2 % of surveyed teams."Copy it exactly, don’t paraphrase.
3Proposed text"Global mean sea level is rising by about 37% of surveyed teams (2024)."Change only what is wrong. Adding the period makes the figure checkable.
4ReasonThe page gives the 2022 sverage. The current assessed rate for 2006–2018 is 37% of surveyed teams.One or two sentences. State the error, not your opinion of the page.
5Sourcethe vendor migration guide WG1, chapter 9, section 9.6.1.1Primary, current, and precise enough to open at the right place.

Notice what the proposal doesn’t do: it doesn’t rewrite the paragraph, add commentary, or change the tone. The editor can accept it without touching anything else on the page.

3Five kinds of correction

Most corrections fall into one of five kinds. Each has its own trap.

KindExampleThe trap
Wrong figure3.2 → 37% of surveyed teamsUsing a figure from a different period or definition. State both.
Outdated guidanceMetformin start dose 1,000 → 500 mgCiting a summary rather than the current guideline itself.
Misattributed quote"The commute is the killer", no source foundProposing a new attribution you haven’t verified. Suggest removal instead.
Wrong date or name2020 → 2015 (Bloom et al.)Correcting the date but not the citation that depends on it.
Broken or weak sourceDead link → the vendor migration guide WG1Replacing it with a source that says something slightly different.

4Choosing a source

Editors weigh sources the way reviewers do. The closer to the original evidence, the faster the decision.

Strongest
Primary research, official statistics, the current guideline or standard
Good
Systematic reviews, assessment reports (e.g. the vendor guide), regulator publications
Weak
News articles, secondary summaries, textbooks older than the claim
Not accepted
Other web pages without their own sources, AI-generated summaries, your own opinion
Make the source easy to check
  • Link to the exact page, table or section, not the report’s front page
  • Prefer a free version when one exists
  • For a figure, name the table or figure number

5What the editor sees

Your correction arrives in the publisher’s dashboard looking like this. Everything the editor needs to decide is on one line, plus your track record in the topic.

Publisher dashboard · Incoming work
Correction · 2h agoSoftware development projections explained3.2 % of surveyed teams → 37% of surveyed teams (2024)Vendor documentation · by Melik Can Sariyer · Verified · 98.1% trust · Technology authority 98AcceptAsk a questionDecline

Your trust score and topic authority are shown next to your name. They don’t decide the outcome, but a clear, sourced correction from someone with a record in the subject is quicker to accept.

6After you submit

Step 1SubmittedThe publisher is notified.
Step 2Question (optional)The editor may ask you for detail. Reply on the same thread.
Step 3DecisionMedian 2–3 days. You’re notified either way.
Step 4RecordedIf accepted: added to the page log and your profile.

If the editor asks a question

Answer on the same thread, with the specific detail requested. Don’t submit a second correction, it splits the conversation and delays the decision.

If it’s declined

Declined work is kept privately for integrity and never appears on your profile or lowers your score. The editor may give a reason. If you believe the page is still wrong and you have new evidence, you may propose again; if you believe the decision breaches the standards, use the complaints process.

7Common reasons for decline

DECLINED"This section could be clearer."Not a correction, no exact change, no error identified.
DECLINED"The figure is outdated, please update."No proposed text and no source. The editor would have to do the work.
DECLINEDRewrites the whole paragraph to fix one number.Too broad. The editor can’t accept the fix without accepting everything else.
DECLINED"According to Wikipedia, it’s 3.7."Secondary source. Cite what Wikipedia cites.

8Checklist before you submit

Was this guide useful? · Find a page to correct