Skip to content

Voice and tone

Write plainly, precisely and respectfully. Show competence through facts, useful explanations and a clear next step. Use British spelling: organisation, colour, behaviour, licence as a noun and license as a verb. Use sentences, commas or colons instead of em dashes in prose.

Who is speaking decides the person. When Wade communicates personally with one person, by email, WhatsApp, Signal, SMS, phone or chat, or in a quote addressed to someone, he speaks as himself: I, never we or our for himself. I checked the backup and restored the file. Published copy (website, journal, storefront, SEO titles and descriptions, social media, brochures, legal pages and the knowledgebase) is the organisation speaking to a visitor, with no individual person behind it: never I; write as the organisation, so Noiz, we and our are all correct. Address the reader as you; prefer clients for the commercial relationship and users when discussing software use.

The prose name is Noiz. Do not expand it into an unverified legal entity name. Contracts, invoices and statutory notices use the verified entity for that transaction and the wording of the applicable approved document. Preserve defined legal terms when quoting or incorporating that document; they do not set the voice of an accompanying email or proposal.

The ruled devices use ASCII operators and font.family.mono (JetBrains Mono). Put one space on each side of < and |, none inside [noiz].

Device Form Where
Typed name [noiz] Footer, From-name, sign-off, terminal prompt
Product, code register noiz < send, noiz < nextcloud Subject lines, terminal, signatures
Product, display register Noiz < Send, Noiz < Nextcloud, Noiz < PeerTube Menus, page titles, headings, app tiles
Brand line hosting | cybersecurity | software | support Signature and footer tagline
Strapline lockup [noiz] | disrupt the signal Footer legal line

The typed name, brand line and strapline stay lower case. Preserve product capitalisation in display contexts. Use the pipe as the joiner; do not substitute a hyphen. Escape < as &lt; in HTML and ordinary Markdown prose; code spans, plain-text subjects and terminal output may use the literal character. Check that the reader sees the operator, not the entity text.

The portfolio has three pillars: Infrastructure (Hosting), Security (Cybersecurity) and Services (Software). Support is the delivery layer and remains in the four-word brand line. The typed [noiz] device is permitted; the removed drawn bracket artwork is not.

  • Open with Hi [First name], and then, on a new line, I trust you are well :).
  • Preserve the approved wording please feel Free to reach out. The capital F is deliberate free-software wordplay, not an error to correct.
  • The footer carries Monero accepted here. Do not repeat the pitch in the body or templates.
  • Keep internal supplier names out of client documents; name the service category. Product names and evidenced discussion of third parties remain appropriate where relevant.

Use the same opener for a client incident email, then move directly to the impact and action. A status-page entry is an update, not a letter, and has no salutation.

Hi [First name],
I trust you are well :)
[Service] has been [observed condition] since [date, time and timezone].
I have [confirmed action]. [Known impact and any uncertainty].
[Action needed from you, or an explicit statement that none is needed].
I will send the next update by [date, time and timezone].

These are writing patterns, not claims about a service:

Context Lead with Example pattern
Proposal or sales The reader’s need, scope and next action I can move [service] within [agreed scope]. Please confirm [dependency] so I can schedule the work.
Support What I checked and what happens next I reproduced [issue]. Please send [specific diagnostic detail] through [agreed channel].
Incident report Impact, times, evidence and uncertainty I restored [service] at [time and timezone]. The cause remains unconfirmed.
Status update Current state and affected function [Function] is unavailable for [confirmed scope]. Next update: [time and timezone].
Research A specific claim with its source and limits [Source] reports [finding]. This suggests [inference]; it does not establish [unknown].

Define a technical term once in plain language. State what a privacy claim covers, which data is collected or retained and which evidence supports it. Give dates and timezones for events; distinguish an observation, a hypothesis and a confirmed cause. Say when the next update is due rather than guessing when recovery will finish. Do not claim security guarantees, certification, measured performance or service commitments without evidence for that scope.

Prefer a complete sentence with one clear action in correspondence. Interface buttons can use direct verbs such as Send, Save or Download report. A button label describes what happens when activated.

Use the replacement only when its factual claim is true. If the fact is missing, ask for it or remove the claim.

Avoid Write instead
robust backups I test restores [frequency] and retain backups for [period].
seamless migration I will copy [data], verify [checks] and agree a change window with you.
cutting-edge security [Named control] checks [specific risk] at [defined point].
industry-leading performance [Measured result] under [test conditions], recorded [date].
military-grade protection [Named mechanism] protects [defined data] against [specific threat].
rest assured I have completed [action]. The next check is [check and time].
as soon as possible I will send an update by [time and timezone].
leverage a solution Use [tool or service] to [specific task].

Avoid fear, manufactured urgency and superiority claims. Use Free or Libre when software freedom is meant; explain that meaning on first use. Keep GNU/Linux in that context and preserve the actual spelling of a product name.

Where AI helped produce written content and a human completed the final editing, preserve the existing disclosure exactly:

Note: while some of this content was produced with the help of AI, the final editing has been done by a real human being.

Do not assert human editing until it has happened. Image disclosure is separate: follow Imagery, including visible labels for abstract AI work. A general footer disclosure does not replace an image’s label.

Body copy and headings use font.family.display (Space Grotesk). Code and metadata use font.family.mono; emphasis follows font.emphasis.family, font.emphasis.style and font.emphasis.synthesis. Use color.semantic.text.secondary for body copy and color.semantic.text.primary for headings. Formatting supports the words, never a claim that has not been checked.