doc: move v8.stopCoverage() to expected location in doc

Trott · targos · commit ddc24b21058f · 2021-07-11T09:46:19.000+02:00
PR-URL: #39212 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Harshitha K P <harshitha014@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
diff --git a/doc/api/v8.md b/doc/api/v8.md
@@ -223,6 +223,19 @@ v8.setFlagsFromString('--trace_gc');
 setTimeout(() => { v8.setFlagsFromString('--notrace_gc'); }, 60e3);
 ```
 
+## `v8.stopCoverage()`
+
+<!-- YAML
+added:
+  - v15.1.0
+  - v12.22.0
+-->
+
+The `v8.stopCoverage()` method allows the user to stop the coverage collection
+started by [`NODE_V8_COVERAGE`][], so that V8 can release the execution count
+records and optimize code. This can be used in conjunction with
+[`v8.takeCoverage()`][] if the user wants to collect the coverage on demand.
+
 ## `v8.takeCoverage()`
 
 <!-- YAML
@@ -240,19 +253,6 @@ by [`NODE_V8_COVERAGE`][].
 When the process is about to exit, one last coverage will still be written to
 disk unless [`v8.stopCoverage()`][] is invoked before the process exits.
 
-## `v8.stopCoverage()`
-
-<!-- YAML
-added:
-  - v15.1.0
-  - v12.22.0
--->
-
-The `v8.stopCoverage()` method allows the user to stop the coverage collection
-started by [`NODE_V8_COVERAGE`][], so that V8 can release the execution count
-records and optimize code. This can be used in conjunction with
-[`v8.takeCoverage()`][] if the user wants to collect the coverage on demand.
-
 ## `v8.writeHeapSnapshot([filename])`
 <!-- YAML
 added: v11.13.0
