104. Sentences and paragraphs

A sentence can ask the reader to carry several things at once: the subject, a condition, an exception and the hope that a verb will eventually arrive. Sometimes the load is necessary. Often you can move the exception.

Write in the order that lets the thought unfold. Keep a condition beside its consequence, give new information a clear connection to what came before and use the pause at the end of a sentence deliberately. Then build paragraphs that take the reader somewhere.

Put the reader on firm ground

Begin with something the reader can identify: an actor, a known object, a relevant condition or the subject already under discussion. Reach the main action before intervening detail becomes difficult to hold.

Fictional example: an exporter checks the folder, filenames and free space before writing files.

Delayed: The exporter, after checking the folder, filenames and free space, writes the files.

Sequential: The exporter checks the folder, filenames and free space. Then it writes the files.

Both versions are grammatical. The second makes the sequence easier to inspect. Keep the first if the surrounding paragraph needs to emphasize the exporter and the interruption remains easy to follow.

A fixed rule about the first seven words would miss the point. Some sentences need a substantial opening condition. Others can reach the verb immediately. Read for the relationship the reader must retain, not a count.

Put prerequisites before actions. “Choose Export if the destination is correct” invites the reader toward the command before establishing whether to use it. “If the destination is correct, choose Export” presents the decision in time.

Hand new information to the next sentence

A sentence often works well when it starts from familiar material and ends with the detail the next sentence will develop.

Fictional example: a package includes a manifest listing its files.

The package includes a manifest: a list of the files it needs. The manifest lets you compare the expected files with the files present.

The repeated noun gives the reader continuity. Introducing a new subject merely to avoid the repetition could break that connection.

This movement can carry a whole paragraph. An observation gains a name; the named thing gains an explanation; the explanation makes a choice possible. Each sentence adds something, and each arrives from somewhere.

Do not force the pattern where it becomes stiff. A clear pronoun can continue the subject. A question can identify a real uncertainty. A short sentence can interrupt the sequence when the interruption itself helps the reader understand.

Let a sentence arrive

The final phrase receives the pause that follows it. Give that position useful work: a result, a distinction or a detail that changes the reader's understanding.

Fictional scene: a designer keeps opening similarly named proofs to find the version with a corrected join.

She checks the dates, opens the two files and enlarges the same letter in each. The difference is in the join.

The longer sentence develops the search. The short one locates the answer. The variation follows the thought; it is not a recipe for alternating long and short sentences throughout a document.

A dry observation can occupy the final position when the material supports it. Keep the joke smaller than the point it illuminates. If the paragraph needs another sentence explaining why the observation was amusing, revise or remove it.

Never delay a warning, price or eligibility condition for a stronger ending. Those facts belong before the decision they govern. The reader's opportunity to act outranks the sentence's opportunity to perform.

Choose active and passive for the subject

Use active voice when responsibility or sequence matters.

The application checks the file before export.

Keep passive voice when the receiver is the subject, the actor is unknown or naming the actor adds no useful information.

The file was created in an earlier version.

The passive sentence does not need an invented creator. It describes the fact that matters.

Within a paragraph about a particular object, passive voice can keep attention on that object while introducing what happens to it. Varying the grammar may also relieve a repetitive run, provided the relationship remains clear.

Do not use passive voice to hide a known responsibility that the reader needs. If the application failed to save, say so. If the evidence establishes only that the save did not complete, preserve that narrower account.

Keep the connecting words

Articles, relative pronouns and repeated prepositions can prevent a false start. Keep them when they make the structure easier to parse.

Compressed: Confirm the folder you selected contains the proof.

Clearer: Confirm that the folder you selected contains the proof.

The added that signals the clause the reader is about to encounter. It is doing work.

Place only where its scope is clear. Compare “Only this preset changes the folder” with “This preset changes only the folder.” One limits the presets; the other limits the affected settings.

Repeat a noun after this or these when several referents compete. Keep the pronoun alone when the antecedent is obvious. A blanket ban would make many ordinary sentences needlessly heavy.

Give introductory phrases a clear subject. In a fictional importer that ignores subfolders:

Unclear actor: When importing a folder, subfolders are ignored.

Clear actor: When you import a folder, the application ignores its subfolders.

Unpack a dense noun phrase when its relationships are uncertain. “The quality setting for exports from the default project” may be longer than a stack of modifiers, but it tells the reader what modifies what. Use hyphens where conventional and helpful; rewriting is often clearer than adding more punctuation.

Cut effort, not just words

Remove a phrase when the meaning survives: in order to often becomes to; due to the fact that often becomes because. Preserve words that carry conditions, timing, uncertainty or scope.

Splitting can reduce effort without reducing length. Joining can keep a relationship intact. Ask which version a reader can follow without reconstructing the intended logic.

Before accepting a concise revision, compare its claims with the source. “Can export” and “exports” may differ in context. “May fail” and “fails” certainly can. A direct style is no reason to turn possibility into certainty.

Stop when the sentence is accurate, clear and suited to the task. Replacing good words with different good words can absorb an afternoon without improving the page.

Make punctuation show the relationship

Use a period when the reader needs a clear boundary. A run-on sentence does not become connected thought simply because its clauses share a comma.

A colon can introduce the detail the first part prepares the reader to receive:

The comparison needs one more input: the revised proof.

Avoid inserting a colon between a verb and its ordinary object:

The comparison needs the revised proof.

Parentheses hold a useful secondary detail. If the parenthesis contains the required action, move that action into the main sentence. A short aside can give explanatory prose a conversational turn, but the reader should be able to resume the main clause without searching for it.

A semicolon can connect closely related complete clauses. A period is often easier in instructions. Choose by the relationship and reading context.

Use a spaced dash for a purposeful interruption or turn. Prefer a colon for an explanation. If the page repeatedly interrupts itself, revise its order before adjusting the marks.

Preserve exact punctuation in code, quotations and interface labels. Quotation marks identify quoted language; they should not make an ordinary word seem important. Use the destination's label formatting from mechanics.

A slash must not hide an unresolved choice. Write “A or B, or both” when that is the logic. Keep literal slashes in paths and identifiers.

Build a paragraph around a change in understanding

A paragraph can define, explain, compare, demonstrate, qualify or direct. Its sentences should contribute to that movement.

The point often belongs near the start in task and reference writing. In an explanatory passage, an observation can come first and lead to the point. The reader should still know what they are looking at and why it matters.

Fictional example: an app reports links to source images; an existing link can point to a file that is currently unavailable.

The link is still listed, but the image does not appear. A stored path and an available file are different things: the application can retain the first while being unable to open the second. Check the file at the reported path.

The paragraph begins with a visible puzzle, explains the distinction and arrives at a check. Moving the final action to the opening might suit a quick recovery note. Keeping the explanation's discovery suits a concept page.

One paragraph need not perform only one tiny operation. A definition and its example can belong together. Split when the topic or reader's task changes, when a condition becomes hard to locate or when a new paragraph would make the relationship clearer.

Read the first sentence of each paragraph as a diagnostic. A sequence of vague introductions suggests buried points. An essay whose opening sentences develop a visible puzzle may be working exactly as intended.

Connect without inventing a cause

Small connectors make strong claims. Then establishes sequence. Because establishes cause. So presents a consequence. Use each only when the evidence supports that relationship.

Fictional fact packet: a release adds background rendering and reduces export time. The packet does not establish that the first change caused the second.

Unsupported connection: Background rendering makes exports faster.

Supported account: This release adds background rendering and reduces export time.

The second sentence can remain plain. If the explanation needs a causal link, investigate it. A more elegant transition cannot create missing evidence.

Echo a relevant noun when it helps the next sentence pick up the thought. Use but for a real qualification or reversal, and for addition and then for a known next event. A paragraph does not need a transition word merely because another paragraph precedes it.

Review moreover, furthermore and similar signposts in context. Sometimes they express a useful addition. Sometimes they hide the fact that two paragraphs have no established relationship. Repair the relationship before choosing a synonym.

Place exceptions by consequence

A condition that determines whether the reader may act belongs before the action. A limitation that affects a purchase belongs beside the relevant claim. An edge case that helps explain a concept may wait until the main model is clear.

Do not hide a required condition in a parenthesis or optional note. State its effect and the supported path.

Fictional packet: the application replaces an existing output file with the same name and lets the reader choose a different output name. The source document remains unchanged.

Export replaces an existing output file with the same name. To keep that output, choose a different name before exporting. The source document remains unchanged.

The warning appears before the preventive action and preserves the distinct state of the source document. It does not claim that replacement can be undone.

When several exceptions compete for space, inspect the structure. Separate an alternate workflow from a qualification that applies to every reader. Make the branch visible before someone starts down it.

Repair the wall paragraph

A dense paragraph may contain a good definition, a prerequisite, a sequence and recovery guidance. Identify those jobs before trimming words.

Fictional packet: export uses the last saved state; the output goes to the chosen folder; a read-only destination prevents output creation.

Export creates output from the last saved state of the document.

Save your changes before exporting. Choose a writable destination folder, then export.

Check the chosen folder for the output file. If the application reports a read-only destination, choose a writable folder and export again.

The first paragraph explains the model, the second gives the task and the third handles verification and a supported failure. The actual command labels would still need checking before publication as product instructions.

The added breaks make the jobs visible. They do not require every paragraph in the article to be equally short. Keep a developed explanation together when separating it would scatter its reasoning.

Diagnose before polishing

Name the difficulty you are trying to repair.

What the reader encounters	Repair to try	Fact to protect
A long interruption before the verb	Move or split the interruption	The timing of the action
An unclear actor	Name the supported actor or keep an honest passive	Unknown responsibility
Several nouns competing for a pronoun	Repeat the relevant noun	Which object changes
A condition after an instruction	Move the condition earlier	Who may act and when
Related statements with an invented causal link	Separate them or verify the connection	The distinction between correlation and cause
A string of equally emphatic fragments	Develop the relationship in a complete sentence	Useful intentional emphasis
A paragraph containing several tasks	Separate the tasks and route the reader	Required steps and branches

These labels give the next editor something concrete to do. “Awkward” is a reaction worth investigating, but it does not locate the repair.

Check the improved side of every before-and-after example too. A revision may fix a delayed verb while adding an unsupported cause. Good examples need the same source discipline as production copy.

Practice: recombine without losing facts

Use this fictional packet:

• Export uses the last saved state of a document.
• Unsaved edits are excluded.
• The output appears in the chosen folder.

Write a procedure opening, a concept paragraph and a confirmation note. Change order and rhythm to suit each job.

A procedure opening might be:

Save the document before exporting. Unsaved edits are excluded from the output.

A concept paragraph might be:

Export uses the last saved state of the document, so changes made since the last save are excluded. Save again when those changes need to appear in the output.

A confirmation note might be:

Check the output in the folder you chose. If recent edits are missing, confirm that you saved them before exporting.

The concept sentence uses so because the packet supports the causal explanation. The confirmation note offers a check rather than claiming that every missing edit has the same cause.

In the second pass, underline conditions and compare each claim with the packet. Read aloud to hear where the thought changes. Keep a longer sentence when it holds a necessary relationship together; keep a short one when it provides a useful stop.

Try another version with more personality in the explanation. Keep the steps literal. If the expressive version adds a capability, hides the prerequisite or makes the file appear to act, return to the facts before revising the rhythm.

Finally, remove the last-saved-state rule from the packet. The destination alone cannot establish whether export includes unsaved edits. Delete the saving claim or mark it for confirmation. This last variant tests whether the sentence's logic still comes from its source after the example has become familiar.

Checklist

• The reader meets a recognizable subject, condition or continuing topic.
• The main action is easy to find.
• Prerequisites, warnings and decision-changing limits arrive in time.
• New information connects to what the reader already knows.
• Sentence variation follows the thought rather than a numerical pattern.
• Passive voice preserves topic or uncertainty where useful.
• Connecting words keep scope, timing and cause accurate.
• Punctuation clarifies structure and preserves protected strings.
• Each paragraph develops an explanation or serves a distinct reader task.
• The revised examples have been checked for new defects as well as the intended repair.
• A read-aloud or equivalent close review found no unresolved confusion.