Capitalization Rules — Consistent Capitalization Standards for Technical Documentation

In this tutorial, you will learn about Capitalization Rules. We cover key concepts, practical examples, and best practices to help you master this topic.

Capitalization rules define when words should be capitalized in documentation. Consistent capitalization improves readability and maintains professional appearance. Inconsistent capitalization is one of the most visible signs of unprofessional documentation.

In this lesson, you will learn capitalization rules for headings, product names, UI elements, and code terms.

What You'll Learn

You will understand sentence case versus title case, capitalize product names and UI elements correctly, and apply consistent capitalization rules.

Why It Matters

Inconsistent capitalization distracts readers and undermines credibility. When Compression is capitalized in one heading and compression in another, readers notice.

Real-World Use

DodaTech enforces sentence case for all headings through Vale rules. Capitalization consistency improved from 70 percent to 98 percent.

flowchart LR
  A[Capitalization Rules] --> B[Sentence Case]
  A --> C[Title Case]
  A --> D[Product Names]
  A --> E[UI Elements]
  B --> F[Headings]
  C --> G[Proper Nouns]
  D --> H[DodaZIP]
  E --> I[Save Button]
  A:::current
  classDef current fill:#f90,color:#fff,stroke:#333,stroke-width:2px

Sentence Case vs Title Case

Sentence case capitalizes only the first word and proper nouns. This is the standard for most technical documentation headings.

Title case capitalizes major words including nouns, verbs, adjectives, and adverbs. It is used for book titles and formal publications.

Most technical style guides recommend sentence case for headings. Choose one and stay consistent.

# Sentence case (preferred for most tech docs)
## Setting up your development environment
## Installing the required dependencies

# Title case (academic or formal)
## Setting Up Your Development Environment
## Installing the Required Dependencies

Product Names

Always capitalize product names as they are officially written. DodaZIP has ZIP in all caps. Doda Browser has Browser capitalized.

Do not change product name capitalization for stylistic reasons. Even at the start of a sentence, keep the official capitalization.

When a product name starts with a lowercase letter, capitalize it at the start of a sentence. Otherwise, keep the official form.

# Correct product name usage
- DodaZIP compression library
- Doda Browser configuration
- DodaTech developer portal

# Incorrect
- DodaZip compression library
- Doda browser configuration
- Dodatech developer portal

Common Mistakes

1. Inconsistent Heading Case

Using sentence case in some headings and title case in others. Pick one and use it everywhere.

2. Capitalizing Common Terms

Compression Algorithm should be compression algorithm when used generically.

3. Wrong Product Name Capitalization

Writing DodaZip or dodazip instead of the official DodaZIP.

4. Over-Capitalizing UI Elements

Writing Click The Save Button instead of Click Save.

5. Capitalizing Code Terms

Writing The GetUser function instead of the get_user function. Code terms should match their actual case.

6. Capitalizing File Extensions

.CSV file instead of .csv file. File extensions are typically lowercase.

7. Inconsistent Bullet Capitalization

Capitalizing some bullets and not others. Be consistent within each list.

Practice Questions

1. What is sentence case?

Only the first word and proper nouns are capitalized. Used for most technical documentation headings.

2. When should you capitalize a product name?

Always capitalize as the product officially writes it. DodaZIP not DodaZip.

3. How should code terms be capitalized?

Match the actual case of the code. If the function is get_user, write get_user not GetUser.

4. What is the rule for UI element capitalization?

Capitalize as they appear in the interface. Click Save not Click The Save.

5. Challenge: Audit a documentation page for capitalization issues. Find five inconsistencies and correct them. Categorize each issue by type.

FAQ

Mini Project

Create a capitalization rules reference for a documentation project. Include rules for headings, product names, UI elements, code terms, file extensions, and list items. Provide good and bad examples for each rule.

What's Next

Next: Punctuation Rules