I only run the exact word when the word itself is the story; otherwise, I mask it with the first letter and a dash so readers still get the weight of it without me repeating harm for no reason. Before anything goes live on my own site, I read the sentence back out loud, and if a slur or swear word is there for shock rather than evidence, I cut it. A bracketed description of what was said usually reads clearer and safer than the word itself.

I decide to quote, soften, or mask slurs and profanity by asking one key question: does the exact wording materially affect the reader's understanding of wrongdoing or intent, or does it only amplify harm? If the precise phrase is needed for accountability, I allow a quote but pair it with a clear content note and context. If the exact wording is not essential, I soften or mask it to prevent retraumatizing readers while preserving meaning. I draw on the principle that ambiguity can be weaponized, so clarity is the priority when determining whether to publish language verbatim. One wording choice I used in guidance to reporters was to replace a graphic slur with a short bracketed descriptor such as "[racial slur]" and immediately follow it with a concise explanation of its role in the exchange. That approach preserved the factual record, reduced harm to readers, and kept focus on the behavior being reported rather than on repeating abusive language.

I decide to quote verbatim only when the exact language is necessary to show the incident's meaning or to prompt a concrete change; otherwise I avoid repeating gratuitous slurs. We adopted a rule that summaries are not acceptable and that frontline messages should be presented word for word so the record is not softened through compression. To reduce harm, I pair any raw quote with a short factual note about what action followed, which signals purpose rather than amplifying the offensive language. Publishing the original text alongside a concise explanation of consequence has made pieces clearer and safer by focusing readers on cause and outcome rather than the phrasing itself.

When publishing The Hennhouse Podcast transcripts, I balance the need for authenticity with the responsibility to avoid harm, quoting profanity only when it is essential to meaning or accountability. More often, I soften language so the sense of the exchange is clear without repeating a slur. One redaction I used was replacing explicit words with a short bracketed label such as "[expletive]" to preserve pacing and tone while signaling offensive language. This approach kept the conversation readable and made it safer for a broader audience.

The deciding factor should be whether the language is the story itself or a distraction from it — not whether it makes anyone uncomfortable.

When I help authors handle sensitive material in their published work, I apply a three-part test:

Does the exact word carry evidentiary weight? If the word itself is the point, quote it.

Would softening it distort the meaning? If yes, don't soften.

Would masking it protect the reader without hiding the truth? If yes, mask it and contextualize.

One redaction choice I've used that made a piece clearer and safer: an author's manuscript quoted a source using a racial slur in a historical context. Instead of reproducing it in full, I redacted it as [slur redacted — racial epithet] and added a brief footnote explaining that the word appeared in the original source and why it was withheld.

This preserved the historical accuracy, signaled respect to the reader, and prevented the author's platform from being misread as endorsing the language. The focus stayed on the argument, not the shock value — and it landed better with editors and readers alike.

The principle is simple: quote when the word is evidence, soften when it's incidental, and mask when the harm outweighs the informational gain — but always tell the reader what you did and why.

Emmanuel Michael, Author Visibility Specialist