2.2 KiB
2.2 KiB
Copy Guidelines
Tone
- Calm
- Direct
- Reassuring
- Technical only when necessary
Product Voice
- Explain what happened first.
- Explain impact second.
- Offer a next step every time.
- Avoid fear-based maintenance language.
Good Patterns
Results may be incomplete without Full Disk Access.You can keep using limited mode and grant access later.Most selected actions are recoverable.
Avoid
Critical errorIllegal operationYou must allow thisYour Mac is at risk
CTA Style
- Use clear verbs:
Retry,Open System Settings,Review Plan,Restore - Avoid generic CTA labels such as
OKandContinue
Glossary
Scan— read-only analysis that collects findings; it never removes anything by itself.Cleanup Plan/Uninstall Plan— the actionable set of reviewed steps Atlas proposes from current findings.Review— the user checks the plan before it runs. Avoid usingpreviewas the primary noun when the UI is really showing a plan.Run Plan/Run Uninstall— apply a reviewed plan. Use this for the action that changes the system.Reclaimable Space— the estimated space the current plan can free. Make it explicit when the value recalculates after execution.Recoverable— Atlas can restore the result from History while the retention window is still open.App Footprint— the current disk space an app uses.Leftover Files— extra support files, caches, or launch items related to an app uninstall.Limited Mode— Atlas works with partial permissions and asks for more access only when a specific workflow needs it.
Consistency Rules
- Prefer
planoverpreviewwhen referring to the actionable object the user can run. - Use
reviewfor the decision step before execution, not for the execution step itself. - If a button opens macOS settings, label it
Open System Settingsinstead of implying Atlas grants access directly. - Distinguish
current planfromremaining items after executionwhenever reclaimable-space values can change. - Keep permission language calm and reversible: explain what access unlocks, whether it can wait, and what the next step is.