Terminology

Consistent terminology ensures clarity and reduces confusion across Hardwater products.

General Principles

1. Be consistent - Use the same term for the same concept
2. Be clear - Use terms that are easy to understand
3. Be concise - Prefer shorter terms when possible
4. Be specific - Use precise terms, avoid vague language

Common Terms

Actions

Term	Usage	Avoid
Save	Save changes, data	Store, Persist
Delete	Delete item, account	Remove, Erase
Cancel	Cancel action	Close, Dismiss
Submit	Submit form	Send, Post
Create	Create new item	Add, Make
Edit	Edit item	Modify, Change
Update	Update information	Change, Modify

Status

Term	Usage	Avoid
Active	Active status	Enabled, On
Inactive	Inactive status	Disabled, Off
Pending	Pending status	Waiting, Queued
Completed	Completed status	Done, Finished
Failed	Failed status	Error, Broken

Navigation

Term	Usage	Avoid
Home	Home page	Main, Dashboard
Settings	Settings page	Preferences, Config
Profile	User profile	Account, User
Help	Help section	Support, FAQ

Forms

Term	Usage	Avoid
Required	Required field	Mandatory, Must
Optional	Optional field	Not required
Email address	Email input label	Email, E-mail
Password	Password input	Pass, Pwd
Confirm password	Confirm password	Re-enter password

Messages

Term	Usage	Avoid
Success	Success message	Successfully, Done
Error	Error message	Failed, Problem
Warning	Warning message	Caution, Alert
Information	Info message	Note, Tip

Brand-Specific Terms

Hardwater

• Project - Main work unit
• Task - Work item within a project
• Team - Group of collaborators
• Workspace - Organization or company space

Hardwater Studios

• Portfolio - Collection of creative work
• Project - Creative project
• Asset - Creative asset (image, video, etc.)
• Studio - Creative workspace

Technical Terms

When technical terms are necessary:

1. Define on first use - Explain technical terms when first introduced
2. Use consistently - Once defined, use the same term
3. Provide context - Help users understand technical concepts

Example:

"API (Application Programming Interface) allows different software to communicate with each other."

Avoiding Jargon

Prefer plain language over jargon:

Jargon	Plain Language
Leverage	Use
Utilize	Use
Facilitate	Help, Make easier
Implement	Add, Create
Execute	Run, Do

Regional Variations

Use American English spelling and terms:

• Color (not colour)
• Organization (not organisation)
• Center (not centre)

Resources

• Voice and Tone
• Content Patterns
• Get Started: Content Designers