Skip to content

[selectors-4] Fix typo #1886

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 17, 2017
Merged

[selectors-4] Fix typo #1886

merged 1 commit into from
Oct 17, 2017

Conversation

kristoforsalmin
Copy link

I've replaced a word with more formal equivalent.

@fantasai fantasai merged commit 5a2a437 into w3c:master Oct 17, 2017
@tabatkins
Copy link
Member

(Fine with it being merged, but that wasn't a typo - I spell the word that way intentionally. English spelling is terrible broken in some places.)

@frivoal
Copy link
Collaborator

frivoal commented Oct 18, 2017

https://www.youtube.com/watch?v=dz4Ps55Rx40&feature=youtu.be&t=65

@kristoforsalmin
Copy link
Author

@tabatkins I'm sorry, didn't know that. I thought it'd be a good idea to use either of those forms consistently.

@bradkemper
Copy link
Contributor

We also have “cough”, not “coff”. “Tough”, not “tuff”. “Rough”, not “ruff”. “Enough”, not “enuff”. “Thorough”, not “thurrow”. “Borough” spelled differently than “burrow”. “Bureau”, not “byurrow”. “Align”, not “uhlline”. And countless other words with non-phonetic confusing spellings.

Our specs should stick to English spelling as it is, not as we wish it was.

@tabatkins
Copy link
Member

Spelling drifts with usage. ^_^ Like I said, I'm fine with it being merged, but I'm gonna keep using it myself.

@fantasai
Copy link
Collaborator

fantasai commented Jan 1, 2018

@racse1 As the other co-editor, I agree with @bradkemper and appreciate the fix.

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