These are just a pair of minor things I came across while working on #78 and #79
Just a minor typo in the samples
A slight improvement to error reporting consistency when config.fsx can't be loaded. Presently we get the generic error message that something went wrong - but the Error case we're discarding on :461 actually carries valuable information generated on :282
These are just a pair of minor things I came across while working on #78 and #79
config.fsx
can't be loaded. Presently we get the generic error message that something went wrong - but the Error case we're discarding on :461 actually carries valuable information generated on :282