
Splitting one prompt in two renumbered every step after the cut
We split one long numbered prompt into two. Every step after the cut changed number, and the sentences that navigate by those numbers went on pointing at whatever now wore them.
How we build the thing that publishes your changelog, your blog and your release notes.

We split one long numbered prompt into two. Every step after the cut changed number, and the sentences that navigate by those numbers went on pointing at whatever now wore them.

Entries that open with "we've added" put the team in the subject position and leave the reader to translate. The repair is grammatical: make the thing the reader controls the subject of the sentence, and delete the team from it.

A product changelog is read by people who will see the change on screen. An API changelog is read by people whose code will stop working, and that audience needs the symbol name, the date and a feed a machine can poll.

An assistant quotes a passage, not a page. Docs that survive that treatment answer in the first sentence, restate their own subject, and name exact values instead of gesturing at them.

Whether GA4 records a click to your docs depends on where the docs live. The built-in outbound click event fires only for links that lead away from the current domain, and configuring cross-domain measurement switches it off again.
Market4 turns one release note into a changelog page, a blog post, a mail-out and a week of social posts — and then tells you which of them brought anyone back.