Sunday morning I made a change that no analytics tool will ever surface. No conversion rate will visibly move. No user will notice consciously. I replaced every em-dash and en-dash across three sites with plain punctuation — commas, periods, parentheses, the occasional colon — and it took about twenty minutes across three repos.
That was the week. Four commits total: the Sunday autopost, and that one content edit applied to theapparchitect.com, civo-cloud-manager.app, and marcelrgberger.com in quick succession.
When a Tiny Edit Is Actually a Decision About Voice
Here is why I did it, and why I think it is worth writing about.
Em-dashes are not wrong. But they have a specific register. They read as deliberate, slightly formal, a little editorial. The kind of punctuation you see in long-form journalism or careful essays. That is fine if your writing actually earns that register. When it does not — when the surrounding prose is conversational and direct — an em-dash starts to feel like someone straightening their tie before a casual conversation. A small mismatch, but those stack up.
I had been using em-dashes heavily across all three sites for a while. At some point I read a paragraph back to myself out loud and it did not flow the way I thought it should. The rhythm was slightly stiff. I tracked it to the dashes. A comma or a period would have done the job with less ceremony.
The fix was mechanical once the decision was made. I ran a search across the MDX content directories, found the patterns, and replaced them. Three commits in about six minutes of actual work. The decision took longer than the execution, which is usually how it goes with copy.
I am still not sure I got every instance right. There are places where an em-dash genuinely was the best choice and I may have swapped it out for something weaker. I will keep an eye on it. If something reads worse next time I review a page, I will put it back. That is fine — writing is iterative, the same as code.
Side Note: What “Thin Week” Actually Means
Two recent posts here have been honest about quiet periods on the contribution graph. I want to be careful not to turn that into a genre. So let me say this plainly: this was a thin week because a longer-running piece of work is still in progress and not ready to show yet. It is not stalled. It is just not shippable. When it is, it will have a proper post.
In the meantime, the small edit across three sites is a real thing I did, and I think there is something honest in writing about it. If you are considering hiring an independent developer for a custom app, this is the kind of work that tends not to appear in proposals or invoices. It is the thirty minutes on a Sunday where you reread your own writing, find something off, and fix it — not because anyone asked, but because it was wrong.
That habit — the willingness to loop back and correct small things that only you notice — is what separates a site that feels considered from one that feels assembled. I think it applies equally to copy and to code.
This week’s active projects are on marcelrgberger.com and at civo-cloud-manager.app. More substance next post.