What is Common Noun?
A common noun names a general person, place, thing, idea, or category rather than one individually named entity, so it is normally lowercase unless another capitalization rule applies.
What good common noun looks like
A well-edited sentence distinguishes general category words from proper names, keeping ordinary nouns lowercase while preserving capitals only where a sentence, title, or official name requires them.
- Identify the general category being named.
- Keep the common noun lowercase in ordinary sentence position.
- Capitalize only when another rule independently requires it.
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.
- Identify the general category being named.
- Keep the common noun lowercase in ordinary sentence position.
- Capitalize only when another rule independently requires it.
How to write common noun step by step
- 1Replace the noun mentally with another member of the same category.
- 2Check whether an official name is actually present.
- 3Lowercase category words used generically.
- 4Retain capitalization at the beginning of a sentence.
- 5Review paired uses such as city/New York City or university/Stanford University.
8 Common Noun examples
Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.
The teacher collected the essays.
Our city added two bicycle lanes.
She borrowed a novel from the library.
A university can set its own application deadlines.
The river flooded after three days of rain.
Every company needs a clear refund policy.
Common Noun templates
Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.
General person: The [common noun] [verb phrase].
General place: A/The [common noun] [action].
General thing: This [common noun] [description].
Common mistakes to avoid
- Capitalizing job titles used generically.
- Treating every geographic word as a proper noun.
- Lowercasing a common noun when it begins a sentence.
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 Common Noun
What is Common Noun?
A common noun names a general person, place, thing, idea, or category rather than one individually named entity, so it is normally lowercase unless another capitalization rule applies.
What makes Common Noun effective?
A well-edited sentence distinguishes general category words from proper names, keeping ordinary nouns lowercase while preserving capitals only where a sentence, title, or official name requires them.
How do I write Common Noun?
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 Common Noun?
Capitalizing job titles used generically. Treating every geographic word as a proper noun. Lowercasing a common noun when it begins a sentence.
When should I use a first-party or primary source instead of a secondary source for Common Noun?
Use the first-party or primary source when the exact fact, quotation, current requirement, project/manuscript detail, policy, metric, or source text controls the conclusion. Use a strong secondary source when the job is synthesis, explanation, field-level context, or orientation and the secondary source is appropriate to that job. If a reader could act on the claim, if sources disagree, or if wording depends on an exact passage, number, rule, or current status, escalate to the controlling source of truth and record the source, version/date, and locator before publication.
Should Common Noun 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 Common Noun 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 Common Noun 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.