GeezerVison

Is removing the reference to the unref() documentation intentional?

Yes although it wasn't an easy decision. The choices were:

• Use wording that isn't straightforward simply so we can include unref() by itself and link that to the net docs. (This is what the existing text does.)
• Use the simple/straightforward wording here but add a possibly-confusing link for process.stdin.unref() to the net doc description of unref().
• Use the simple/straightforward wording here that tells the user what they need to know, and don't bother with a link to unref(). At a later date, address the fact that our docs can be non-intuitive. If I find process.stdin.unref() mentioned in code or a tutorial, good luck finding it in the docs. I'm not sure what the solution is, but I think we should solve it. We should not be relying on linking every mention to a surprising place.