etcher: README.md doesn't match "style guide"
According to https://github.com/resin-io/docs#style-manual resin.io shouldn’t be capitalised, whereas README.md in this repo currently says “the Resin.io team”.
I won’t submit a PR to fix this myself, because it’s unclear whether “the Resin.io team” should be updated to “the resin.io team” or “the resin team”.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 23 (22 by maintainers)
Commits related to this issue
- style: refer to Resin.io as resin.io, according to the style manual > For all, lower-case capitalization unless beginning a sentence (Ex. I > like resin.io. Resin.io is great.) See: https://github.c... — committed to balena-io/etcher by deleted user 8 years ago
- chore: update package.json description to match README.md Both the README.md and the repository description say "Flash OS images to SD cards & USB drives, safely and easily.", while `package.json` cu... — committed to balena-io/etcher by deleted user 8 years ago
- chore: update package.json and README.md to match repo description Repository description says "Flash OS images to SD cards & USB drives, safely and easily.", while `package.json` currently says "An ... — committed to balena-io/etcher by deleted user 8 years ago
- chore: update package.json and README.md to match repo description (#824) Repository description says "Flash OS images to SD cards & USB drives, safely and easily.", while `package.json` currently s... — committed to balena-io/etcher by deleted user 8 years ago
- style: refer to Resin.io as resin.io, according to the style manual > For all, lower-case capitalization unless beginning a sentence (Ex. I > like resin.io. Resin.io is great.) See: https://github.c... — committed to balena-io/etcher by deleted user 8 years ago
- style: refer to Resin.io as resin.io, according to the style manual (#823) > For all, lower-case capitalization unless beginning a sentence (Ex. I > like resin.io. Resin.io is great.) See: https:... — committed to balena-io/etcher by deleted user 8 years ago
I’ve updated the Gitter description!
Note from my pedant side: “safe & easy” should be “safely and easily” if that one is going to go into more widespread use. Alternately, it could be “It’s safe and easy”.