Lingua-e
← Back

Developer English guide + free exercises

UK vs US Spelling of Tech Terms: Color or Colour, Program or Programme?

October 21, 2026

Is it 'color' or 'colour'? 'Organize' or 'organise'? Both are correct English, they just belong to different dialects. This guide covers the spelling patterns that split British and American English, plus the tech-specific exceptions where the 'wrong' dialect spelling is actually the only one that works, like CSS, which only accepts 'color'. Then 27 free exercises to practice telling them apart.

Spelling Patterns

US vs UK spelling

Most US/UK spelling differences fall into a handful of predictable patterns. Once you know the pattern, you can usually guess the other dialect's spelling, even for a word you've never seen written that way before.

US spellingUK spellingPatternExample
colorcolour-or / -our“Pick a background color that passes contrast checks.”
behaviorbehaviour-or / -our“This flag changes the default behavior of the retry logic.”
favoritefavourite-or / -our“Users can star a repo to add it to their favorites.”
flavorflavour-or / -our“The free and paid tiers are just two build flavors of the same app.”
customizecustomise-ize / -ise“You can customize the keyboard shortcuts in the settings panel.”
organizeorganise-ize / -ise“We organize our components by feature instead of by file type.”
initializeinitialise-ize / -ise“The constructor is where you initialize the object's starting state.”
serializeserialise-ize / -ise“We serialize the response as JSON before sending it over the wire.”
synchronizesynchronise-ize / -ise“This job runs nightly to synchronize the cache with the database.”
optimizeoptimise-ize / -ise“Profile the code first, then optimize the slowest function.”
minimizeminimise-ize / -ise“Batch the requests to minimize the number of round trips.”
authorizeauthorise-ize / -ise“The middleware checks the token before it will authorize the request.”
analyzeanalyse-yze / -yse“Run the profiler to analyze where the memory leak is coming from.”
catalogcatalogue-og / -ogue“The design system has a full catalog of reusable components.”
centercentre-er / -re“Use flexbox to center the modal both vertically and horizontally.”
fiberfibre-er / -re“The new data center is connected by a dedicated fiber line.”
canceledcancelled-l / -ll“The deploy was canceled halfway through the rollout.”
modelingmodelling-l / -ll“We spent the sprint modeling the new database schema.”
travelingtravelling-l / -ll“The packet is still traveling through three more hops before it arrives.”
graygreyother“Disabled buttons are shown in gray in this design system.”
licenselicenceother“This repository is released under the MIT license.”
Practice this section →

Tech Exceptions

When the pattern doesn't apply

A handful of tech terms don't follow the usual split, either because the technology itself forces one spelling, or because software conventions settled on one spelling regardless of dialect. These are the ones developers get wrong in both directions.

color (in CSS)

CSS properties like `color` and `background-color` only accept the American spelling. `colour` is not valid CSS, and the browser silently ignores it, even in a UK-authored stylesheet.

program

Software is always a 'program' in both US and UK English (a Python program, a running program), even though British English otherwise writes 'programme' for a TV programme, a conference programme, or a degree programme.

disk

Computer storage is 'disk' in both dialects (hard disk, disk space, disk drive). British English reserves 'disc' for optical media like a compact disc or DVD, never for computer storage.

dialog box

Software interface text often keeps 'dialog box' in UK products and documentation too, even though general British writing uses 'dialogue' for a conversation between people.

Practice this section →

Key Takeaways

  • US English favors shorter endings: -or, -ize, -er, -og. UK English favors -our, -ise, -re, -ogue: color/colour, organize/organise, center/centre, catalog/catalogue.
  • CSS only accepts the American spelling 'color'. 'Colour' is invalid and silently ignored, even in UK-authored code.
  • 'Program' means software in both dialects. British English only uses 'programme' for a TV show, a conference, or a degree, never for code.
  • 'Disk' is computer storage in both dialects. British English reserves 'disc' for optical media like a CD or DVD, not for a hard disk.
  • Either spelling is understood everywhere, so pick one dialect and stay consistent within the same document, README, or codebase.

English for developers

Practice: UK vs US spelling

Each sentence describes where you'd read it: a UK blog, a US changelog, a PR description. Pick the spelling that matches.

Spelling Patterns

↑ Back to the theory
Which is the UK spelling?

A UK-based blog post about this component's would describe how it reacts to user clicks.

Which is the US spelling?

An American engineering blog would write: 'Pick a background that passes contrast checks.'

Which is the UK spelling?

In a UK team's app store listing, users 'star a repo to add it to their '.

Which is the US spelling?

An American Android developer would say: 'The free and paid tiers are two build of the same app.'

Which is the US spelling?

A US engineering doc would say: 'You can the keyboard shortcuts in the settings panel.'

Which is the UK spelling?

A UK README would say: 'We our components by feature instead of by file type.'

Which is the UK spelling?

A UK code comment would read: 'The constructor is where you the object's starting state.'

Which is the US spelling?

An American PR description would say: 'We the response as JSON before sending it over the wire.'

Which is the UK spelling?

A UK changelog entry would read: 'This job runs nightly to the cache with the database.'

Which is the US spelling?

An American performance ticket would say: 'Profile the code first, then the slowest function.'

Which is the UK spelling?

A UK architecture doc would read: 'Batch the requests to the number of round trips.'

Which is the US spelling?

An American security doc would say: 'The middleware checks the token before it will the request.'

Which is the US spelling?

An American debugging guide would say: 'Run the profiler to where the memory leak is coming from.'

Which is the UK spelling?

A UK design system's docs would read: 'We keep a full of reusable components.'

Which is the US spelling?

An American CSS tutorial would say: 'Use flexbox to the modal both vertically and horizontally.'

Which is the UK spelling?

A UK networking article would read: 'The new data centre is connected by a dedicated line.'

Which is the UK spelling?

A UK incident report would say: 'The deploy was halfway through the rollout.'

Which is the US spelling?

An American sprint summary would say: 'We spent the sprint the new database schema.'

Which is the UK spelling?

A UK networking comment would read: 'The packet is still through three more hops before it arrives.'

Which is the US spelling?

An American design system doc would say: 'Disabled buttons are shown in in this design system.'

Which is the UK spelling?

A UK open-source repo's README would read: 'This repository is released under the MIT .'

Tech Exceptions

↑ Back to the theory
Tech exception

This CSS declaration only works with one spelling, no matter which team wrote it: : #1a1a1a;

Tech exception

A British developer describing software they wrote would still say 'I wrote a Python ', not the word British English normally uses for a TV schedule.

Tech exception

Even in UK technical writing, a hard refers to computer storage, not an optical disc.

Tech exception

A UK software product's settings screen would still show a 'Save changes?' box, even though British English elsewhere uses 'dialogue' for a conversation.

Tech exception

British English writes 'programme' for a conference schedule, but for the thing a compiler compiles, it writes .

Tech exception

A UK IT support article about backing up files to an external hard uses the computing spelling, not the optical-media one.

Ready to practice your English at work?

Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.

Try Lingua-e for free
Roxana Lafuente

Written by

Roxana Lafuente

Lingua-e's founder

Roxana Lafuente is a software engineer with 8+ years of experience. At the beginning of her career, even though she had already passed the First Certificate in English, she still froze every time she had to speak up in the daily standup. That was a gap nobody was fixing. After 2,000+ standups, she figured out what actually builds fluency: practice that looks like your real work. She built Lingua-e so other developers wouldn't have to take the long road to feel confident working in an international development environment.