doc: fix two doc errors

[Fishrock123]

Found these while digging around.

process.stdout always blocks as of
20176a9

WritableState.buffer is getBuffer() as of
9158666

cc @orangemocha for the first one. I'm unaware of a case where it wouldn't block now.

[Fishrock123]

I guess also cc @chrisdickinson for the latter.

[orangemocha]

For the first one: I believe that's correct. LGTM

[evanlucas]

LGTM

[tschaub]

For the first one: I believe that's correct. LGTM

Having the docs say that process.stdout.write() is always blocking makes it sound like writes are synchronous. This doesn't look to be the case (see #2972). Would it make sense to update the docs to say that writes are always asynchronous? This seems more pertinent to users of process.stdout.write() than whether or not it blocks.

[Fishrock123]

Would it make sense to update the docs to say that writes are always asynchronous? This seems more pertinent to users of process.stdout.write() than whether or not it blocks.

Ugh, this is way to confusing.

The call is asynchronous as in the actual write will (likely?) not occur during the function being called. It will later block the process to do the write, however. It is likely to be done in the I/O phase of that tick I believe.

That being said, I think there is some js-side data that is updated synchronously which is normally what you'd be checking from the same process.

cc @bnoordhuis who likely knows how the heck this actually works

[Fishrock123]

Refs: #2972 (comment)