Writing style
Write clear, consistent, and accessible copy across Davidnet.
Spell out abbreviations and use US English
Use the full name of features and apps in customer-facing copy. Avoid Latin abbreviations like ‘e.g.’, ‘i.e.’, ‘etc.’, or ‘&’ because they aren’t localization friendly and confuse assistive technologies.
- Use US English in all UI copy and code.
- Never use an apostrophe for plural abbreviations.
- Avoid articles like ‘a’, ‘an’, and ‘the’ in buttons, labels, and action headings.
Save changes
Save the changes & exit
Format headings and text emphasis
Use sentence case in all titles, headings, menu items, labels, and buttons. Only capitalize the first word of a sentence, proper nouns, and trademarked names.
- Phrase UI and documentation headings with an action verb, and avoid gerunds (the ‘ing’ form of verbs).
- Never use bold, italics, colons, or periods in headings. Rephrase questions as statements whenever possible.
- Use bold to highlight key phrases and static UI elements like menu items or buttons. If text is already bold, use italics instead.
- Use italics sparingly in apps, and never in hyperlinks. Reserve them for dynamic UI elements like a field name or user input.
- Use
monospaced textfor file names, directories, attributes, strings, and developer documentation.
Select Account settings , then Profile .
Navigating to “Account Settings” > “Profile.”
Write in active voice and present tense
Active voice puts the emphasis on the person or thing performing an action, making your writing shorter, clearer, and friendlier.
- Use contractions whenever possible to keep your tone conversational.
- Use present tense for instructions and UI messages. Reserve past tense for completed actions, like error headings or success messages.
- Minimize pronouns, though you can use ‘you’, ‘your’, or ‘we’ when advising users or writing error messages.
- Avoid gendered pronouns. Always use ‘they’ or ‘their’ instead of ‘he/she’ or ‘his/her’.
You need to validate your email address.
Validation will be required by the user.
Structure lists for easy scanning
Use lists to break up dense content and limit them to 6 items or fewer. Split longer lists into multiple groups.
- Bulleted lists: Use when the order doesn’t matter, and phrase every item in a parallel way.
- Numbered lists: Use for sequential tasks. Capitalize the first word of each step and end with a period.
- Complete sentences: Start each item with a capital letter and end with a period. Do not use a lead-in sentence with a colon.
- Fragmented sentences: Introduce the list with a colon, start each item with a lowercase letter, and omit ending periods.
Format numbers and ranges
Use digits rather than words in most cases, except when a number starts a sentence, appears in a common expression, or falls between one and nine in formal long-form content.
- Write out ‘zero’ and ‘one’ if the digits could be confused with the letters L, I, or O.
- Use ‘to’ instead of hyphens in number ranges, unless space is tight in a table or mobile view.
- Use ‘of’ instead of a forward slash to express a fraction, like 3 of 5 steps.
- Use a dot for thousands separators and a comma for decimals, like 1.000 and 0,5%.
Reference UI elements and prevent truncation
Always write UI elements in sentence case, even if the component styles them differently. Bold both the element name and its icon when writing step-by-step instructions.
- Use ‘then’ instead of a ‘>’ symbol between navigation steps, because screen readers announce the symbol as “greater than”.
- Shorten messages or wrap text to avoid truncation across screen sizes and zoom levels.
- Add a tooltip to display full text if truncation is unavoidable in icon buttons or user-generated content.
Apply punctuation consistently
Consistent punctuation keeps interfaces clean and prevents screen readers from misinterpreting symbols.
- Apostrophes: Use curly apostrophes to show possession. Place the apostrophe before the ‘s’ for singular nouns (including those ending in ‘s’) and after the ‘s’ for plurals.
- Colons and commas: Use colons to introduce lists or steps, and always include an Oxford comma before the final item in a series.
- Hyphens and dashes: Join 2 or more words acting as a compound adjective before a noun, except after ‘very’ or adverbs ending in ‘-ly’. Avoid em dashes in copy.
- Ellipses: Never put spaces between the dots in an ellipsis (…). Only add spaces around the ellipsis when omitting words inside a direct quote.
- Exclamation marks: Avoid them in UI copy, and use at most 1 per marketing page.
- Periods: End complete sentences with a period and 1 space. Omit periods in titles, tooltips, field descriptions, and menu names unless they contain more than 1 sentence.
- Quotation marks: Use single curly quotes (‘’) in UI copy and when defining terms. Use double curly quotes (“”) for direct quotes in documentation, and never use quotation marks to emphasize UI elements.
“From medicine and space travel to disaster response … our products help teams all over the planet advance humanity through the power of software.”
Example of an ellipsis inside a direct quote