doc: edit addon text about event loop blocking

PR-URL: #36448 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Shelley Vohr <[email protected]>
nodejs · Dec 21, 2020 · 9891811 · 9891811
1 parent acd78d9
commit 9891811
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/api/addons.md b/doc/api/addons.md
@@ -28,10 +28,10 @@ involving knowledge of several components and APIs:
   as interacting with the filesystem, sockets, timers, and system events. libuv
   also provides a threading abstraction similar to POSIX threads for
   more sophisticated asynchronous addons that need to move beyond the
-  standard event loop. Addon authors are encouraged to think about how to
+  standard event loop. Addon authors should
   avoid blocking the event loop with I/O or other time-intensive tasks by
-  off-loading work via libuv to non-blocking system operations, worker threads
-  or a custom use of libuv's threads.
+  offloading work via libuv to non-blocking system operations, worker threads,
+  or a custom use of libuv threads.
 
 * Internal Node.js libraries. Node.js itself exports C++ APIs that addons can
   use, the most important of which is the `node::ObjectWrap` class.