Guía de inglés para developers + ejercicios gratis
Ortografía UK vs US de términos técnicos: ¿color o colour, program o programme?
21 de octubre de 2026
¿Se escribe 'color' o 'colour'? ¿'Organize' u 'organise'? Ambas formas son inglés correcto, solo pertenecen a dialectos distintos. Esta guía cubre los patrones de ortografía que distinguen al inglés británico del americano, más las excepciones técnicas donde la ortografía del dialecto 'equivocado' es en realidad la única que funciona, como CSS, que solo acepta 'color'. Después, 27 ejercicios gratuitos para practicar cómo distinguirlos.
Spelling Patterns
Ortografía US vs UK
La mayoría de las diferencias de ortografía entre US y UK siguen un puñado de patrones predecibles. Una vez que conoces el patrón, generalmente puedes adivinar la ortografía del otro dialecto, incluso para una palabra que nunca viste escrita así.
| Ortografía US | Ortografía UK | Patrón | Ejemplo |
|---|---|---|---|
| color | colour | -or / -our | “Pick a background color that passes contrast checks.” |
| behavior | behaviour | -or / -our | “This flag changes the default behavior of the retry logic.” |
| favorite | favourite | -or / -our | “Users can star a repo to add it to their favorites.” |
| flavor | flavour | -or / -our | “The free and paid tiers are just two build flavors of the same app.” |
| customize | customise | -ize / -ise | “You can customize the keyboard shortcuts in the settings panel.” |
| organize | organise | -ize / -ise | “We organize our components by feature instead of by file type.” |
| initialize | initialise | -ize / -ise | “The constructor is where you initialize the object's starting state.” |
| serialize | serialise | -ize / -ise | “We serialize the response as JSON before sending it over the wire.” |
| synchronize | synchronise | -ize / -ise | “This job runs nightly to synchronize the cache with the database.” |
| optimize | optimise | -ize / -ise | “Profile the code first, then optimize the slowest function.” |
| minimize | minimise | -ize / -ise | “Batch the requests to minimize the number of round trips.” |
| authorize | authorise | -ize / -ise | “The middleware checks the token before it will authorize the request.” |
| analyze | analyse | -yze / -yse | “Run the profiler to analyze where the memory leak is coming from.” |
| catalog | catalogue | -og / -ogue | “The design system has a full catalog of reusable components.” |
| center | centre | -er / -re | “Use flexbox to center the modal both vertically and horizontally.” |
| fiber | fibre | -er / -re | “The new data center is connected by a dedicated fiber line.” |
| canceled | cancelled | -l / -ll | “The deploy was canceled halfway through the rollout.” |
| modeling | modelling | -l / -ll | “We spent the sprint modeling the new database schema.” |
| traveling | travelling | -l / -ll | “The packet is still traveling through three more hops before it arrives.” |
| gray | grey | other | “Disabled buttons are shown in gray in this design system.” |
| license | licence | other | “This repository is released under the MIT license.” |
Tech Exceptions
Cuando el patrón no aplica
Un puñado de términos técnicos no siguen la división habitual, ya sea porque la tecnología misma impone una ortografía, o porque las convenciones de software se asentaron en una sola forma sin importar el dialecto. Son las que los developers escriben mal en ambas direcciones.
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.
Puntos clave
- El inglés americano prefiere terminaciones más cortas: -or, -ize, -er, -og. El inglés británico prefiere -our, -ise, -re, -ogue: color/colour, organize/organise, center/centre, catalog/catalogue.
- CSS solo acepta la ortografía americana 'color'. 'Colour' no es válido y el navegador lo ignora en silencio, incluso en código escrito por un developer británico.
- 'Program' significa software en ambos dialectos. El inglés británico solo usa 'programme' para un programa de TV, una conferencia o una carrera universitaria, nunca para código.
- 'Disk' es almacenamiento de computadora en ambos dialectos. El inglés británico reserva 'disc' para medios ópticos como un CD o DVD, no para un disco duro.
- Ambas ortografías se entienden en todas partes, así que elige un dialecto y mantén la consistencia dentro del mismo documento, README o código base.
Inglés para developers
Práctica: ortografía UK vs US
Cada oración describe dónde la leerías: un blog UK, un changelog US, una descripción de PR. Elige la ortografía que corresponde.
Spelling Patterns
↑ Volver a la teoríaA UK-based blog post about this component's would describe how it reacts to user clicks.
An American engineering blog would write: 'Pick a background that passes contrast checks.'
In a UK team's app store listing, users 'star a repo to add it to their '.
An American Android developer would say: 'The free and paid tiers are two build of the same app.'
A US engineering doc would say: 'You can the keyboard shortcuts in the settings panel.'
A UK README would say: 'We our components by feature instead of by file type.'
A UK code comment would read: 'The constructor is where you the object's starting state.'
An American PR description would say: 'We the response as JSON before sending it over the wire.'
A UK changelog entry would read: 'This job runs nightly to the cache with the database.'
An American performance ticket would say: 'Profile the code first, then the slowest function.'
A UK architecture doc would read: 'Batch the requests to the number of round trips.'
An American security doc would say: 'The middleware checks the token before it will the request.'
An American debugging guide would say: 'Run the profiler to where the memory leak is coming from.'
A UK design system's docs would read: 'We keep a full of reusable components.'
An American CSS tutorial would say: 'Use flexbox to the modal both vertically and horizontally.'
A UK networking article would read: 'The new data centre is connected by a dedicated line.'
A UK incident report would say: 'The deploy was halfway through the rollout.'
An American sprint summary would say: 'We spent the sprint the new database schema.'
A UK networking comment would read: 'The packet is still through three more hops before it arrives.'
An American design system doc would say: 'Disabled buttons are shown in in this design system.'
A UK open-source repo's README would read: 'This repository is released under the MIT .'
Tech Exceptions
↑ Volver a la teoríaThis CSS declaration only works with one spelling, no matter which team wrote it: : #1a1a1a;
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.
Even in UK technical writing, a hard refers to computer storage, not an optical disc.
A UK software product's settings screen would still show a 'Save changes?' box, even though British English elsewhere uses 'dialogue' for a conversation.
British English writes 'programme' for a conference schedule, but for the thing a compiler compiles, it writes .
A UK IT support article about backing up files to an external hard uses the computing spelling, not the optical-media one.
¿Listo para practicar tu inglés en el trabajo?
Lingua-e tiene ejercicios interactivos basados en conversaciones reales de developers: standups, code reviews, retrospectivas y más. Practica hasta que salga solo.
Prueba Lingua-e gratis
Escrito por
Roxana LafuenteFundadora de Lingua-e
Roxana Lafuente es ingeniera de software con más de 8 años de experiencia. Al comienzo de su carrera, aunque ya había aprobado el First Certificate in English, se bloqueaba cada vez que tenía que hablar en el standup diario. Era un problema que nadie estaba resolviendo. Después de más de 2.000 standups, descubrió qué es lo que realmente construye la fluidez: practicar situaciones que se parecen a tu trabajo real. Creó Lingua-e para que otros developers no tuvieran que tomar el camino largo para sentirse seguros trabajando en un entorno de desarrollo internacional.