Skip to content

Commit 6e9f0da

Browse files
TrottMylesBorins
authored andcommitted
doc: standardize on "host name" in async_hooks.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 <luigipinca@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
1 parent c8aa08e commit 6e9f0da

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/api/async_hooks.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -296,7 +296,7 @@ of propagating what resource is responsible for the new resource's existence.
296296
`resource` is an object that represents the actual async resource that has
297297
been initialized. This can contain useful information that can vary based on
298298
the value of `type`. For instance, for the `GETADDRINFOREQWRAP` resource type,
299-
`resource` provides the hostname used when looking up the IP address for the
299+
`resource` provides the host name used when looking up the IP address for the
300300
host in `net.Server.listen()`. The API for accessing this information is
301301
currently not considered public, but using the Embedder API, users can provide
302302
and document their own resource objects. For example, such a resource object
@@ -383,8 +383,8 @@ Timeout(7) -> TickObject(6) -> root(1)
383383
```
384384

385385
The `TCPSERVERWRAP` is not part of this graph, even though it was the reason for
386-
`console.log()` being called. This is because binding to a port without a
387-
hostname is a *synchronous* operation, but to maintain a completely asynchronous
386+
`console.log()` being called. This is because binding to a port without a host
387+
name is a *synchronous* operation, but to maintain a completely asynchronous
388388
API the user's callback is placed in a `process.nextTick()`.
389389

390390
The graph only shows *when* a resource was created, not *why*, so to track

0 commit comments

Comments
 (0)