-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix some little typos... #44
Conversation
* capitalize 'REST', 'API', 'WebSocket', 'QoS', 'URL' and 'URI' consistently * use 'Events API' consistently to refer to the REST API * use back-ticks consistently e.g. to format JSON field names/examples within sentences * format JSON message examples more consistently * reduce use of 'will' and 'will be' to talk about the spec's defined behaviours, replacing with 'must' or, most often, just 'is' (there are still more...) * remove trailing double spaces (which force a break) where redundant
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.
Looks good to me, but it would be good for @cristian-recoseanu to have a look before merging as Cristian prepared the original documentation (I am ok with the schema changes)
Can we please go with "temperature" rather than "Temperature" |
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.
LGTM
….x, addressing review comment #44 (comment) to use lowercase 'temperature' in example event types.
Resolves #40, and the 'number/Temperature' examples referred to in #30, and
If the above tweaks are too many, we can adjust the PR...