doc: fixup alignment of warning subsection

Subsection was accidentally aligned with the wrong event. PR-URL: #51374 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Matthew Aitken <[email protected]> Reviewed-By: Tierney Cyren <[email protected]> Reviewed-By: Harshitha K P <[email protected]>
nodejs · Feb 15, 2024 · fabd5c4 · fabd5c4
1 parent 9da0926
commit fabd5c4
Showing 1 changed file with 12 additions and 12 deletions.
diff --git 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'`
-
-<!-- YAML
-added:
-  - v16.2.0
-  - v14.18.0
--->
-
-* `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'`
+
+<!-- YAML
+added:
+  - v16.2.0
+  - v14.18.0
+-->
+
+* `worker` {Worker} The {Worker} that was created.
+
+The `'worker'` event is emitted after a new {Worker} thread has been created.
+
 ### Signal events
 
 <!--type=event-->