-
Notifications
You must be signed in to change notification settings - Fork 117
extension point clarification #1447
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
extension point clarification #1447
Conversation
removed "more formally defined"
index.html
Outdated
extension points. While some implementers signalled interest in these properties, | ||
their inclusion in this specification was considered to be premature. Some of these | ||
extension points were originally defined in previous versions of this | ||
specification, whilst others were not. It is important to note that none of these properties | ||
are defined by this specification. Consequently, implementers are cautioned that usage of these | ||
properties is considered experimental. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
W3C uses US English.
extension points. While some implementers signalled interest in these properties, | |
their inclusion in this specification was considered to be premature. Some of these | |
extension points were originally defined in previous versions of this | |
specification, whilst others were not. It is important to note that none of these properties | |
are defined by this specification. Consequently, implementers are cautioned that usage of these | |
properties is considered experimental. | |
extension points. While some implementers signaled interest in these properties, | |
their inclusion in this specification was considered to be premature. Some of | |
these extension points were originally defined in previous versions of this | |
specification, while others were not. It is important to note that none of these | |
properties are defined by this specification. Consequently, implementers are | |
cautioned that use of these properties is considered experimental. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signaled and signalled are both English terms. Signaled is predominantly used in 🇺🇸 American (US) English ( en-US ) while signalled is predominantly used in 🇬🇧 British English (used in UK/AU/NZ) ( en-GB ). (see https://sapling.ai/usage/signaled-vs-signalled)
While and whilst are the same, but whilst is a bit more formal (according to one famous grammar book). (see https://www.ielts-simon.com/ielts-help-and-english-pr/2010/11/ielts-grammar-while-whilst-whereas-as.html)
I gladly accept replacing usage by use. Note that the original text contained usage and was not edited by this PR.
Note that the rest of the proposed changes are line feeds in different places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://www.grammarly.com/blog/while-vs-whilst/
Typically, Brits use whilst and Americans use while.
https://thecontentauthority.com/blog/signalled-vs-signaled
The word “signalled” is the British spelling of the word “signaled”.
Again, W3C uses US English. In other words, the changes to "signaled" and "while" are appropriate.
And usage to use
Editorial, multiple reviews, changes requested and made, no objections, merging. |
removed "more formally defined"
Preview | Diff