Summary
UI labels
Bold UI labels, and match the capitalization the product shows. If the button says Create Role, write Create Role, even though docs headings use sentence case. Don’t use quotation marks, italics, or code font for UI labels. Use code font only for text the reader types or text that appears in code.Emoji
Don’t use emoji for decoration or to signal importance. For warnings and notes, use a callout component at the right level:
Check marks (✅) and crosses (❌) in tables are fine because they carry data, such as whether a plan includes a feature.
Technical values
Write limits, quotas, versions, default values, and parameter values exactly as the product, SDK, or API defines them. The one-through-nine rule for numbers doesn’t apply to these values, and this guide doesn’t set a style for them. Accuracy is what matters.Dates and times in technical content
The general date and time rules in Grammar, punctuation, and formatting apply to prose. When you describe dates and timestamps in data, APIs, or exports, accuracy comes first:- Name the format. Say whether a value is a Unix timestamp in seconds, a Unix timestamp in milliseconds, or an ISO 8601 date.
- Name the time zone. Say whether the value is in UTC or in the project’s time zone. Don’t leave the reader to guess, and don’t assume a default.
- Use the exact format the API accepts. Write format tokens in code font, with the same casing the API reference uses for that endpoint, such as
yyyy-mm-ddorYYYY-MM-DD. Include an example value:2026-01-31. - Show the full example. A sample value is clearer than a description:
"time": 1767225600.