Skip to content

[css-env-1] use standardized spelling #2626

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

Closed
wants to merge 1 commit into from
Closed

[css-env-1] use standardized spelling #2626

wants to merge 1 commit into from

Conversation

jonathantneal
Copy link
Contributor

@jonathantneal jonathantneal commented Apr 30, 2018

There were just two spelling issues I noticed when reviewing the env() spec again last night. Thanks for writing this up, by the way! 😄

Also, I see you’ve merely used a “less common spelling”, tho it may not be used in any other specs? https://www.merriam-webster.com/dictionary/tho

@jonathantneal jonathantneal changed the title [css-env-1] fix spelling errors [css-env-1] use more formal spelling Apr 30, 2018
@jonathantneal jonathantneal changed the title [css-env-1] use more formal spelling [css-env-1] use standardized spelling Apr 30, 2018
@tabatkins
Copy link
Member

"tho" and "thru" are becoming commonplace words, and I actively advocate for their usage. They do show up in other specs, tho @fantasai tends to rewrite them if she edits the text. ^_^

@tabatkins tabatkins closed this Apr 30, 2018
@tabatkins
Copy link
Member

(and I'll note that MW says that they appear in "some technical journals", which is close enough to a description of the CSS specs ^_^)

@AmeliaBR
Copy link
Contributor

I would strongly argue for merging this PR.

For English language learners, and anyone else with reading difficulties, non-standard spelling is an unnecessary extra hurdle.

@AmeliaBR AmeliaBR reopened this Apr 30, 2018
@tabatkins
Copy link
Member

If and when this draft gets officially accepted, we can think about it. For now, it's a valid spelling and the way my fingers spell it by default. I'm keeping it.

@tabatkins tabatkins closed this Apr 30, 2018
@svgeesus
Copy link
Contributor

svgeesus commented May 1, 2018

this isn't really the appropriate venue for pushing your ideas on the future evolution of the English language.

@svgeesus svgeesus reopened this May 1, 2018
@tabatkins
Copy link
Member

tabatkins commented May 1, 2018

~ it's an unofficial draft ~

@tabatkins tabatkins closed this May 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants