Skip to content

Conversation

@leonerd
Copy link
Contributor

@leonerd leonerd commented Dec 5, 2025

In my defence, I am British, so don't colour me an idiot please ;)

  • This set of changes does not require a perldelta entry.

@leonerd leonerd force-pushed the fix-en_GB-spelling branch from 53d1c79 to eac64c3 Compare December 5, 2025 18:29
@leonerd leonerd merged commit cb60726 into Perl:blead Dec 5, 2025
33 checks passed
@leonerd leonerd deleted the fix-en_GB-spelling branch December 6, 2025 00:38
@karenetheridge
Copy link
Member

Why did this need to be done? Was there a spell check test somewhere that failed?

As a non-US english speaker, I take umbrage at the obligation to conform.

@Grinnz
Copy link
Contributor

Grinnz commented Dec 6, 2025

To keep a consistent voice in our documentation: https://perldoc.perl.org/perldocstyle#Choice-of-language:-American-English

@Grinnz
Copy link
Contributor

Grinnz commented Dec 6, 2025

or in this case, our core warning messages, which has even broader effects.

@khwilliamson
Copy link
Contributor

khwilliamson commented Dec 6, 2025 via email

@leonerd
Copy link
Contributor Author

leonerd commented Dec 7, 2025

My thinking in this case was that while I was editing something else in perldiag.pod, I found there there were plenty of "unrecognized" messages but only a single "unrecognised", and that single odd one was a message I'd added recently, still experimental. So I felt it would be good to make them all conform to the same pattern.

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.

5 participants