copy slop
Copy fails in familiar ways: a name repeated inside one card, sentences stapled together with em dashes, adjectives where a measurement belongs, an intro before the rule. Each section puts the failing copy (A) next to a rewrite (B) with the same facts, live, and states the rule that settles it. Pattern source: impeccable.style/slop; the reasoning, demos and rewrites are ours.
repeated label in one container
A container names its subject once. When the eyebrow, the heading and the button all say "billing", none of them carries information: the reader pays attention three times and learns nothing three times. The name is one decision; repeating it dilutes it and crowds out the words that could say something.
A: billing says billing
billing
billing
manage your plan and invoices.
three labels, zero facts. the button repeats the card title instead of naming its action.
B: the name appears once
billing
plan, payment method, and the last 12 invoices.
the heading owns the name; the body states what lives here; the button names its action. same card, three working parts.
<div class="card"><h4>billing</h4> <!-- the one mention of the name --><p>plan, payment method, and the last 12 invoices.</p><button>open invoices</button> <!-- names its action, not the card --></div>
em dash pileups
The em dash is a strong mark that signals an interruption. Used once, it adds rhythm; used every clause, it replaces syntax, and the reader loses the sentence's skeleton: what leads to what, what qualifies what. Prose that states relationships needs the relationships to be visible in the punctuation.
A: six dashes, one breath
Nightly syncs — which run at 02:00 — copy the ledger — the append-only table — into cold storage — where retention rules — set by finance — hold for 90 days.
every clause is stapled to the last; nothing subordinates, so nothing can be skimmed.
B: sentences carry the structure
Nightly syncs run at 02:00. They copy the ledger (the append-only table) into cold storage, where the finance-set retention rules hold for 90 days.
same facts: the period separates the two events, the commas qualify, the dashes are gone.
nightly syncs run at 02:00. they copy the ledger (the append-onlytable) into cold storage, where the finance-set retention rules holdfor 90 days.<!-- period separates events; parentheses hold the aside; zero dashes -->
generic marketing claims
"Supercharge", "seamless", "world-class" are claims no page can demonstrate, so a reader who has shipped software discounts them to zero. A claim the page can measure (a rate, a percentile, a count) survives scrutiny and does the persuading the adjectives attempted.
A: adjectives
supercharge your pipeline
seamless integrations, world-class performance, effortless setup.
three unmeasurable claims; each one could describe any product, so each one describes none.
B: the measurement is the claim
importer
moves 2,400 rows per second and holds p95 under 80 ms on a 10 million row table.
same card, same job: two numbers a reader can check against their own workload, and a button that leads to the proof.
<div class="card"><h4>importer</h4><p>moves 2,400 rows per second and holds p95 under 80 ms on a10 million row table.</p><button>read the benchmark</button> <!-- the claim's proof --></div>
forced contrast
The "Not X. Y." slogan borrows the punch of a real contrast without doing the work: it never says what the thing is, only what it is louder than. A reader who does not already know the product learns nothing, and a reader who does feels the pitch.
A: negation as a headline
not a dashboard. a decision engine.
the reader must already know what a 'dashboard' is and why denying it means anything.
B: say what it is
a dashboard for deploys
who shipped, what changed, and what broke, per release.
the same ambition (this is more than charts) stated as content: who shipped, what changed, what broke.
<h4>a dashboard for deploys</h4><p>who shipped, what changed, and what broke, per release.</p><!-- states what it is and who it serves; no negation headline -->
magic words
"Like magic", "simply", "it just works" mark the exact spot where an explanation was owed. They promise the reader that understanding is unnecessary, which is false for anything a reader will operate: the steps exist whether or not the copy admits them.
A: wonder where steps belong
deploy in one click
press deploy and, like magic, your database migrates itself. simply ship.
two magic words, zero steps. when the deploy fails, this copy has told the reader nothing to check.
B: the mechanism in one line
deploy in one click
the runner applies pending migrations, health-checks the service for 30 seconds, then switches traffic.
same one-click promise, now falsifiable: the reader knows what will happen and in what order.
<h4>deploy in one click</h4><p>the runner applies pending migrations, health-checks the servicefor 30 seconds, then switches traffic.</p><!-- the promise stays; the mechanism replaces the wonder -->
filler intros
"In this section we will look at..." spends the reader's first and sharpest attention on a sentence that survives deletion. It also signals that the page does not trust its own structure: a section that opened with its rule would not need to announce that a rule is coming.
A: throat clearing
retries
in this section, we will take a look at and explore the retry configuration options that are available to you and how they can be used.
38 words before the first fact, and the reader has learned that retries exist, which the heading already said.
B: the rule is the intro
retries
retries back off exponentially: 1s, 2s, 4s, capped at 30s, five attempts per request.
the first sentence under the heading is the rule; the numbers follow it immediately.
<h4>retries</h4><p>retries back off exponentially: 1s, 2s, 4s, capped at 30s,five attempts per request.</p><!-- first sentence under the heading is the rule -->
hedging
"Should probably", "might", "can help" convert a claim into a non-claim: they are true no matter what happens, so they inform no one. When the team has measured the effect, the hedge hides the strongest sentence available; when they have not, the sentence should say that instead.
A: unfalsifiable by design
batching
enabling batching should probably reduce costs and might improve latency for most users.
'should probably' and 'might' fit every possible outcome; the reader learns nothing and pays attention anyway.
B: the measurement, with its scope
batching
batching cut p95 latency from 210 ms to 140 ms in the september load test; writes outside the batch window were not measured.
same topic, now a fact and its boundary: what was measured, when, and on which traffic.
<h4>batching</h4><p>batching cut p95 latency from 210 ms to 140 ms in the septemberload test; writes outside the batch window were not measured.</p><!-- measurement + scope; the unmeasured part says so -->