# English

**Audience and variety.** Keep the English variety in the brief or approved copy. Resolve spelling, time format or a numerical date against a regional convention when those differences matter. An English-language request does not establish a US readership. In a customer reply, use the form of address already in the relationship. A neutral imperative often works for a procedure.

**Diction and rhythm.** Use familiar verbs for the reader's task and keep the specialist term when it specifies the operation. Contractions can suit an informal email. Preserve the discipline of an incident report, a contractual promise or an exact quotation. A repeated warning may be needed at two distinct decision points.

**Typography and values.** Retain the publisher's punctuation conventions and every protected code or identifier. Preserve numeric ranges and currency symbols. When asked to localize an unambiguous source date, a written month avoids swapping month and day. Keep `06/07` as supplied when its meaning is unresolved. Never infer a time zone, currency or thousands separator from the reader's language.

**Fictional service update.** “The new policy applies to renewals received after 8 June” restricts both the transaction and the date. Replacing it with “The policy takes effect on 8 June” changes both. Carry the full condition through the rewrite, even when it needs an extra sentence.

Use the [glossary](glossary.md) for product terminology. UK government guidance offers examples of task-oriented wording for interface text. [GOV.UK Service Manual](https://www.gov.uk/service-manual/design/writing-for-user-interfaces)
