A Pre-Publish Text Formatting Checklist for Clean Copy

You've spent hours writing. The argument is tight, the examples land, the conclusion feels earned. Then you hit publish — and two minutes later someone screenshots a heading that says "CHAPTER overview" and tags you in it. One letter. Lowercase o. The whole post now lives in someone's cringe folder.

Formatting errors don't just look sloppy. They undermine trust in a way that's weirdly disproportionate to their size. A double space nobody notices in conversation becomes glaring in print. A title where half the words are capitalized and half aren't makes readers wonder what else you were careless about.

This checklist is what I run through before anything goes live — blog posts, landing pages, email newsletters, product descriptions, even internal documents that clients might ever see. It's ordered by how easy each category is to miss, not by importance. Everything here matters.

1. Heading and Title Case

Start here because it's the most visible layer and also the one with the most inconsistent rules floating around the internet.

Pick one style and use it everywhere. Title Case (capitalize most words), Sentence case (only the first word and proper nouns), or ALL CAPS for specific stylistic reasons. Do not mix them across headings on the same page.
Check your subheadings separately from your main title. It's extremely common to nail the H1 and then let H2s and H3s drift into inconsistent capitalization.
In Title Case, verify the small words. Articles (a, an, the), short prepositions (in, on, at, by, for), and coordinating conjunctions (and, but, or, nor) typically stay lowercase unless they're the first or last word. Run each heading through a case converter tool if you're unsure — don't guess.
Watch for proper nouns inside headings. Brand names like iPhone, WordPress, or YouTube have their own capitalization rules that override your heading style. "How To Use Youtube For Marketing" is wrong. "YouTube" is not negotiable.
Check your meta title separately. The title tag in your HTML is often written at a different time than the visible H1. They frequently diverge.

2. Spacing — The Invisible Mess

Spacing errors are basically invisible when you're reading your own draft. Your brain fills them in. A paste from a PDF, a copy from an email, a tab character that snuck in — these live in your content rent-free until someone else notices.

Run a double-space check. Two spaces between sentences is a typewriter habit that's been obsolete for decades. Paste your content into a plain text editor and use Find (Ctrl+F / Cmd+F) to search for two consecutive spaces. There will be some. There are always some.
Check for spaces before punctuation. "We need to talk , okay ?" happens more often than you'd think when editing on mobile or copying from certain sources. A space before a comma or period is always wrong in English.
Check for missing spaces after punctuation. The opposite problem.After a period with no space, the next sentence merges.This is more common in converted documents than in fresh writing but it shows up.
Look at line breaks in your actual rendered output. What looks fine in a markdown editor or a CMS text box sometimes renders with awkward paragraph breaks or orphaned single words on their own line.
Check around em dashes and en dashes. Decide: do you use spaces around your em dashes or not? (Both are valid — just be consistent.) An en dash (–) used where an em dash (—) belongs, or a plain hyphen used for both, is another common drift point.

3. Sentence Case Inside Body Text

This one trips people up because they're thinking about headings and forget the body copy has its own rules.

Check every sentence starts with a capital. In long paragraphs, especially ones with semicolons or restructured sentences, a lowercase start slips through.
Verify that mid-sentence capitals aren't there for the wrong reasons. Sometimes autocorrect capitalizes words after abbreviations (e.g., "etc. The" becomes "etc. the" by convention after abbreviation periods in some style guides, but "e.g. The" mid-clause is wrong). Know your style guide's position on this.
Product and feature names: lock them down. If you're writing about an app called "taskBoard" with a lowercase t and capital B, that's the name. Write it that way every single time. If your CMS autocorrects it, add it to your autocorrect exceptions or do a final Find-and-Replace pass.

4. Punctuation Consistency

Oxford comma: pick a side and stay there. "Red, white, and blue" vs. "red, white and blue" — neither is universally correct, but mixing them in one document is always wrong.
Quotation marks: curly or straight? Straight quotes (" ") are a typewriter artifact. Curly/smart quotes (" ") are typographically correct. Most modern CMSes handle this automatically, but copied text often brings straight quotes with it. Check, especially around dialogue or pulled quotes.
Apostrophes in contractions and possessives. The autocorrect-generated apostrophe in "it's" is sometimes a straight apostrophe when it should be a closing single quote shape. It looks wrong at large sizes.
Ellipsis: three dots or the actual ellipsis character? Three separate periods (...) and the ellipsis character (…) render differently in different fonts and contexts. Pick one and use it consistently.

5. List Formatting

Lists are where formatting inconsistency gets comfortable and sets up camp.

All list items should follow the same grammatical structure. If three items are full sentences and one is a fragment, fix the fragment. If three items start with verbs and one starts with a noun, restructure.
Decide on end punctuation and commit. List items that are full sentences typically end with periods. Fragments typically don't. Whatever you choose, every item in a given list should match.
Check capitalization at the start of each list item. They should all start with a capital, or none should — depending on whether they're full items or completions of a lead-in sentence. ("The checklist covers: case errors, spacing issues, and punctuation" — those items don't need caps.)
Nested lists need their own consistency check. They're easy to forget about.

6. Numbers and Units

Spell out numbers under 10 (or 13, depending on your style guide), use numerals for the rest. Don't write "I have 3 suggestions" in one paragraph and "I have nine tips" two paragraphs later.
Units of measurement: consistent abbreviation or spelling. "5 MB" vs "5mb" vs "5 megabytes" — choose a format and stick to it throughout the document.
Dates: pick a format. June 23, 2026 or 23 June 2026 or 2026-06-23 — all valid in context, but do not use all three in one article.

7. The Final Read-Aloud Pass

This is not optional and most people skip it. Don't.

Read the entire thing out loud, slowly. Your mouth will stumble on doubled words ("the the"), missing words, and awkward sentence rhythms that your eyes would glide over.
Use your browser or OS text-to-speech feature. Hearing a robot read your copy is humbling but extremely effective. Any sentence that sounds robotic probably reads robotic.
Read headings in sequence as if they're a standalone outline. Do they make sense in order? Do they match the tone of the body copy underneath them?

8. Tools That Actually Help

There's no shame in using mechanical help for mechanical problems.

A dedicated case converter tool lets you paste text and flip between Title Case, UPPER CASE, lower case, and Sentence case instantly. Use it on every heading before it goes live.
A whitespace visualizer (many code editors have this) makes double spaces and trailing spaces visible at a glance.
The Find-and-Replace function in your CMS or editor is your manual sanity check for anything the automated tools miss — search for two spaces, search for straight quotes, search for your product name in every case variation to catch inconsistencies.

The goal isn't perfection for its own sake. It's that readers can move through your content without hitting a speed bump that makes them think about the writing instead of the ideas. Every formatting error is a tiny tax on their attention. This checklist exists to collect that tax before your readers have to pay it.

Save a copy somewhere you'll actually use it. Run through it before you hit publish. Not every time will feel necessary — but the times it catches something, you'll be glad you did.