Skip to main content

Writing style guide

Style guide. A protocol between voice, reader and machine.

Contents

This page is a working protocol for prose on this site. It guides three readers: future me, a human editor, and a machine model: artificial intelligence generative language model. Review a draft with empathy, and edit it for consistency and clarity.

A written protocol holds one voice steady across years, moods, and tools. Read each item as a pressure test from a cross-check list. Apply it, and see what the sentence gains in its context. Every rule here is local, situated, and open to revision.

Purpose

Readers

Write for a shadow reader: a reader who is often excluded, tired, distracted, multilingual, and/or neurodivergent. Future me reads first.

A sentence that holds for a tired reader holds for most readers. Precision still needs its own check. The register sits between academic and plain, so a practitioner keeps reading and a newcomer follows without a glossary.

Voice

My English sits across several boxes, and the edit keeps its marks.

It carries four influences: the Bangladeshi English and Bangla idioms of a Dhaka upbringing, the grammar of independent cinema, the hand-coded early web, and years of bureaucratic and academic English. Standard fluency sands those marks away.

Priority

When two rules pull apart, the higher one wins.

House preferences serve the reader. A preference that bends the meaning has stopped serving.

Writing

Sentences

Give each clause one job, and state what holds or changes.

Competing clauses split attention. A sentence that names the surviving condition (“The institution held”) carries more than one built around an absence (“The institution did not change”).

Words

Choose the word that names what happened, at its true scale.

Filler signals a hedge (just, actually, basically), a package (moreover, “it is important to note,” key takeaways), or an inflation (literally, incredibly, delve). Crutch words repeat without a job: question, encounter, route, practice. Question words used as rhetoric are filler too: who, what, when, where, why and how, set up as a staged question (“Why does this matter?”) or a teaser (“Here is how”). Both delay the claim and sound wise without saying more. State the claim. Keep these words for a plain grammatical job: the reader who returns. Each costs the tired reader attention, and so do -ize, -ness, and -ly words that bury a plain verb.

Prefer one verb to a phrasal verb. In put off, take away, find out or go on, the meaning hides in a small particle that a reader of English as a second language must guess. Choose the single verb: postpone, remove, learn, continue. Keep a phrasal verb only when no single verb says the same thing as plainly.

Marks

Let punctuation pace the reading, and keep its set small.

Each mark asks the reader to change pace. Few marks, used the same way every time, become habit. Quotations, citations, and code keep their original marks.

Editing

Structure

Give every text a shape the reader can hold: a few parts, short paragraphs, concrete things first.

Three is a drafting habit. It keeps a section compact and invites a test of anything extra. A necessary fourth point stays.

Strike and repair

Strike a default word that someone else supplied, and write the repair beside it: ~~default~~ repair.

Interfaces, forms, platforms, and generative models hand over vocabulary already chosen. The struck word is the expected one, so the reader recognizes it at a glance and the repair does the thinking. Some repairs correct a term. Others make an argument, and an argument is open to dispute.

Use one strike per paragraph at most, and name the source of the default once.

Review

Separate three acts: diagnosis, suggestion, and edit. The writer authorizes the third.

An editor, human or machine, sees patterns the writer has stopped seeing. The writer knows what the sentence is for. Each keeps their part.

Version history

1.9 (2026-11-14). Prefer one verb to a phrasal verb: remove, not take away; postpone, not put off. Plain-language guidance for readers of English as a second language.

1.8 (2026-11-10). Bangla in Latin letters follows its Bangla sound, not the Anglo standard: kokhono, shomoy, kori. Names keep their owners’ spelling.

1.7 (2026-11-08). No question words as rhetoric: state the claim. Section headings renamed Purpose, Writing and Editing, since the guide now avoids its own staged questions.

1.6 (2026-11-04). No serial comma, unless a list would misread without it.

1.5 (2026-10-04). Headings ask who, why, and how. Rule priority added. Seam and review authority defined. Verb table folded into Words. Exceptions for quotations, citations, code, and ranges. File and metadata rules moved to the site’s decision log.

1.4 (2026-10-04). Rule of three throughout: instruction, why, how. Strike and repair shown in use. Editing instructions folded into the page. Semicolons and negative framing removed.

1.3 (2026-10-04). Copyedited and compressed. US spelling. Screen rules moved to the site’s decision log.

1.2 (2026-10-04). Sentence-case headings. Added strike and repair, links, labels, marks and dates, Bangla, and citation.

1.1 (2026-08-25). Added assertive framing, suffix and crutch-word checks, show before tell, and two verbs (outlive, hold).

1.0 (2026-08-25). First draft, from a working session on the unlearning framework.