Editorial: Fix a few inconsistencies in "GamepadButton Interface"

kri commented 4 years ago

This PR is relatively straightforward. All in all, there were only a couple of editorial changes, all of which in the GamepadButton Interface section:

A few missing commas have been added.
An instance of "value" has been changed to "attribute", because the "pressed attribute" had been specified under that nomenclature, and a property shouldn't be able to mirror a value, but rather mirror another property.
<a> has been used to reference the definition of pressed.
There used to be an instance where both "0" and "zero" would be used in the same sentence. Since both referenced the same value, I've replaced "0" with "zero".
The term "respectively" has been added in a phrase where two numeric values were assigned to two button states in order to avoid confusion.

The following tasks have been completed:

[ ] Modified Web platform tests (link to pull request)

Implementation commitment:

[ ] WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
[ ] Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=)
[ ] Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)

Preview | Diff

marcoscaceres commented 4 years ago

Can I be a pain and ask you to change the “zero” to 0. That better matches the checks.

marcoscaceres commented 4 years ago

Marked as non substantive for IPR from ash-nazg.

kri commented 4 years ago

You're not being a pain at all. :) My reasoning to go for "zero" when given the choice was really just based on the recommendation to spell out integers below 10 in English. Given the technical context, I can see how writing 0 might be favorable here, so I'll happily comply.

I went ahead and force-pushed your requested change. Let me know if there's anything else I can do.

marcoscaceres commented 4 years ago

Thanks @kri. All review feedback is always greatly appreciated.

w3c / gamepad

Editorial: Fix a few inconsistencies in "GamepadButton Interface" #122