Why Your English Titles Look Wrong (Even When the Spelling Is Fine)

Introduction

I didn't really think about English capitalization until I started publishing things.

Blog titles, landing pages, a batch of variable names — every word spelled correctly, yet the whole thing felt… untidy. Like a desk where everything is present but nothing is aligned.

A few examples I've had to fix:

• how To Improve Your SEO quickly in 2026
• WELCOME TO our Website built for developers
• the History Of Artificial intelligence and Machine learning
• iphone User Guide for Beginners
• A GUIDE TO writing better emails at Work

Grammar and spelling were usually fine. The capitalization rules were just fighting each other.

Why capitalization trips people up

Capital letters do more than mark the start of a sentence. They signal proper nouns, give headings visual weight, and preserve fixed brand spellings (that lowercase i in iPhone is the classic example).

So you're not following one rule — you're juggling visual convention and grammar, and those conventions shift between academic papers, news outlets, and product copy.

That also explains a familiar moment: you fix what you can, Grammarly still flags something, and neither of you is necessarily wrong. You're just using different style guides.

Mistakes I keep seeing

Mixing Title Case and Sentence case

This is the big one. Part of a headline follows "title rules," part follows "sentence rules," and the result looks assembled from two templates:

Title Case is the formal headline style. Content words (nouns, verbs, adjectives) are usually capitalized; short words like a, the, to, and and often stay lowercase in the middle. But there's no global standard — How to Build and How To Build can both be defensible, and AP style capitalizes To.

Sentence case is simpler: write the headline like a normal sentence. Notion, Google Docs, Slack, and GitHub lean this way. It reads naturally and doesn't feel like it's shouting for attention.

Capitalizing anything that "feels important"

Non-native writers hit this a lot — including me. Seasons, academic fields, generic nouns: if it seems significant, the shift key comes out:

Spring and summer are seasons, not proper nouns. Physics and computer science are fields of study. University stays lowercase when you mean it generically. West coast in the Scotland example is just a geographic description.

Categories stay lowercase; names get capitalized. Spring is a category; English and World War II are names. West Coast (US) is a name; west coast of Scotland is not.

ALL CAPS that sound like shouting

ALL CAPS reads as yelling. Modern UI tends to use weight, color, or icons instead of caps lock.

"Normalizing" brand names

iPhone, eBay, GitHub, YouTube, ChatGPT, JavaScript — fixed spellings. Auto-title-case and typos turn them into:

On SEO titles and product pages, Github instead of GitHub is the kind of detail that quietly erodes trust.

Developers: naming conventions that don't match

If you code, you've seen this up close. Backend returns user_name, frontend uses userName, URLs want user-profile, SQL has created_at — each layer has its habit. Mix them and you get:

No single style is universally "correct" — just pick one per context and stick with it in your project.

When I stopped fixing these by hand

Capitalization cleanup is repetitive, mechanical, and unforgiving. Dozens of titles to normalize, SEO meta titles to align, an entire paragraph typed with Caps Lock on — by the fifth line I'm drifting.

For batch headlines and variable names I use Case Converter. It works well for:

• Side-by-side preview: type hello world and see Hello World, HELLO WORLD, helloWorld instantly
• Writing and dev formats: switch Title Case, Sentence case, camelCase, snake_case without overwriting source text
• Batch cleanup: normalize SEO titles, meta titles, and variable names at once
• Whitespace tidy-up: trim extra spaces and line breaks while you're at it

Faster than pasting into Word and trying formats one by one.

There's no single "correct" capitalization

Publishers, schools, and style guides disagree:

The first two can be valid in their respective systems; the third usually looks sloppy.

What actually helps readers: consistency within a piece. Don't mix Title Case and Sentence case. Don't let auto-format turn GitHub into Github. Consistency beats debating every single word.

Closing thought

Capitalization is a small detail with an outsized effect on how polished your work feels — whether a README looks cared-for, an SEO title looks trustworthy, or a page reads like it was thrown together.

If you bounce between headlines, marketing copy, and variable names, a good converter eventually becomes part of the routine. Format problems that seem trivial at five items become real time sinks at fifty.