Address typographical issues from Reviewer 1.

snim2 commented 8 years ago

Partly addresses #126

[ ] Rules 4 and 5 seem like variations on the same rule -- keeping the data accessible. It would be helpful to differentiate these rules a bit more.
[X] Line 21: is a good advice => is good advice
[ ] Line 136: States that an example of machine readable open format that would not be easy to process include Microsoft word, but in the preceding rule (Rule 4) it states that Microsoft excel is not an open format. Perhaps just keep PDF as the example.
[ ] Lines 140-144: discussing source code doesn't really fit in this section. Perhaps move these lines to the section about metadata (Rule 7).
[X] Line 147: variable is a column => variable as a column
[X] Line 147-148: unit is a table => unit as a table
[X] Line 161: standards-compliant data, it is easier to build
[ ] Line 164: The section on semantic versioning is well received
[X] Line 200: meta-data in in well => meta-data in well
[X] Line 201: Extraneous close paren ) after JSON
[ ] Line 244: Seems like an appeal to authority. Replace explicit reference to Kristen Briney
[ ] Line 245: Include a caution with respect to Rule 8 (ensure that the offsite "cloud" storage is as secure as the primary storage)
[X] Line 311: include oxford comma "animals, fungi, and microbes"
[X] Line 337-338: ways to programatically query databases through

snim2 commented 8 years ago

Do you want me to bring this up to date with master?

emhart commented 8 years ago

Sure @snim2 that would be great.

snim2 commented 8 years ago

OK, all done.

emhart / 10-simple-rules-data-storage