Writers' Toolkit Write Style guide Capitalization and punctuation
Open source

Capitalization and punctuation

This section includes capitalization and punctuation guidelines.


Consult the following capitalization guidelines when you write.

Sentence-case capitalization

Use sentence-case capitalization to capitalize the first word of a sentence, the first word of a heading, and all proper nouns.

This style is primarily lowercase and is considered the quickest form to read.

All caps capitalization

Use all-caps capitalization exclusively for abbreviations, such as API, HTTP, ID, JSON, SQL, or URL.

Capitalizing proper nouns

The names of people, places, and products take initial capitals because they are proper nouns.

Grafana-specific capitalization guidelines

  • Menu and submenu titles always use sentence case: capitalize the first word, and lowercase the rest.
    • Dashboards when referring to the submenu title.
    • Keyboard shortcuts when referring to the submenu topic.
  • Generic and plural versions are always lowercase.
    • Lowercase dashboard when referring to a dashboard generally.
    • Lowercase dashboards when referring to multiple dashboards.
  • Exceptions: If a term is lowercase in the Grafana UI, then match the UI.

Kubernetes objects

When referring to Kubernetes objects, such as Jobs, Pods, and StatefulSets, capitalizing them makes it clear that you are not talking about generic jobs and pods.

In the first use, introduce the object as Kubernetes XX, then use it alone in subsequent uses.


  • Create the Kubernetes Job and check the logs to retrieve the generated token:
  • The Job requires the token be submitted as …

Punctuation guidelines

Refer to the following punctuation guidelines when you write technical content.

  • After a period, add one space, not two.
  • When listing a series of items, insert a comma before and or or. This is known as using serial commas or the Oxford comma.
    • Example: “During lunch, we enjoyed quiche, quinoa, and kale salad.”
  • Do not abbreviate and with an ampersand (&).
    • Exception: If the UI uses an ampersand, match the UI.
  • At the end of a paragraph, remove extra space characters.
  • Use bold to indicate paths within a web application, and greater-than symbols (>) to indicate path separators.
    • Example: “To add an administrator to the list of local users, navigate to Appliance > Configuration > Access.”