Darlo Technical Writing

Editing for clarity

$149 · enrolled · 16 min
A short video walkthrough accompanies this lesson. The full written lesson is below.

Writing is rewriting. The first draft’s only job is to get the facts down; editing is where those facts become usable. This is the highest-leverage skill in the entire craft — and, conveniently, the one that most improves AI-drafted text, which tends to be verbose, hedged, and generically fluent. If you learn one thing from this course that pays back daily, make it editing.

Most people conflate writing and editing and try to do both at once, which does neither well. Separate them: draft fast and loose to capture the content, then switch hats and edit ruthlessly to serve the reader. The draft is for you; the edit is for them.

The editing pass, in order

  • Cut what doesn’t earn its place. Read each sentence and ask ‘what does the reader do with this?’ If the answer is nothing, delete it. A good pass often removes a quarter of the words with no loss of meaning.
  • Prefer the active voice. ‘The server validates the token’ beats ‘the token is validated’ — it’s shorter and names who acts, which readers need.
  • Front-load. Put the most important information first — in the sentence, the paragraph, and the page. Readers scan; reward the scan instead of burying the point in paragraph three.
  • Make it scannable. Break walls of text into steps, tables, and short paragraphs, with informative headings a reader can navigate by eye.
  • Prefer concrete over abstract. Replace ‘utilise the appropriate configuration’ with ‘set timeout to 30’.

Tighten: ‘It should be noted that in order to authenticate, it is necessary for the user to first obtain an API key, which can be obtained from the settings page.’

A strong edit: ‘To authenticate, get an API key from Settings.’ Twenty-eight words become nine, the passive voice and throat-clearing are gone, and it’s clearer. That ratio is typical — and it’s exactly the kind of bloat AI drafts produce by default.

Consistency of terms

Pick one word for each concept and use it everywhere. If it’s a ‘project’, never also call it a ‘workspace’; if users ‘sign in’, they never ‘log in’ on another page. Inconsistent terminology makes readers stop and wonder whether two words mean two different things — a tiny tax paid on every page. This is exactly what a style guide, enforced by a linter, exists to prevent.

Run each paragraph through one question: ‘so what does the reader do with this?’ A paragraph explaining the history of your auth system on a how-to page fails the test — cut it or move it to an explanation page. A paragraph telling them which header to set passes. Applied honestly across a page, this test alone produces most of the improvement a professional editor would.

In the age of AI

Editing is where you add the most value on top of a machine draft, because AI produces fluent, plausible, and almost always bloated prose. Your edit makes it tight, concrete, correct, and consistent with your voice. The workflow that works in practice: let AI draft, then edit ruthlessly — never ship the raw generation. The model gives you clay; editing is where it becomes something worth a reader’s time. Ruthlessness here is kindness to the reader.

Answer, then press Check. Explanations appear after.

Choose oneA strong editing pass typically…

Select allWhich are editing-for-clarity moves? (Select all that apply.)

This lesson is part of Technical Writing Pro

Enrol to unlock all 12 lessons — $149.