Creating content ·
How to rewrite a post before you publish it
The first draft of a post is almost never the one to publish. Not because it is badly written, but because in the first pass you are still deciding what you want to say, and that process leaves behind sentences that do not belong, half resolved ideas and a tone that does not always sound like you.
Rewriting is not fixing grammar mistakes. It is a process done in separate passes, each with a specific goal, that turns an honest draft into a text you can publish without hesitating.
By Sheena de PunkVoice · Edited by Mario Pérez
Why does it help to edit in separate passes?
Short answer: because each layer of the text asks for a different kind of attention, and mixing them means fixing commas while the underlying idea is still unresolved. Four passes cover almost everything, idea, structure, sentence and voice.
Doing it all in a single read leads to a specific problem, polishing the style of a paragraph you will later delete entirely because it did not fit the structure. That time is wasted and the text stays just as weak where it mattered.
Order matters. You review the biggest things first, idea and structure, because a change there can throw out whole sentences. You leave the smallest things, sentence and voice, for the end, once you already know which text is going to survive.
- Idea: does this say something worth reading?
- Structure: does the order of the parts help or get in the way?
- Sentence: does each line say the same thing with fewer words?
- Voice: does this sound like how you actually talk?
What gets reviewed in the idea pass?
Short answer: whether the post defends something concrete or stays at a generic observation anyone could have written. In this pass no sentence gets touched yet, you only ask whether it is worth publishing this the way it is framed.
A clear sign the idea is not resolved is not being able to summarize the post in one sentence without using the word and several times. If the summary needs to link three loose ideas, the post has not decided yet what it is about.
When the idea is weak, no amount of sentence editing fixes it. It is worth going back to the origin, the question or the experience that started the post, and checking whether there is really something to say about it before polishing further.
What gets reviewed in the structure pass?
Short answer: the order of hook, promise, development, twist and closing, and whether any part is missing, excessive or in the wrong place. Here whole paragraphs get moved, others get deleted and sometimes the opening gets rewritten from scratch.
A useful trick is reading only the first line of each paragraph, skipping the rest. If those first lines tell the whole post in a coherent way, the structure holds the text together. If they feel disconnected, the problem is not in the sentences but in the order of the ideas.
This pass is also where you decide what gets cut entirely. A paragraph can be well written and still not belong, either because it repeats something already made clear earlier or because it distracts from the main twist.
How do you trim without losing nuance?
Short answer: cutting words, not ideas. Most long sentences hold a single idea wrapped in qualifiers, repetitions and transition phrases that can be removed without changing the meaning.
A practical method is removing every ly adverb and every adjective that adds no new information. If the sentence still works without them, they were not needed. If it breaks, it was one of the few that did add something.
Nuance gets lost when you cut the wrong way, removing the exception or the but that made the statement honest. A shorter post with a more absolute claim than what you actually believe is not an improvement, it is a different text you no longer fully stand behind.
- Cut: ly adverbs, redundant adjectives, empty transition phrases.
- Keep: the exception or nuance that makes the statement honest.
- Keep: the concrete example, even if it lengthens the paragraph.
How do you spot filler sentences and clichés?
Short answer: by looking for sentences that could appear in any post about any topic without changing anything. If a sentence fits equally well in a post about sales as in one about leadership, it is filler, no matter how well built it is.
Clichés tend to announce themselves with the same structure, a big statement with no example behind it. Lines like consistency is the key to success or all change starts with yourself say nothing specific about what you actually did, and that is why the reader skips them without really reading.
The fix is the same in both cases, replacing the generic sentence with the concrete detail that originated it. Instead of consistency is the key, telling how many weeks in a row you posted without seeing results and what happened when you stopped waiting for one.
- Filler: sentences that work for any post about any topic.
- Cliché: big statements with no example of your own behind them.
- Fix: replace the generic sentence with the detail that originated it.
Why does reading the post out loud help?
Short answer: because the ear catches rhythm and voice problems the eye stops noticing after several silent reads. A sentence that reads fine internally can sound odd out loud, and that oddness usually points to a forced construction.
Reading out loud also reveals where a period is missing. If you run out of breath halfway through a sentence, that sentence is too long for the post's rhythm, even if it is grammatically fine.
Another useful sign is noticing where you stumble while reading, since it often matches a word you would not use in conversation. Those words are the fastest giveaway of a text that does not sound like the person signing it.
How do you check the text sounds like your own voice?
Short answer: by comparing it to something you have actually written or said, not to the abstract idea of how a professional post should sound. If the text uses words or turns of phrase you never use in a normal conversation, it probably resembles a generic mold more than it resembles you.
A simple exercise is covering the author's name and asking whether someone who knows you would recognize the post as yours without seeing it. If the answer is uncertain, it is usually because the tone got flattened while trying to sound correct instead of sounding like yourself.
Your own voice is not a fixed style applied the same way every time. It changes with the topic and the mood of the post, and that is fine. What should not change is that the word choices still feel like yours and not like a neutral text anyone could have written.
What makes the final mobile pass different?
Short answer: it shows how the text actually breaks for most of the people who will read it, something a desktop editor does not display the same way. A line that looks short on the computer can wrap at an odd point on a small screen and change the rhythm you had planned.
This pass also checks where the see more cut actually falls, which varies by device and app. If the hook and the promise do not fit before that cut on mobile, it needs trimming even if it looked fine on desktop.
It is worth doing this pass as the last step, after idea, structure and sentence are already resolved, because by then content is no longer changing. You are only adjusting line breaks and, if needed, shortening a sentence that takes up more room than expected on a small screen.
How do you use Sheena to rewrite without letting it write for you?
Short answer: by asking it to discuss the text with you, not to hand it back finished. It is useful for flagging where a sentence sounds like filler, where the argument has a logical gap or where the tone drifts from how you normally write, and you decide on those flags, not it.
A specific use that works well is sending the draft and asking it to mark the three sentences that most resemble clichés, without rewriting them. You then decide how to change them, with your own example or your own word, instead of accepting a generic alternative that sounds just as empty.
The line is clear when the result stops sounding like you. If reading the finished post you do not recognize the sentences as your own, the line between discussing the text and having it written for you has been crossed. That is exactly the approach Sheena works with inside PunkVoice, and we explain it in more detail in our editorial policy.