Acronyms
Guidelines for introducing and formatting acronyms to maintain clarity and readability.
Language
Validated on 2 Feb 2026 • Last edited on 17 Feb 2026
When in doubt, default to the Microsoft style guide. This style guide supersedes Microsoft guidance when rules conflict.
DigitalOcean content and products, including Cloudways, support people with different backgrounds, languages, and levels of experience. Language choices should prioritize clarity, inclusivity, and accessibility for a worldwide audience.
Language Principles
Apply these principles consistently across all DigitalOcean content.
Clarity and Simplicity
Use plain, direct language:
- Favor clarity over cleverness.
- Avoid unnecessary jargon. Use technical terms only when they are widely understood or required for accuracy.
- Keep sentences as simple as possible without losing essential detail.
Point of View
- Address the reader in the second person (“you”).
- Use “we” when speaking for DigitalOcean or making recommendations.
Contractions
Use contractions (for example, you’re, it’s) to maintain a natural, conversational tone.
Avoid contractions when emphasizing a strong recommendation, requirement, or constraint.
Language Standards
Use American English spelling and vocabulary across all DigitalOcean content.
Examples include:
- color (not colour)
- behavior (not behaviour)
- license (noun and verb, US usage)
Refer to this section’s child pages for the complete set of language standards and rules.
Examples and Names
- Use fictional names such as Sammy Shark for internal mascots.
- Use diverse, realistic human names for user examples.
Voice-Related Language Constraints
Certain language choices affect clarity and interpretation across cultures:
- Passive voice is acceptable when it improves clarity, accuracy, or simplicity.
- Avoid overpromising, exaggeration, or emotionally loaded language.
- Avoid idioms, slang, or humor that may not translate globally.
Examples
These examples show preferred and discouraged language usage.
| DO | DO NOT |
|---|---|
| “You can resize the Droplet at any time from the Control Panel.” | “This feature will completely change how you deploy forever.” |
| “We recommend enabling backups before deploying to production.” | “Just spin it up real quick—it’s super easy.” |
| “If you see this error, restart the service and try again.” | “Users simply love how magical this experience feels.” |
Considerate Language
Guidelines for using inclusive, precise, and bias-free language.
Dates and Times
Guidelines for formatting dates, times, and time zones clearly and consistently.
Domains and IP Ranges
Guidelines for using reserved domains and IP address ranges in documentation examples.
Links and Link Text
Guidelines for writing clear, descriptive, and accessible link text.
Pronouns
Guidelines for using inclusive, accurate, and unambiguous pronouns while prioritizing clarity and respect for diverse identities.
Verbs
Guidelines for using active, direct, and descriptive verbs to make documentation clear, concise, and actionable.
Word Choice
Guidelines for avoiding idioms, slang, and colloquialisms to ensure clarity for a global audience.