Streams integration: change from .wait() to .ready

[domenic]

I did a scan and .wait() is only used in notes and in examples so this is pretty minor. But in whatwg/streams#243 we changed from a side-effecting .wait() to a passive .ready in the public API.

[ClaesNilsson]

Ok, thanks for spotting this Domenic. I'll replace .wait() with .ready in the examples and comments. Furthermore I see in whatwg/streams#245 that .ready is fulfill-only. So in the examples in the TCP and UDP Socket API specification errors must be handled in another way than with a promise reject function for .ready. I guess that I just can remove the promise reject handling and rely on mySocket.closed... handling to detect for example situations like loss of network contact.

[domenic]

Oh yeah, sorry for not noticing that too.

I guess that I just can remove the promise reject handling and rely on mySocket.closed... handling to detect for example situations like loss of network contact.

That was exactly the reasoning :)

[ClaesNilsson]

I fill that and make a PR.

[ClaesNilsson]

Looks ok? #84

[ClaesNilsson]

Closed with #84