From a1c330f231ad100f0c83c0d3215951096e925c89 Mon Sep 17 00:00:00 2001 From: Kevin Date: Thu, 1 Jun 2017 14:13:37 +0800 Subject: [PATCH] doc: fix typo in async_hooks.md --- doc/api/async_hooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/async_hooks.md b/doc/api/async_hooks.md index 06c8a41a5786f2..c41c9bc8707d33 100644 --- a/doc/api/async_hooks.md +++ b/doc/api/async_hooks.md @@ -278,7 +278,7 @@ Now if we only use `scope` to graph resource allocation we get the following: TTYWRAP(6) -> Timeout(4) -> TIMERWRAP(5) -> TickObject(3) -> root(1) ``` -The `TCPWRAP` isn't part of this graph; evne though it was the reason for +The `TCPWRAP` isn't part of this graph; even though it was the reason for `console.log()` being called. This is because binding to a port without a hostname is actually synchronous, but to maintain a completely asynchronous API the user's callback is placed in a `process.nextTick()`.