On this page
Content basics
Plain language, voice and tone, terminology, grammar and punctuation for text in Nebula components.
These guidelines apply to all text written for Nebula components and the products built with them. Component-specific guidance lives with each component. In Kaluza Agent Experience your user is working under pressure and often mid-call, so content has to be scannable, unambiguous and quick to act on.
Plain language
Write in plain English. Aim for a reading age of around 9 and keep sentences under 25 words, which is what GOV.UK asks for and is not the same as writing for children. Domain terms are exempt, because you can't simplify MPAN. Use the simplest word that is accurate.
Do
Help
About
Buy
Don't
Assist
Approximately
Purchase
Keep sentences short. One idea per sentence. Front-load the most important information, put the key point first, then the supporting detail.
Do
Payment failed. Card declined by the bank.
Don't
The bank has declined the card, which means the payment failed.
Avoid double negatives. They force the reader to decode meaning under pressure.
Do
This account is eligible for support.
Don't
This account is not ineligible for support.
Write positively. A negative construction makes your user invert the instruction before they can act on it.
Do
To submit, complete all required fields.
Don't
You can't submit if you don't complete all required fields.
Cut weak sentence openers. Remove you can, there is, there are and replace with a direct verb.
Do
Add notes to this account.
Don't
You can add notes to this account.
Avoid adverbs and unnecessary adjectives, they are usually redundant. Delete simply, easily, just, and similar on review.
Do not use Latin abbreviations: e.g., i.e., etc. Spell it out or restructure the sentence.
Do
For example, a gas meter or electricity meter
Don't
E.g. a gas or electricity meter
Active voice
Use active voice in most cases. It is shorter, clearer, and more direct.
Do
We couldn't process this payment.
Don't
This payment could not be processed.
Passive voice is acceptable where active voice would sound accusatory, which is usually where the user caused the error. Naming us as the actor makes a bank's decision sound like ours.
Do
Your payment has been declined.
Don't
We declined your payment.
Use simple verb tenses, past, present, future. Avoid perfect tenses (has/have done) and progressive tenses (is/was doing).
Do
You entered an incorrect password.
Your changes will be saved.
Don't
You've entered an incorrect password.
Your changes will be being saved.
Write about what actions and controls do, not how to physically interact with them.
Do
Select Submit payment
Enter the address
Open the account menu
Don't
Click the Submit payment button
Type the address
Tap the account icon
Labels and calls to action
Interactive elements should use verb-first labels that describe the action.
Do
Submit payment
Don't
Submission
Be specific. Every call to action on a page should be unique so screen readers can distinguish between them.
Omit articles (a, an, the) in labels and action-based headings.
Do
Add note
Don't
Add a note
Avoid personal possessive pronouns in labels.
Do
Update address
Don't
Update your address
Voice and tone
Tone should be neutral, direct, and helpful. This is a professional tool, not a consumer app.
Contractions are appropriate and improve readability, use them naturally (can't, we couldn't, you'll). Avoid contractions in legal notices, payment processing, and account security contexts where casual language reduces trust.
Do not use politeness padding (please, thank you) in UI labels. It adds length without value.
Do not inflate ease of use. Avoid easy, simple, just, they assume something about how easy your user is finding it.
Do
Set up your payment plan in 3 steps.
Don't
It's easy, just set up your payment plan.
Avoid urgency language (warning, immediately, danger) unless the situation genuinely warrants it. Reserve strong signals for genuinely critical moments.
Consistency and terminology
Use the same word for the same concept throughout. In a data-dense tool a synonym reads as a different thing, so your user will wonder what changed.
Pick one term and use it everywhere. The words for interface actions are in Preferred terms.
When an acronym appears for the first time in a context, spell it out once with the acronym in parentheses: Meter Point Administration Number (MPAN). Do not spell out platform-wide acronyms on every occurrence.
Avoid creating new acronyms. Only use an acronym if your audience is already familiar with it, or if it is an internationally recognised abbreviation (SMS, PDF, CSV).
Feature and function naming
Most features do not need a branded or capitalised name. Refer to them descriptively.
Do
bulk upload, payment plan
Don't
Bulk Upload, Payment Plan
Describe what a feature does rather than just naming it.
Do
Set up a payment plan to spread this balance over time.
Don't
Payment Plan
Every new name is another concept your user has to learn. Only introduce a named concept when it is necessary.
Writing about people
Default to they and them where you don't know someone's pronouns. Don't write his/her or he or she.
disabled is fine where it describes a control rather than a person, as in 'Sorting is temporarily disabled'. Where you mean a person, say what they need rather than naming a condition.
Capitalisation
Use sentence case for all UI text, headings, labels, buttons and notifications. Only capitalise proper nouns and product names.
Every punctuation mark has a rule, and they're together in the punctuation reference, along with dates, numbers and currency.