From 83909e04c0b9e985a84a15301f9021d00226d859 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Sun, 12 Jan 2020 07:25:50 -0800 Subject: [PATCH] doc: standardize on "host name" in fs.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/fs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/fs.md b/doc/api/fs.md index a4b7e81ecde301..736237f1f905b4 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -175,9 +175,9 @@ fs.readFileSync(fileUrl); Using WHATWG [`URL`][] objects might introduce platform-specific behaviors. -On Windows, `file:` URLs with a hostname convert to UNC paths, while `file:` +On Windows, `file:` URLs with a host name convert to UNC paths, while `file:` URLs with drive letters convert to local absolute paths. `file:` URLs without a -hostname nor a drive letter will result in a throw: +host name nor a drive letter will result in a throw: ```js // On Windows : @@ -199,7 +199,7 @@ fs.readFileSync(new URL('file:///c/p/a/t/h/file')); `file:` URLs with drive letters must use `:` as a separator just after the drive letter. Using another separator will result in a throw. -On all other platforms, `file:` URLs with a hostname are unsupported and will +On all other platforms, `file:` URLs with a host name are unsupported and will result in a throw: ```js