FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

docs: convert narrative US spellings to UK English by peter-lawrey · Pull Request #201 · OpenHFT/Java-Thread-Affinity · GitHub

docs: convert narrative US spellings to UK English - #201

Open
peter-lawrey wants to merge 1 commit into
developfrom
sausage/docs-uk-english
Open

docs: convert narrative US spellings to UK English#201
peter-lawrey wants to merge 1 commit into
developfrom
sausage/docs-uk-english

Conversation

Copy link
Copy Markdown
Member

Summary

Documentation uses UK English for narrative text. Standard US technical terms (synchronization, serialization, initialization, finalize, deserialize, normalization) are preserved because that is how they appear in the Java platform and wider ecosystem.

Changes:

  • -or -> -our: behavior, color, favor, flavor, honor, labor, neighbor, endeavor
  • -ize -> -ise for non-technical verbs: organize, recognize, realize, optimize, minimize, maximize, emphasize, utilize, summarize, customize, prioritize, generalize, analyze

Proper nouns (e.g. "Apache License") and third-party paths (e.g. jsr166/) are left alone.

Test plan

  • Diff shows only narrative/spelling swaps.
  • No API or identifier names affected.
  • CI green.

🤖 Generated with Claude Code

Project convention is UK English in documentation. Standard US
technical terms (synchronization, serialization, initialization,
finalize, deserialize, normalization) are kept unchanged because
that is how they appear in the Java platform and wider ecosystem.

Covers: behavior/behaviour, color/colour, favor/flavor/honor/labor,
neighbor/endeavor -> -our forms; and -ize verbs outside the kept
technical set (organize, recognize, realize, optimize, minimize,
maximize, emphasize, utilize, summarize, customize, prioritize,
generalize, analyze) -> -ise forms. Proper names such as Apache
License are untouched.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL