From 9147e21f4053279db795a9f0b4fb8e0bc1b11d20 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Tue, 28 Jun 2016 16:58:58 -0700 Subject: [PATCH] doc: improve usage of `zero`/`0` --- doc/api/http.md | 2 +- doc/api/process.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/http.md b/doc/api/http.md index 493e66b7e7589e..b6f565ffbc74d9 100644 --- a/doc/api/http.md +++ b/doc/api/http.md @@ -585,7 +585,7 @@ a listener for the `'listening'` event. See also [`net.Server.listen(path)`][]. Begin accepting connections on the specified `port` and `hostname`. If the `hostname` is omitted, the server will accept connections on any IPv6 address (`::`) when IPv6 is available, or any IPv4 address (`0.0.0.0`) otherwise. Use a -port value of zero to have the operating system assign an available port. +port value of `0` to have the operating system assign an available port. To listen to a unix socket, supply a filename instead of port and hostname. diff --git a/doc/api/process.md b/doc/api/process.md index 34738d76ad3020..e8ec8a69a63ea6 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -183,7 +183,7 @@ code without properly recovering from the exception can cause additional unforeseen and unpredictable issues. Exceptions thrown from within the event handler will not be caught. Instead the -process will exit with a non zero exit code and the stack trace will be printed. +process will exit with a non-zero exit code and the stack trace will be printed. This is to avoid infinite recursion. Attempting to resume normally after an uncaught exception can be similar to