A correction that names the span it applies to is the one that lands

A complaint is not an instruction
Make it punchier. Less corporate. Too long. Something is off in the middle. These are the corrections people actually type, and each of them states a feeling about the whole rather than an operation on a part. What comes back is a full rewrite in which the objectionable thing may or may not have changed and several things you liked have quietly gone.
The mechanism is straightforward enough. An unlocated instruction gives no basis for leaving anything alone, so everything is in scope, and the parts you were happy with were only ever safe by accident.
The result is the familiar experience of the third revision being worse than the first while nobody did anything wrong. You asked for a change to a document and got a different document.
Locate it, name the property, state the target
A correction that works has three parts. Where: quote the sentence or name the section, rather than describing it. What is wrong with it: not that you dislike it but which property is off — it repeats the previous paragraph, it asserts something you cannot support, it uses a term the reader will not know. What it should be instead: the target state, in terms someone could check.
Compare two versions of the same complaint. The second paragraph of the opening section explains the background twice, so cut it to one explanation and keep the example about the delayed shipment. That is an operation. Make the opening tighter is a mood.
The quoted span matters more than the rest. Once the text to be changed is identified explicitly, everything outside it has a reason to survive, and you can see whether it did.
Say what must survive the change
The half of a correction people never write is the preservation clause. Keep the structure, keep the third paragraph exactly as it is, do not change the terminology, retain the opening line. It feels redundant to say and it is the difference between a targeted repair and a fresh attempt.
This is worth being unusually explicit about when the piece is nearly finished, because at that point most of the value is in what already works. Late in a draft the instruction is mostly protective: here is a small thing to fix, and here is the long list of things that must come back unchanged.
A useful habit is to ask for the changed passage on its own rather than the whole document reissued. You then paste it in yourself, and nothing else can move, which removes the problem rather than mitigating it.
One correction at a time, for a reason
Bundling five fixes into one message produces a result where some are applied fully, some partially, and one is missed, and you cannot tell which without a line-by-line comparison that costs more than the fixes did. Interactions between the fixes make this worse: a shortening instruction and an add-detail instruction pull against each other and the resolution is never announced.
Separate passes are slower per exchange and faster overall, because each result is verifiable at a glance. Apply, check, then apply the next. The discipline resembles ordinary editing, where nobody would attempt five structural changes in a single sweep either.
Where the fixes are genuinely mechanical and independent — a terminology substitution, a date format, a heading style — bundling is fine, and the reason it is fine is that each one can be checked by search rather than by reading.
When the correction is really an objection to the whole thing
Some dissatisfactions cannot be located because they are not local. If your honest description of the problem is that the piece argues the wrong thing, or that it is organised around a distinction you no longer believe in, no span will contain it, and the well-formed correction you are trying to write does not exist.
That is a signal about the draft rather than about your phrasing, and it is a different situation from the one this technique addresses. The response there is to go back to what the piece is for, which is a decision about restarting rather than about revising.
The test is quick. Try to write the correction as a where, a what and a target. If you cannot name the where after a minute of trying, the problem is upstream of the wording, and further instructions will keep producing documents that are wrong in a new way each time.
Common questions
Why does a general instruction change things you did not mention?
Because nothing in it identifies what to leave alone, so the entire text is in scope. Naming the span gives everything outside it a reason to remain, and asking for only the changed passage removes the possibility of collateral edits altogether.
Should several corrections be sent together?
Only when they are mechanical and independently checkable, such as a terminology change or a date format. Substantive fixes interact, get partially applied, and leave you comparing documents line by line, which costs more than separate passes would have.
What if you cannot say where the problem is?
Then it is probably structural rather than local, and no phrasing of the correction will reach it. Trying and failing to write the where is a useful test: it tells you the draft needs reconsidering rather than editing.
Editor, Prompt After Prompt
Bhavna covers prompt craft, writing with ai, images & audio and the questions readers actually send in and thinks most subjects are more interesting once you know how they work.