STR-02

Pass example

Your files are backed up every 24 hours. You can restore any version from the last 30 days.

Fail example

Your files are backed up automatically every 24 hours to our secure cloud servers, which means you can always access previous versions of your work if you need to restore a file by going to the file browser and right-clicking the file you want to restore and selecting version history from the dropdown menu and choosing the version you want.

Relevant content types

• Short UI copy
• Long-form copy

Weighted in these moments

This standard behaves differently depending on the reader's moment. Moment-aware evaluation picks one of these adjustments when the moment matches.

• destructive_action Destructive — relax
  Extra content density is acceptable — friction prevents mistakes.
• interruption — emphasize
  Dense modals and toasts overwhelm. One message, one action.

Version history

1. v4.6.1 · 2026-04-23

   Per-standard version tracking introduced. Every standard starts at the library version current at introduction; bump per-standard when the rule text, examples, or content_type_notes change.

Related standards

Other standards in the Content structure category.

• STR-01 — Use headings to create scannable structure in help content, onboarding flows, and long-form UI copy. Short UI copy like error messages, tooltips, and confirmations don't need headings.
• STR-03 — Use parallel structure in lists and sequential steps. Each item should follow the same grammatical pattern. In multi-step flows, a final result-state item ('You're ready to go', 'Your account is set up') may shift to declarative when it describes an outcome rather than an action.
• STR-04 — Front-load key information in tooltips and microcopy. Users may not read to the end.
• STR-05 — Group related information together. Don't scatter details across disconnected sections.
• STR-06 — Nest headings hierarchically. Never skip heading levels for visual styling. H1 for page title, H2 for sections, H3 for subsections.