From ece70a82883894e090ec29fa1c5f01b3230b6b81 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sun, 12 Jan 2020 07:24:25 -0800 Subject: [PATCH] doc: standardize on "host name" in errors.md Our docs have a mix of "hostname" and "host name" in prose. Let's follow the usage of Unix man pages, RFCs, and most professionally-edited sources, and use "host name" in prose and "hostname" to refer to the command and in code. Lint rule forthcoming. PR-URL: https://github.com/nodejs/node/pull/31326 Refs: https://github.com/nodejs/node/pull/31073 Reviewed-By: Luigi Pinca Reviewed-By: Richard Lau Reviewed-By: James M Snell Reviewed-By: Trivikram Kamat --- doc/api/errors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/errors.md b/doc/api/errors.md index 4d9651be8ddd2a..63d2e1c20d5346 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -1792,7 +1792,7 @@ additional details. ### `ERR_TLS_CERT_ALTNAME_INVALID` -While using TLS, the hostname/IP of the peer did not match any of the +While using TLS, the host name/IP of the peer did not match any of the `subjectAltNames` in its certificate. @@ -1843,7 +1843,7 @@ An attempt was made to renegotiate TLS on a socket instance with TLS disabled. ### `ERR_TLS_REQUIRED_SERVER_NAME` While using TLS, the `server.addContext()` method was called without providing -a hostname in the first parameter. +a host name in the first parameter. ### `ERR_TLS_SESSION_ATTACK`