Various comments and suggestions

[matthijskooijman]

Some useful feedback from IRC, which I didnt' want to get lost in history.

11:46:35 < mlaci> just reading https://docs.pinocc.io/scoutcommands.html
          and wondering whether power.enablevcc is supposed to
          consume additional power
12:00:41 < mlaci> the default torch color could be mentioned
12:01:50 < mlaci> for pin.makeinput it could be mentioned that this is
          the default state (with pull-ups enabled, i assume)
12:04:01 < mlaci> the choice of d2-d8 for pin.report.digital is quite
          arbitrary. any plans to make a port like "a", "b",
          "c", ... specifiable?
12:09:42 < mlaci> regarding scout.daisy daisy is a rather confusing word
          to me in this context. have you considered scout.wipe?
          sounds so much more natural to 
                          me.
12:12:00 < mlaci> also, scout.reboot would be more intuitive than
          scout.boot.  boot implies that the scout hasn't booted
          up yet even if it's obvious for the technical minded.
12:14:33 < mlaci> regarding hq.settoken wondering what happens if the
          token of two pinoccios are the same, even from
          different users? would those pinoccios clash?
12:19:02 < mlaci> is the event handler enabled by default? if so it
                  could be mentioned in events.start
12:49:10 < mlaci> shouldn't temperature() provide a float, not an int?
12:54:54 < mlaci> for mesh.setdatarate() it'd be useful to know the
                  default data rate.
12:56:01 < mlaci> also, for the example of mesh.setdatarate()
                  mesh.setpower(0) is featured erroneously
12:58:45 < mlaci> it's not clear what value mesh.resetkey() will reset
          the key to. is this some factory key hardwired into
          the firmware?
14:31:59 < mlaci> now I see that the default torch color is green. ok :)
14:32:11 < mlaci> (haven't got my boards yet)
14:42:16 < mlaci> typo at https://docs.pinocc.io/api.html : "vlad uri
                  characters" - i guess it should be "valid"
14:53:22 < mlaci> on https://docs.pinocc.io/api.html you could mention
          http://blog.getpostman.com/ which is a super-useful
          rest client implemented as a chrome app

[matthijskooijman]

Hmm, seems github autoclosed this issue, even though it's only partially resolved. I guess that "resolves part of #9" is a better way to write commit messages than "partially resolves #9", then :-)