doc: heading levels should only increment by one

These are flagged by Markdownlint MD001 rule.

PR-URL: https://github.com/nodejs/node/pull/29331
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
This commit is contained in:
Nick Schonning 2019-08-27 00:07:14 -04:00 committed by Rich Trott
parent 17a697c794
commit 9e8edb0d79
2 changed files with 4 additions and 4 deletions

View File

@ -110,7 +110,7 @@ release.
</tr>
</table>
### Notes
## Notes
* The [Node.js Long Term Support plan](https://github.com/nodejs/Release) covers
LTS releases.

View File

@ -6,14 +6,14 @@ when analyzing its memory (either on a running process or a core dump). Node.js
provides this metadata in its builds for V8 and Node.js internal structures.
### V8 Postmortem metadata
## V8 Postmortem metadata
V8 prefixes all postmortem constants with `v8dbg_`, and they allow inspection of
objects on the heap as well as object properties and references. V8 generates
those symbols with a script (`deps/v8/tools/gen-postmortem-metadata.py`), and
Node.js always includes these constants in the final build.
### Node.js Debug Symbols
## Node.js Debug Symbols
Node.js prefixes all postmortem constants with `nodedbg_`, and they complement
V8 constants by providing ways to inspect Node.js-specific structures, like
@ -22,7 +22,7 @@ V8 constants by providing ways to inspect Node.js-specific structures, like
`src/node_postmortem_metadata.cc`, and most of them are calculated at compile
time.
#### Calculating offset of class members
### Calculating offset of class members
Node.js constants referring to the offset of class members in memory
are calculated at compile time.