Validated on 4 Apr 2023 • Last edited on 17 Apr 2025
When in doubt, we default to the Microsoft style guide, but this style guide supersedes any guidelines from Microsoft.
The DigitalOcean community is bigger than just us; it’s truly global. Our content and our products — including Cloudways — help people all over the world to create. With that wide reach comes a huge responsibility for us to make inclusive content that’s accessible and clear to all people. We take that responsibility seriously.
Be thoughtful about your use of language and prioritize clarity over cleverness.
Acronym usage should follow industry-standard guidance, such as the Microsoft Style Guide’s recommendations on acronyms and global communications. These principles help ensure clarity, consistency, and accessibility across our documentation.
Don’t use terms that may carry unconscious bias, sensitive subjects, or associations with military actions, politics, or historical events and eras. Use gender-neutral alternatives for common terms.
Use clear, unambiguous formats for all dates and times. Choose the format based on your audience and the technical context. Consistent formatting improves readability and prevents misinterpretation across regions and systems.
Follow RFC-2606 (example.com/net/org/edu), RFC-5737 (203.0.113.0/24 and 198.51.100.0/24), and RFC-3849 (2001:DB8::/32).
Link text should be clear, descriptive, and meaningful on its own. Readers (including those using screen readers) should understand where a link goes without needing surrounding context.
Use pronouns that are inclusive, accurate, and unambiguous. Prioritize clarity while respecting a diverse range of identities and communication preferences.
Use verbs that are active, direct, and descriptive. Strong verb choices make documentation clearer, more concise, and more actionable for readers.
Don’t use idioms, slang, or colloquialisms. They may confuse our global audience or fail to translate across cultures.
Try using different keywords or simplifying your search terms.