Salesforce.com Style Guide for Documentation and User Interface Text

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Capitalization

Rules for capitalizing specific names or terms can never be final. Consistency is the key. Capitalize whole words sparingly and don't use to add emphasis. If there's any doubt, opt for lowercase.

  • Capitalization styles:
    • THIS LINE IS ALL CAPS.
    • this line is all lowercase.
    • This Line Is Initial Caps.
    • This Line is Title Style Caps.
    • This line is sentence style caps.
  • When spelling out an acronym, only capitalize the individual words if they're proper nouns. Use all capital letters for the acronym itself.
  • Use a colon to separate two clauses when the second explains the first. Capitalize the word following the colon only when it's a complete sentence or formal quotation. For example: Don't forget this point: The report is due by 9:00.
  • Always capitalize both words in an edition name, as in Enterprise Edition and Group Edition. Don't capitalize edition when it appears by itself as a common noun: Accounts are available in all editions.
  • Use all lowercase for file extensions. For example, Word adds .docx to a file name if you neglect to specify the file format when saving. Refer to the Microsoft Manual of Style for Technical Publications.
  • Capitalize all letters in a key name, as in ALT or RIGHT ARROW.
  • Use title-style capitalization for:
    • Browser window titles
    • Popup window titles
  • Capitalize each column heading in a table, the first word of each column entry, and proper nouns. However, don't change the capitalization of objects, methods, calls, or other language constructs, such as the Account object or create().
  • Use title-style capitalization for UI page, related list, and screen names. In documentation, use the page name exactly as it appears on the screen.
  • Capitalize the names of all tabs in the application. Refer to them using the exact spelling in the user interface. For example: Accounts tab, not Account tab. Don't capitalize tab in general usage.
  • Don't capitalize report unless it's part of the report name.
  • Use title-style capitalization for button names, such as Clone or Run Report. Don’t use ending punctuation in button labels.
  • In UI text, most object names are referenced from hard-coded labels that are capitalized. In this case, use the capitalization found in the user interface. For example: Select Text Area (Long) and click Next.
  • Capitalize link text based on context. For example, if link text includes an element that is capitalized in the UI, capitalize it in the link text too.
  • Use sentence caps for ghost text, unless the text includes a reference to a UI element or other proper noun.
Titles and Headings
Use title-style capitalization in titles and headings.
In titles, use a colon to separate a title from a subtitle. Capitalize the first letter of every word in a title, with the exception of prepositions, articles, coordinate conjunctions, the infinitive to, and forms of the verb to be. These words are not capitalized unless they're the first or last word or an integral part of a verb phrase.
Capitalize the first and last words of titles, no matter what the words are.

Capitalize the second element of a hyphenated compound in a title when it's a feature name, proper noun, or adjective: Real-Time Quotes, Third-Party Software.

Don't alter words or abbreviations whose meaning or correct spelling depends on case: Using the vi Editor.
Don't alter the capitalization of abbreviations in titles: The 1-kHz Oscillator, Start Sync at 12:00 a.m.
See Also