Writva
Guide

How to edit one passage with AI and keep the rest intact

The short version: select the smallest passage that contains the whole problem, describe what is actually wrong with it, read the result against the text around it, and accept it only once you are sure it still says what you meant.

When a targeted edit is the right tool

Targeted editing suits a draft that mostly works. The argument is sound, the structure holds, and a handful of passages are letting it down — a sentence that buries its point, a transition that lurches, a paragraph that repeats what you already said.

It is the wrong tool when the underlying thinking is unresolved. If you do not yet know what a section is arguing, polishing its sentences will produce fluent prose that is still wrong. Fix the thinking first, then edit the words.

Choose the right scope

Most disappointing AI edits are scope problems, not model problems.

Sentence level

One sentence is awkward, overlong, or buries its point. Select that sentence. This is the safest scope: you can check the result in seconds.

Paragraph level

The individual sentences are fine but the paragraph circles, or its point arrives too late. Select the paragraph — the fix needs to see all of it.

Multi-paragraph, structural

Two sections overlap, or an idea is introduced twice. This is usually a structural decision, not a wording one. Decide what should go where yourself, then use targeted edits to smooth the seams.

Selection too narrow

You select half a sentence, so the fix cannot see the clause that caused the problem. The result reads oddly against the words on either side.

Selection too broad

You select three paragraphs to fix one line. Now you have to re-read all three to find what changed — the exact problem targeted editing was supposed to avoid.

Describe the problem, not the wish

“Make this better” is not an instruction — it is a hope. It gives the model no information about what is wrong, so it applies generic improvements: smoother rhythm, more conventional vocabulary, fewer risks. That is how drafts get flattened.

Vague

“Improve this paragraph.”

“Make it flow better.”

“Make it more professional.”

Specific

“The main claim is at the end. Move it to the first sentence.”

“Cut this to two sentences without losing the qualification.”

“This repeats the previous paragraph. Keep only what is new.”

A worked example

A paragraph from a hypothetical article about remote work. Only the second sentence is selected.

The draft

The team moved to a four-day week in March. It is worth noting that the productivity data which was collected over the following six months did not show the decline that had been anticipated by several of the managers. By September, two other departments had asked to run the same trial.

The selected sentence is the second one.

The instruction

“This sentence is too long and starts with filler. Lead with the finding and keep it under twenty-five words.”

A possible revision

The team moved to a four-day week in March. Six months of productivity data showed none of the decline several managers had expected. By September, two other departments had asked to run the same trial.

What to check before accepting

The meaning survived: managers expected a decline, and it did not appear. “Six months” is still there, so no fact was quietly dropped. The sentence still leads into the September result. If the revision had said the data showed an increase, that would be a new claim your draft never made — and the kind of thing only you can catch.

Illustrative, not a guaranteed output. The point is the review, not the wording.

Review before you accept

  1. Check the meaningDoes it still say what you meant? A clearer sentence that says something slightly different is a loss, not a gain.
  2. Check the factsNumbers, dates, names and qualifiers are exactly where edits go wrong. AI does not know which details are load-bearing.
  3. Check the seamsRead the sentence before and after. A revision can be excellent in isolation and wrong in place.
  4. Check the voiceIf the passage no longer sounds like the rest of the piece, keep the improvement and restore your own phrasing.
  5. Accept deliberatelyAccepting should be a decision you make, not the default that happens while you are reading.

Common mistakes

Editing before the thinking is settled

Polishing a paragraph whose argument you have not decided produces a well-written placeholder.

Accepting because it sounds smoother

Smoothness is easy to produce and easy to mistake for quality. Ask whether it is clearer, not whether it is smoother.

Chaining edits without re-reading

Five accepted revisions in a row can drift a long way from where you started. Re-read the whole section periodically.

Trusting it with facts

A revision can introduce a confident claim your source never made. Verification is always yours.

Before you accept: a checklist

Run through this each time

  • Did I select the complete thought — no more, no less?
  • Did I describe the actual problem instead of asking for quality?
  • Does the revision still mean what I meant?
  • Did any fact, number, name or qualifier change?
  • Does it still connect to the sentences around it?
  • Does it still sound like the rest of the piece?
  • Am I accepting this deliberately, or just because it is there?

How Writva supports this

Writva keeps two copies of your work: the Stable Version, which is the draft of record, and the Edited Version, where a proposed change appears. A revision never overwrites the Stable Version on its own — it sits beside it until you Promote it, and the previous version stays in your history either way.

That structure exists to make the review step above unavoidable rather than optional. The selected-text editing feature page covers how it works in the product.

Questions about targeted editing

How much text should I select at once?

Select the smallest span that contains the whole problem. If the issue is one clumsy clause, select the sentence. If two sentences contradict each other, select both — a fix that can only see one of them cannot resolve the contradiction.

What makes an instruction useful?

Name the problem rather than asking for quality. “Make this better” gives the model no information; “this sentence buries the main claim at the end” tells it what to fix and lets you check whether it did.

Should I accept a revision that is only partly right?

Take the part that helped and rewrite the rest yourself. Partial acceptance is normal and usually faster than requesting another full attempt.

Do I need Writva to work this way?

No. The method — narrow the scope, describe the problem, review against the surrounding text, accept deliberately — applies in any tool. Writva is built to make that loop the default rather than something you have to impose.

Try the method on a draft you already have

The workflow is the same whether you are fixing one sentence or working through a chapter.

Related