A Reviewer Said to Improve the English of My Paper. Now What?
The comment feels personal and vague at the same time. It is usually one of three specific things, and only one of them is really about grammar. Knowing which you have tells you exactly what to fix.
While you wait
Waiting on a decision? Get your next move ready.
The wait is out of your hands; the next move isn't. Scan your next manuscript free, or run this paper through the scan to see what reviewers typically push back on, so the revision response is ready when the decision lands.
How to use this page well
These pages work best when they behave like tools, not essays. Use the quick structure first, then apply it to the exact journal and manuscript situation.
Question | What to do |
|---|---|
Use this page for | Building a point-by-point response that is easy for reviewers and editors to trust. |
Start with | State the reviewer concern clearly, then pair each response with the exact evidence or revision. |
Common mistake | Sounding defensive or abstract instead of specific about what changed. |
Best next step | Turn the response into a visible checklist or matrix before you finalize the letter. |
Quick answer: A reviewer said to improve the English of my paper, and the first thing to know is that the comment is usually one of three specific things, only one of which is really about grammar. It can be systematic language errors, overloaded sentences that are grammatically fine but hard to follow, or a polite proxy for "I found this hard to follow" where the real problem is structure. Diagnose which one you have before you spend a cent on editing, because the fix is different for each and the wrong fix leaves the comment alive.
The comment stings because it feels personal and reads as vague. It is neither, once you know what triggered it.
Why the comment is worth decoding, not just obeying
The reasoning matters, because it changes what you do next. The instinct after "improve the English" is to hire a language editor, get the grammar cleaned, and resubmit. That works when the problem is grammar. It fails, expensively, when the problem is that your sentences carry three ideas each or your results section has no through-line, because a grammar editor will hand you back polished sentences that the next reviewer still cannot follow. You will have paid for an edit and kept the objection.
There is a real and unfair backdrop here worth naming plainly. A large survey study found that non-native English speakers spend far more time writing and revising, and face higher rejection specifically on language grounds, for science of the same quality. So the burden is genuine, and it is heavier for some authors than others. The practical consequence is not despair, it is precision: because the system asks more of your language, you want to spend that effort on the thing that actually triggered the comment rather than on a generic polish.
The three patterns behind the comment
This is what decoding looks like. In our pre-submission review work with manuscripts, the "improve the English" comment almost always traces to one of three patterns, and each points to a different fix.
The first is the systematic-error pattern. Articles, prepositions, verb tenses, and singular/plural agreement are off in a consistent way, and the errors accumulate until they tax the reader. What we see is that this is the one case where the comment is literally about grammar, and a strong language edit, or a native-fluent colleague, genuinely solves it. If your draft has this pattern, professional editing is money well spent.
The second is the overloaded-sentence pattern. Every sentence is grammatically correct, but each one carries two or three ideas, runs past forty words, and forces the reader to hold too much at once. Reviewers experience this as "bad English" and label it that way, but no grammar edit fixes it. The fix is to cut each long sentence into two or three, one idea apiece, which is something you can do yourself and which helps more than any polish.
The third is the structure-proxy pattern. The sentences are fine and the paragraphs are fine, but the results have no order, the argument doubles back, and the reader cannot find the thread. "Improve the English" is here a polite stand-in for "I got lost." In practice it means the work is reorganization, not language: lead each paragraph with its point, order the results as a narrative, and signpost the logic. A language editor will not catch this, because there is nothing ungrammatical to catch.
Only the first of the three is solved by the fix everyone reaches for first. The other two are solved by work you can largely do yourself, which is the good news buried in an annoying comment.
How do you match the fix to the pattern?
Once you know which pattern you have, the response is straightforward, and the table below pairs each with its fix.
Pattern | What it looks like | The fix that works |
|---|---|---|
Systematic errors | Article, tense, preposition mistakes throughout | Professional language edit or native-fluent colleague |
Overloaded sentences | Correct but 40-plus words, several ideas each | Split sentences yourself, one idea apiece |
Structure proxy | Grammar fine, but the reader gets lost | Reorganize; lead with the point, order the results |
Manusights pre-submission guidance on language-and-clarity comments.
The costly mistake is applying the first row's fix to the second or third row's problem. A grammar edit on a structure problem is the single most common way authors spend money and still get the same comment on resubmission.
How do you tell which one you have?
Run this quick self-check before deciding anything. Read three paragraphs of your paper aloud, and use what trips you up to place the pattern.
Read-aloud symptom | Likely pattern | First move |
|---|---|---|
You stumble on small words and endings | Systematic errors | Language edit or fluent colleague |
Correct, but you lose the thread mid-sentence | Overloaded sentences | Split each into one idea |
Each sentence is clear; the paragraph's point is not | Structure proxy | Reorder; lead with the point |
Manusights read-aloud diagnostic for language-and-clarity comments.
Most papers have some of all three, but one usually dominates, and that is the one the reviewer reacted to.
A second, harder test: give the flagged section to a colleague who was not involved in the work and ask them to tell you back what it says. Where they hesitate or get it wrong is where the reviewer struggled too. This is worth more than any automated grammar score, because it measures the thing the reviewer actually measured, which is whether a reader can follow you.
Readiness check
While you wait, scan your next manuscript.
The scan takes about 1-2 minutes. Use the result to decide whether to revise before the decision comes back.
Responding to the reviewer without hand-waving
When you resubmit, do the work and then say what you did, specifically. A reviewer who flagged the language once will not be reassured by a vague line that you "have improved the English throughout." Name the concrete steps: that you had the manuscript professionally edited, if you did; that you shortened long sentences and split dense paragraphs; that you reorganized the results for a clearer through-line. Specificity signals that you diagnosed the problem rather than waved at it.
Do the work if: the comment names real, recurring errors; multiple readers get lost in the same places; or the section genuinely reads as three ideas per sentence. Fix the pattern you actually have, then document it in the response.
Push back gently if: the language is clean by independent read, the errors the reviewer cites are not actually errors, or the objection is doing work that a structural fix already addressed. Even then, the winning move is usually to tighten the prose anyway so the objection has nowhere to land, and to say calmly in the response why you believe the language now meets the bar.
What we see across manuscripts
Clearing a language comment rarely goes to whoever spent the most on editing. It goes to whoever worked out which of the three patterns they had and fixed that one, be it a grammar edit, a sentence-splitting pass, or a reorganization. Come back to this page when a reviewer flags your English and you are deciding what to actually change before you submit again. The language-cost research we reviewed, including Amano and colleagues, is cited below. If you want the language and structure read before a reviewer sees them, our pre-submission review flags the overloaded sentences and lost threads that a grammar check misses, and if you are also worried the same clean-up could read as machine-written, the companion guide on whether your paper will be flagged as AI-written covers that separate fear.
Your language-fix checklist
Before you resubmit, run this pass:
- Read three flagged paragraphs aloud and note whether you stumble on grammar, on sentence length, or on losing the thread.
- Split every sentence that runs past roughly forty words into two or three, one idea in each.
- Lead each paragraph with its point, then support it, so a reader knows early what the paragraph is for.
- If the real pattern was systematic error, fix the articles, tenses, and prepositions with a language edit or a fluent colleague.
- Ask someone outside the project to read a section back to you, and mark every place they hesitate.
- In your reply to the editor, name the concrete steps you took rather than promising you improved the English.
Match the fix to the pattern you actually have. The most common way to waste money here is a grammar edit on a structure problem.
Frequently asked questions
Usually one of three things, and only one is grammar. Sometimes it is genuine language errors, like article, preposition, and tense mistakes that pile up. Sometimes the grammar is fine but the sentences are overloaded and hard to follow, which reviewers often mislabel as an English problem. And sometimes 'improve the English' is a polite proxy for 'I found this hard to follow,' where the real issue is organization, not language. Diagnosing which one you have tells you exactly what to fix.
Not always, and not blindly. If the problem is systematic grammar errors, a good language edit helps and is worth it. But if the real issue is overloaded sentences or weak structure, an editor who only fixes grammar will hand back a polished version of a paper the next reviewer still finds hard to follow. Diagnose the type of problem first, then decide whether you need a language editor, a restructuring pass, or both.
Sometimes the burden is real and unfair. Research shows non-native English speakers spend substantially more time and face higher rejection on language grounds for the same science. That does not mean every comment is bias, but it does mean the system asks more of you, so the practical response is to make the language and structure clean enough that it stops being a place a reviewer can object, which protects the science underneath.
Do the work, then say what you did specifically. State that you have revised the manuscript for language and clarity, name the concrete steps (a professional edit, a restructuring of the results, shortened sentences), and if a professional service was used, say so. Vague assurances that you 'improved the English' without evidence rarely satisfy a reviewer who already flagged it once.
Often, yes, especially the clarity and structure problems, which are the ones professional grammar editors miss. Shorten long sentences, put one idea in each, lead paragraphs with the point, and read the paper aloud to hear where it stumbles. For systematic grammar errors a native-fluent colleague or a language service is faster and more reliable than self-editing, but the structural fixes are within reach and often matter more.
Sources
- Amano et al., The manifold costs of being a non-native English speaker in science (PLOS Biology, 2023): https://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.3002184
- Committee on Publication Ethics, guidance on peer review and author support: https://publicationethics.org/guidance/guideline/ethical-guidelines-peer-reviewers
- European Association of Science Editors, guidelines on language and clarity: https://ease.org.uk/publications/author-guidelines-authors-and-translators/
Final step
Done interpreting the status? Put the wait to work.
The decision will arrive on the journal's clock. What you control is what's next: scan your next manuscript free, or run this paper through the scan so the likely reviewer pushback is mapped before the revision request lands.
Free scan, no card needed.
Anthropic Privacy Partner. Your manuscript is never used to train any model.