@RaisinTen - Thanks for the review!

Could you please address this review comment from a previous PR attempt to fix the related issue: #36458 (comment)?

I did incorporate the edits into an existing section instead of making a new section i.e. readline.createInterface(options) section. Am I missing something else?

The wait on the readable stream can also be ended by these calls:

readable.destroy();
readable.pause();
readable.unshift(null);

Should we also document these here?
IMO adding docs for these here seems a little out of place as they are already documented at https://nodejs.org/api/stream.html#stream_class_stream_readable. I think it would be more appropriate if we could mention this group of calls which can end the wait on the readable stream in the readable stream docs itself instead of everywhere an instance of the Readable class is used.

@RaisinTen Sure, we could do it in both places (readable and readline). Do you think it makes sense to add the following in the readable section? I can make that change

The wait on the readable stream can also be ended by these calls:
readable.destroy();
readable.pause();
readable.unshift(null);

The wait on the readable stream can also be ended by these calls:
Should we also document these here?

FWIW I don't think it's necessary: I think it's irrelevant to a user trying to interface with stdin that there are several ways to "make the program not hang". We don't have to be thorough on how the stream API work in the readline API documentation.

Landed in 7980d7c