---
title: "Headings"
description: "Use headings and subheadings to organize content into sections and help users find specific information. When creating a heading, follow the next principles: Include keywords from the associated paragraphs."
canonical: "https://helpcenter.veeam.com/docs/styleguide/tw/headings.html"
breadcrumb: "Style Guide > Plain English > Split Information > Headings"
dateModified: "2026-09-03"
---

# Headings

Use headings and subheadings to organize content into sections and help users find specific information.

When creating a heading, follow the next principles:

- Include keywords from the associated [paragraphs](paragraphs.md).
- Keep the heading short — try to use 4–8 words maximum.
- <a id="capitalization"></a>Capitalize words in the heading according to the following rules:

<table style="width:100%;" class="Blue_Table">
  <tr style="vertical-align:top">
    <th>
      <p>Capitalize</p>
    </th>
    <th>
      <p>Do Not Capitalize</p>
    </th>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">All adjectives, adverbs, nouns and verbs.</p>
    </td>
    <td>
      <p>The preposition <span style="font-style:italic;">to</span>, unless it is the first word in the heading.</p>
    </td>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">All subordinating conjunctions <span style="font-style:italic;">(although, since, if, before, after, unless, until, for (to), as, though, that, once, when, while, because</span>).</p>
    </td>
    <td>
      <p>All coordinating conjunctions (<span style="font-style:italic;">and, or, nor, but, for, yet, so</span>), unless a conjunction is the first word in the heading.</p>
    </td>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">All prepositions that contain more than 4 letters.</p>
    </td>
    <td>
      <p style="text-align:left;">All prepositions that contain 4 letters and less.</p>
    </td>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">Hyphenated compound words (for example, <span style="font-style:italic;">On-Demand Sandbox</span>). </p>
    </td>
    <td>
      <p>Case-sensitive words (for example, command line commands).</p>
    </td>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">The negative quantifier <span style="font-style:italic;">no</span> and the negative adverb <span style="font-style:italic;">not</span>.</p>
    </td>
    <td>
      <p>All articles (<span style="font-style:italic;">a, an, the</span>), unless an article is the first word in the heading.</p>
      <p><span class="T_Controls">Note:</span> In Veeam technical documentation, we do not use articles in headings. </p>
    </td>
  </tr>
  <tr style="vertical-align:top">
    <td style="vertical-align:top;">
      <p style="text-align:left;">All subject and object pronouns (<span style="font-style:italic;">I, me, you, he, him, she, her, it, we, us, they, them</span>), including possessive adjectives (<span style="font-style:italic;">my, your, his, her, its, our, their</span>).</p>
    </td>
    <td></td>
  </tr>
</table>

::: important

The only exception from the listed capitalization rules are Release Notes documents where only topic headings are capitalized according to the rules: *System Requirements*, *Required Permissions*, *New in This Release*, *Known Issues and Limitations* and *Technical Documentation References*. All subheadings that introduce new features and list known issues must be capitalized according to the following principles:

- Capitalize only the first word in each subheading.
- Use articles in case they help you avoid misunderstanding. For example, *The most recent restore point will be used if multiple backups or replicas of a VM exist*.

:::

## Examples

1. Step 1. [L]{.mdhl-correct}aunch [a]{.mdhl-incorrect} [N]{.mdhl-correct}ew [B]{.mdhl-correct}ackup [C]{.mdhl-correct}opy [J]{.mdhl-correct}ob [W]{.mdhl-correct}izard
2. Step 12. [F]{.mdhl-correct}inish [W]{.mdhl-correct}orking [w]{.mdhl-correct}ith [the]{.mdhl-incorrect} [W]{.mdhl-correct}izard
3. [G]{.mdhl-correct}etting [t]{.mdhl-correct}o [K]{.mdhl-correct}now [V]{.mdhl-correct}eeam [B]{.mdhl-correct}ackup & [R]{.mdhl-correct}eplication
4. [B]{.mdhl-correct}ackup [a]{.mdhl-correct}nd [R]{.mdhl-correct}eplication
5. [I]{.mdhl-correct}nstalling [U]{.mdhl-correct}pdates [i]{.mdhl-correct}n [U]{.mdhl-correct}nattended [M]{.mdhl-correct}ode
6. /[b]{.mdhl-correct}ackup[S]{.mdhl-correct}ervers/{[ID]{.mdhl-correct}}/[c]{.mdhl-correct}redentials
7. [F]{.mdhl-correct}ind-[VBRViE]{.mdhl-correct}ntity
8. [S]{.mdhl-correct}cale-[O]{.mdhl-correct}ut [B]{.mdhl-correct}ackup [R]{.mdhl-correct}epositories