What is Capitalization?
Capitalization is the use of uppercase letters according to sentence position, proper-name status, titles, headings, abbreviations, and style-specific conventions rather than simply to make words look important.
What good capitalization looks like
Accurate capitalization distinguishes true proper names from generic descriptions, follows a consistent title and heading style, and avoids unnecessary capitals that can make ordinary roles or concepts look like formal names.
- Capitalize the first word of a sentence and true proper nouns.
- Distinguish formal titles used with names from generic job descriptions.
- Apply one documented title-case or sentence-case system to headings.
- Check branded terms, geographic names, days, months, languages, and official document names individually.
A practical structure to follow
Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.
- Capitalize the first word of a sentence and true proper nouns.
- Distinguish formal titles used with names from generic job descriptions.
- Apply one documented title-case or sentence-case system to headings.
- Check branded terms, geographic names, days, months, languages, and official document names individually.
How to write capitalization step by step
- 1Mark every capital letter in the draft.
- 2Ask whether each marks sentence position, a proper name, an acronym, or a chosen heading style.
- 3Lowercase generic roles and concepts unless a style rule requires otherwise.
- 4Verify unusual institutional or product capitalization from authoritative sources.
- 5Run a final heading-consistency check.
8 Capitalization examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
Correct: Professor Rao spoke first. Correct generic use: The professor spoke first.
Correct: We meet on Monday in September.
Generic: The marketing department revised the plan. Formal name may differ if the organization officially names the unit.
Sentence case heading: How the review process works.
Title case heading under a common style: How the Review Process Works.
Correct: She studies Japanese and economics.
Capitalization templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
Proper-name check: Is [term] an official unique name or a generic description?
Job title: [Formal Title + Name] / [generic title] when used descriptively.
Heading system: Apply [chosen style] consistently to every heading at the same level.
Common mistakes to avoid
- Capitalizing a job title everywhere because it seems important.
- Using title case inconsistently across headings.
- Lowercasing a formal proper name because the words are ordinary in other contexts.
- Copying all-caps branding into running prose when the organization’s style does not require it.
Final revision checklist
- Does the opening make the purpose clear quickly?
- Is every important claim, detail, or example doing a distinct job?
- Could a reader misunderstand any pronoun, transition, time reference, or instruction?
- Is the tone appropriate for the relationship and situation?
- Can you remove repetition without removing necessary context?
- If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?
Questions about Capitalization
What is Capitalization?
Capitalization is the use of uppercase letters according to sentence position, proper-name status, titles, headings, abbreviations, and style-specific conventions rather than simply to make words look important.
What makes Capitalization effective?
Accurate capitalization distinguishes true proper names from generic descriptions, follows a consistent title and heading style, and avoids unnecessary capitals that can make ordinary roles or concepts look like formal names.
How do I write Capitalization?
Start with the purpose and reader, then work through the structure in order. Draft for meaning first, check the examples for pattern, and do a final revision for clarity, accuracy, tone, and unnecessary repetition.
What should I avoid when writing Capitalization?
Capitalizing a job title everywhere because it seems important. Using title case inconsistently across headings. Lowercasing a formal proper name because the words are ordinary in other contexts.
Should Capitalization show one “last updated” date or track verification at the claim level?
Use a page-level revision date for editorial history, but do not let it imply that every statement was reverified on that date. Changeable facts, quotations, policies, project facts, market data, provider capabilities, and other consequential claims should carry a source record with their own last-verified date or version and a specific recheck trigger. Stable editorial synthesis and original instructional examples can use the page revision/version record instead. When a material correction, retraction, or recommendation change affects what the reader should believe or do, retain the prior record and disclose what changed and why.
How do I know whether a claim or source on a Capitalization guide is stale, corrected, or still active?
Do not infer status from the page-wide update date. Check the controlling source or project record, the exact version/date last verified, and the trigger that could make the item changeable. Keep it active when the source still controls the exact claim; mark review due when a trigger has fired but the conclusion is not yet disproved; mark stale when the old version no longer controls; and use corrected, retracted, withdrawn, or superseded when the editorial history requires it. The correction level should match reader impact: cosmetic edits are not the same as a material factual correction or a critical source failure.
If a source behind Capitalization changes, how do I know which other claims or guides need review?
Use the dependency map rather than reviewing the entire site blindly. Identify the exact claim or example that depends on the source, classify the dependency as direct, shared, advisory, or independent, and record why the source changed. Direct dependents should be reviewed immediately when a controlling source is corrected, retracted, superseded, or no longer supports the claim. Shared dependents can be queued by source/claim ID and scope. Replace the source only when the replacement performs the same evidentiary job—or change the claim. Keep the old source/status in the ledger, then propagate the review to templates, examples, and related guides only where that dependency actually exists.
How can editors track a source change for Capitalization without reviewing the entire site?
Use persistent claim, source, and dependency records. Link only the claims that truly depend on a source, then change that source record’s status in the Writing Authority admin when it is corrected, superseded, stale, withdrawn, or retracted. The registry queues the linked claims with a reason code and priority. Reviewers can see the affected guide, inspect the source/dependency IDs, revise or replace the evidence where necessary, and close the queue item after verification. Original site-created examples and templates remain independent unless they contain a real external factual dependency.