docs: be specific about the unit of maxBuffer

[timruffles]

It's nice to be specific about units in docs.

[cjihrig]

I'm in favor of specifying the units. Personally, I think it would be better if the existing sentence:

maxBuffer specifies the largest amount of data (in bytes) allowed on stdout or stderr - if this value is exceeded then the child process is killed.

Was used, possibly with minor edits, as the description of the option. maxBuffer {Number} Max bytes (Default: 200*1024) doesn't explain much, and the actual description of what maxBuffer does is only given for exec(), meaning that readers have to jump around the docs.

[a0viedo]

Hey @timruffles could you re-submit this PR to https://github.com/iojs/io.js? Someone could adopt it for you if you are not interested.

[timruffles]

@cjihrig good call, have updated.

@a0viedo will do

[timruffles]

@a0viedo done

[cjihrig]

Please wrap lines at 80 characters. Then, LGTM.

[timruffles]

done

[cjihrig]

@geek PTAL

[geek]

@timruffles looks good... interested in resubmitting after a merge with the current master? Master has changed since you first submitted and the patch doesn't apply nicely :)

[jasnell]

Already landed in nodejs/node. Going to go ahead and close this here. We can cherry pick the io.js commit back to v0.12 if necessary. Thanks for the PR!