Salesforce Style Guide for Documentation and User Interface Text

About This Guide
Styles A-Z
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
Object and Object Names
Object Manager
Operating System and OS
Optional Steps
Org, Organization
Overlay
Overview Topics
P
Q
R
S
T
U
V
W
Glossary
PDF

Object and Object Names

Don't change the capitalization of objects, methods, calls, or other language constructs, such as the Account object or create(). Consider rewriting a sentence so that a lowercase element is not the first word. However, headings in reference documentation often contain elements, and the elements must retain their case. Use sentence case in tables, if the table heading is a complete sentence or partial introduction to a sentence, as in some FAQ tables.

Objects, such as account and opportunity, or data types, such as Lookup and Text Area, receive no special formatting. They follow different capitalization guidelines depending on their context:
  • Code: When referring to a code context such as in the API or Apex, use the capitalization found in the code itself. The names of objects and data types are capitalized in Apex documents, but are lowercase in API documents to reflect the actual values in the Apex code or the API WSDL (Web Services Description Language), respectively. For example: (API) Every custom field has a boolean data type. (Apex) Ensure that the Boolean condition remains true.

    In most cases, it’s not important to the general user whether you’re referring to the object or record (instance). Use your best judgment and clarify when necessary.