The Proofreader's Stubborn Ink: On the Permanence of a Corrected Error
There’s a persistent myth that the internet is ephemeral, a river of content where yesterday’s news is washed away by today’s. But anyone who has ever tried to correct a long-standing error on a website knows a different truth. The web has a memory, and its pages can become as stubbornly fixed as print. Few understood this tension between fluidity and permanence better than Elizabeth Eisenstein, the great historian of the printing press. Her work doesn't just tell us about the 15th century; it holds up a startlingly clear mirror to our own digital content anxieties.
Eisenstein painstakingly documented how the advent of print created 'fixity.' For the first time, a text could be reproduced hundreds of times, with each copy being identical. This was a revolution. Scribes made errors; their manuscripts were unique, prone to drift and decay. But a printed book was a solid thing. An error typeset in Gutenberg’s workshop could be replicated a thousandfold, locking a mistake into the culture with a force previously unimaginable. The printing press, in its quest for perfect replication, also enabled the perfect replication of flaws.
We face the same paradox with our digital pages. We publish a blog post, a product description, a technical manual. It’s indexed, cached, shared, and linked to. It achieves a kind of fixity not in paper, but in protocols and pathways. Then, we find the error: a misspelled name, a factual inaccuracy, a claim that has since been disproven. The instinct is to correct it, to hit 'update.' But the web, like the early print shops, has already done its work. The incorrect version lives on in archives, in PDFs downloaded by readers, in the minds of those who first consumed it. The correction is the new, fragile truth; the error has the solidity of a thing already disseminated.
So what is the digital proofreader to do, standing in Eisenstein’s shadow? The lesson isn't to avoid correction, but to approach it with historical awareness. A silent edit, a quick fix with no trace, feels clean but denies the reality of the page's life. It pretends the error never had its own fixity, its own existence. A better practice is to acknowledge the correction itself, to leave a subtle mark—a quiet note, a publication date, a revision log. This isn't about shaming an old version, but about respecting the page's history. It’s the digital equivalent of a proofreader’s mark in the margin: not an erasure, but a testament to the process of getting it right.
Eisenstein showed us that fixity is a double-edged sword. It gives an idea longevity, but it can also embalm its imperfections. Our task is to manage this inheritance. We must strive for the fixity of truth while accepting that our pages, like printed books, have a life and a history. The goal isn't a pristine, ahistorical document that pretends it sprung perfectly formed from the server. It’s a living text that honors its own corrections, carrying its stubborn ink stains as a record of its journey toward accuracy.
Notes & further reading
A few pages I came back to while writing this: