103. Words that work

In a fictional drawing app, the Eraser deletes selected objects. Here are two descriptions of that same operation:

The Eraser provides the ability to perform the removal of selected objects.

The Eraser deletes selected objects.

The first sentence gives the action several layers of packaging. The second gives it a verb.

Word choice begins with that kind of attention: what happens, who does it and what changes? Once those relationships are accurate, you can choose a sentence with some life in it. A vivid wrong verb is still wrong, only more memorable.

Choose the event before the verb

Start with the product behavior. Does the command delete, hide, detach or exclude the object? Does it perform an operation or make the operation available? Does it finish now or queue work for later?

These distinctions matter more than the force of the word. A thesaurus can make remove more dramatic; it cannot tell you whether the original file survives.

Fictional fact packet: a command removes a drawing from the current preview while retaining the source file.

Too broad: Delete the drawing.

Accurate: Remove the drawing from the preview. The source file stays in its folder.

The extra sentence earns its space by protecting the scope. A shorter instruction that implies permanent deletion would be a worse edit.

Use the domain's ordinary verbs when they identify the real operation. In type design, kern, interpolate and hint may be more precise than a longer generic phrase. Explain an unfamiliar term where the reader needs it. Keep familiar verbs when they already do the job; is, has and uses are not failures of imagination.

Release a buried action carefully

An action noun can conceal a direct verb:

Heavy: The application performs a comparison of the two proofs.

Direct: The application compares the two proofs.

This fictional pair preserves the actor and operation. The noun comparison had become unnecessary machinery around compares.

Now consider a different fact packet: configuring a profile makes synchronization available, but does not start it.

Original: Configuring the profile enables synchronization.

False repair: The profile synchronizes your files.

Useful explanation: Configure the profile to enable synchronization. This does not start a sync.

The false repair is active, concise and inaccurate. It invents both an actor and a completed operation. Keep enables when enabling is what happens.

Review weak verb-and-noun combinations such as performs a verification or makes a selection. Replace them when the direct verb preserves the contract. Keep an action noun when the action itself is the topic: “The comparison takes place after import” may be exactly the relationship you need to explain.

A search for noun endings can locate candidates. Read the whole sentence before changing them.

Find the noun the reader can recognize

A strong verb needs a clear object. Feature, functionality, item, solution and process may hide the thing the reader must find.

Fictional example: a Tokens list contains expired access tokens, and the action deletes the selected token.

Vague: Remove the item.

Specific: Delete the expired token from the Tokens list.

The revision is useful because the packet establishes both the object and the action. Do not add a control name merely to make an invented example resemble a real interface.

Pronouns save space when the referent is clear. When several files, folders or applications compete for it, repeat the relevant noun.

Save the file in the project folder, then upload the file.

The repeated noun resolves a possible ambiguity. Elsewhere, “upload it” may be perfectly clear. Inspect the actual context rather than declaring pronouns unfit for technical work.

Concrete nouns can also carry voice. A proof with one dark join is easier to picture than an “inconsistent visual outcome.” The detail should explain the subject; an unrelated coffee cup merely decorates the desk.

Keep one name for one thing

A reader following instructions uses names as landmarks. If the draft calls the same control a dialog, an output window and a save pane, the reader has reason to look for three objects.

Introduce the exact label, then use a short form that remains unambiguous. Repeat the full name when another similar object enters the passage. Keep spelling, case and meaningful punctuation intact.

Put sentence variety around the technical name. You can change the length, order and emphasis of the sentence without renaming the control.

A term can have different meanings in different applications. Name the application when context does not settle which meaning applies. Use the product register and glossary for naming scope and status.

Record important naming decisions where the team can find them: exact name, meaning, permitted short form, obsolete variants, source and review trigger. A renamed feature may affect search wording, screenshots, examples and translations as well as prose.

Bridge the reader's words and the interface

The reader may search for account photo while the interface calls the section Profile. Keep both vocabularies visible in a bridge sentence.

In this fictional interface, Profile contains an Upload photo command:

To change your account photo, open Profile and choose Upload photo.

The opening names the task. The labels locate the actions. Later steps can use the established terms without cycling through avatar, user image and profile picture for variety.

Reference pages may need the reverse order. Someone looking up workspaceId wants that identifier first, followed by its meaning and contract. Preserve a literal identifier even when a different word would sound smoother.

Explain jargon at the point where it becomes necessary. A short gloss may be enough; a difficult distinction may need an example. Do not make every definition fit one clause or repeat it mechanically. A later section reached directly from search may need its own brief context.

Remove reassurance that claims too much

Simply, just and easily often express the writer's familiarity with a task. They do not establish the reader's experience.

Unhelpful reassurance: Simply choose the destination and easily export your proof.

Instruction: Choose the destination, then export the proof.

The instruction retains the sequence without predicting how it will feel. If a step has a prerequisite, explain that prerequisite instead of reassuring the reader past it.

Adverbs are useful when they carry a real distinction: automatically, temporarily and recursively can change the operation. Preserve them when supported. Replacing every adverb with a louder verb can make the meaning less exact.

Treat intensifiers similarly. Ask what very or extremely contributes in context. In a quotation, preserve it. In a factual product claim, evidence usually serves the reader better. In a supplied personal voice, an emphatic habit may be worth retaining.

Replace praise with what is known

When you encounter powerful, ask which operation supports the claim. When you encounter seamless, ask which interruption has actually been removed. These questions direct research; they do not authorize you to invent the answers.

Fictional fact packet: an export preset stores a format and destination. No timing or user-study evidence is available.

Unsupported: Presets make export effortless.

Supported: A preset stores the format and destination for an export.

If the packet also establishes that applying the preset restores those settings, the explanation can say so. Without that fact, the attractive follow-up “Choose the preset and both settings are restored” is premature.

Do not repair an unsupported endorsement by reducing its number. “Trusted by thousands of teams” does not become evidenced when edited to “Trusted by teams.” Find a source or remove the endorsement.

A plain factual sentence can have its own confidence. It tells the reader enough to make a judgment without trying to make the judgment for them.

Give numbers their conditions

A number can clarify a claim or disguise an unsupported one. Check what was measured, in which environment, against what baseline and with what variability.

Fictional measurement: one sample import of 10,000 rows finished in 42 seconds on the recorded test machine.

Too strong: Import 10,000 rows in 42 seconds.

Bounded: In this test, importing the 10,000-row sample took 42 seconds.

The second version describes an observation. Attach the relevant version, hardware and data conditions in the published report. Repeat the test if a broader performance claim requires it; editing cannot supply repeatability.

Retain raw counts when they help interpret a percentage. A rise from 4% to 6% is an increase of 2 percentage points and a relative increase of 50%. Those descriptions answer different questions. Choose the one the reader needs, and give the starting values when scale matters.

Use appropriate precision. An exact setting needs its exact value. A changing population estimate may need an approximate count and date. Avoid adding decimal places to make uncertainty look measured.

A comparison can help a reader grasp scale. Verify the arithmetic and keep the original unit nearby. Never trade a setting or compatibility limit for a memorable image.

Keep the small words that hold the contract

Before cutting a short word, ask what relationship it establishes.

Word or distinction	Check
Can	Is this an available capability or choice?
Might or may	Is the result uncertain, or does the sentence mean permission?
Must	Does evidence establish a requirement?
Should	Is this a recommendation, an expectation or an obligation that needs clearer wording?
If	Is the action or outcome conditional?
When	Does the sentence identify an event or expected timing?
While	Does the state hold during an interval?
Because	Is the cause established?
Before and after	Is the order correct?
Only, all and some	Does the scope match the evidence?

Use since and as when their meaning is clear; replace them when time and cause could be confused. Keep restrictive and supplementary clauses distinct through wording and punctuation. The aim is an unambiguous relationship, not a mechanical preference for one relative pronoun in every context.

Keep the articles and connecting words that make a sentence parse naturally. A shorter noun stack is not necessarily a clearer phrase. “The file that the application created” may spare the reader a second attempt at the sentence.

Choose words for sound after meaning

Read a paragraph aloud once its claims are stable. Listen for repeated abstract endings, an accidental tongue-twister or a series of verbs that all seem to hover above the action.

Try replacing an abstraction with its relevant object. Try moving the consequential word closer to the end. Let a plain verb carry a complex thought before adding an adjective.

Fictional example: a review note says that the filenames are so similar that the designer must open each proof to identify it.

Abstract: File identification introduces additional procedural overhead.

Observed: To identify the proof, she has to open it. The filename offers little assistance.

The final phrase understates an inconvenience already established by the example. It works in an explanatory essay. In a recovery instruction, “Open the proof to identify it” may be enough.

Do not force every paragraph to finish with a dry remark. The effect depends on the surrounding prose doing useful work without asking for applause.

Keep a word list that explains its decisions

A house word list should help someone make a decision under deadline. Record the preferred wording, the troublesome alternative, the reason and an example. Include exact labels and naming scope as well as stylistic preferences.

Distinguish protected terminology from words that merely deserve review. An obsolete product name in new copy may be a clear error. Robust in a quotation is protected wording. Robust in an unsupported product claim needs a factual repair.

Update the list when the product changes or repeated edits reveal a real problem. Keep the source or owner of important naming decisions and a reason to revisit them. A list without reasons eventually becomes a collection of things someone once disliked.

Automated searches can locate likely trouble. They cannot determine factual scope, reader need or authorship. A finding needs a decision in context.

Practice: edit without changing the operation

Use this fictional packet:

• Creating a profile enables synchronization.
• Synchronization starts only after a separate command.
• The source files remain in their original folders.
• No speed measurement is available.

Draft to edit:

Creating a profile instantly syncs all your files, giving you effortless access everywhere.

First, mark the unsupported claims. Instantly, all, effortless and everywhere each outrun the packet; syncs changes an enabled state into an operation.

A supported revision is:

Create a profile to enable synchronization. Start synchronization with the separate command. The source files remain in their original folders.

The command still needs its verified name before this becomes a usable procedure. In a working draft, mark that gap with [CONFIRM LABEL]. Do not guess a label to make the example look finished.

For a second pass, revise the explanation around the distinction between enabling and starting. Keep the exact operation and source-file condition. Read both versions aloud, then compare their claims word by word. The more fluent version wins only if it remains equally accurate.

Now try a packet that establishes only that the profile stores settings. Neither enables synchronization nor starts synchronization is available. This checks whether the repair came from the evidence or from a familiar sentence remembered from the previous example.

Checklist

• Verbs name the supported operation, including the difference between enabling and doing.
• Nouns identify the object and its relevant scope.
• Exact labels and terms stay consistent; short forms remain unambiguous.
• Reader vocabulary is connected to interface vocabulary where needed.
• Reassurance, intensifiers and praise have been examined in context.
• Numbers preserve their units, conditions and degree of certainty.
• Conditions, negation and timing survive the edit.
• An expressive detail clarifies the subject without inventing evidence.
• Search findings have been reviewed rather than treated as automatic failures.
• The final wording helps the reader find, decide, act or understand.