doc: standardize on "host name" in deprecations.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: #31326 Refs: #31073 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
nodejs · Jan 16, 2020 · 8055f78 · 8055f78
1 parent 6e9f0da
commit 8055f78
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/doc/api/deprecations.md b/doc/api/deprecations.md
@@ -2270,7 +2270,7 @@ The `_handle` property has been removed because improper use of the native
 object can lead to crashing the application.
 
 <a id="DEP0118"></a>
-### DEP0118: `dns.lookup()` support for a falsy hostname
+### DEP0118: `dns.lookup()` support for a falsy host name
 <!-- YAML
 changes:
   - version: v11.0.0
@@ -2280,7 +2280,7 @@ changes:
 
 Type: Runtime
 
-Previous versions of Node.js supported `dns.lookup()` with a falsy hostname
+Previous versions of Node.js supported `dns.lookup()` with a falsy host name
 like `dns.lookup(false)` due to backward compatibility.
 This behavior is undocumented and is thought to be unused in real world apps.
 It will become an error in future versions of Node.js.