From 30fc6a5449e1e1f30c9e60776e60879a5ae1e54c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Nie=C3=9Fen?= Date: Tue, 29 Oct 2019 11:32:10 -0300 Subject: [PATCH] doc: change node.js to Node.js per guideline --- doc/async_operations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/async_operations.md b/doc/async_operations.md index 8506e1639..064a9c50f 100644 --- a/doc/async_operations.md +++ b/doc/async_operations.md @@ -4,7 +4,7 @@ Node.js native add-ons often need to execute long running tasks and to avoid blocking the **event loop** they have to run them asynchronously from the **event loop**. In the Node.js model of execution the event loop thread represents the thread -where JavaScript code is executing. The node.js guidance is to avoid blocking +where JavaScript code is executing. The Node.js guidance is to avoid blocking other work queued on the event loop thread. Therefore, we need to do this work on another thread.