From fabd5c4b2129682de88bbc3881d286f5e3b8347b Mon Sep 17 00:00:00 2001 From: James M Snell Date: Fri, 5 Jan 2024 11:33:19 -0800 Subject: [PATCH] doc: fixup alignment of warning subsection Subsection was accidentally aligned with the wrong event. PR-URL: https://github.com/nodejs/node/pull/51374 Reviewed-By: Luigi Pinca Reviewed-By: Marco Ippolito Reviewed-By: Matthew Aitken Reviewed-By: Tierney Cyren Reviewed-By: Harshitha K P --- doc/api/process.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/api/process.md b/doc/api/process.md index f0ce10fa9f071a..a4296b6d974d94 100644 --- a/doc/api/process.md +++ b/doc/api/process.md @@ -650,18 +650,6 @@ of the custom deprecation. The `*-deprecation` command-line flags only affect warnings that use the name `'DeprecationWarning'`. -### Event: `'worker'` - - - -* `worker` {Worker} The {Worker} that was created. - -The `'worker'` event is emitted after a new {Worker} thread has been created. - #### Emitting custom warnings See the [`process.emitWarning()`][process_emit_warning] method for issuing @@ -690,6 +678,18 @@ A few of the warning types that are most common include: that will be ignored rather than treated as an error. One example is use of the HTTP response status message when using the HTTP/2 compatibility API. +### Event: `'worker'` + + + +* `worker` {Worker} The {Worker} that was created. + +The `'worker'` event is emitted after a new {Worker} thread has been created. + ### Signal events