doc,errors: use code markup/markdown in headers

PR-URL: https://github.com/nodejs/node/pull/31086
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>

1 files changed, 299 insertions, 299 deletions

diff --git a/doc/api/errors.md b/doc/api/errors.md
index 0831b83e01d..88d982fd195 100644
--- a/doc/api/errors.md
+++ b/doc/api/errors.md
@@ -177,7 +177,7 @@ Throwing an error inside the callback **can crash the Node.js process** in most
 cases. If [domains][] are enabled, or a handler has been registered with
 `process.on('uncaughtException')`, such errors can be intercepted.
 
-## Class: Error
+## Class: `Error`
 
 <!--type=class-->
 
@@ -189,7 +189,7 @@ provide a text description of the error.
 All errors generated by Node.js, including all System and JavaScript errors,
 will either be instances of, or inherit from, the `Error` class.
 
-### new Error(message)
+### `new Error(message)`
 
 * `message` {string}
 
@@ -201,7 +201,7 @@ are dependent on [V8's stack trace API][]. Stack traces extend only to either
 (a) the beginning of *synchronous code execution*, or (b) the number of frames
 given by the property `Error.stackTraceLimit`, whichever is smaller.
 
-### Error.captureStackTrace(targetObject\[, constructorOpt\])
+### `Error.captureStackTrace(targetObject[, constructorOpt])`
 
 * `targetObject` {Object}
 * `constructorOpt` {Function}
@@ -237,7 +237,7 @@ function MyError() {
 new MyError().stack;
 ```
 
-### Error.stackTraceLimit
+### `Error.stackTraceLimit`
 
 * {number}
 
@@ -251,7 +251,7 @@ will affect any stack trace captured *after* the value has been changed.
 If set to a non-number value, or set to a negative number, stack traces will
 not capture any frames.
 
-### error.code
+### `error.code`
 
 * {string}
 
@@ -261,7 +261,7 @@ between major versions of Node.js. In contrast, `error.message` strings may
 change between any versions of Node.js. See [Node.js Error Codes][] for details
 about specific codes.
 
-### error.message
+### `error.message`
 
 * {string}
 
@@ -278,7 +278,7 @@ console.error(err.message);
 // Prints: The message
 ```
 
-### error.stack
+### `error.stack`
 
 * {string}
 
@@ -351,14 +351,14 @@ The number of frames captured by the stack trace is bounded by the smaller of
 `Error.stackTraceLimit` or the number of available frames on the current event
 loop tick.
 
-## Class: AssertionError
+## Class: `AssertionError`
 
 * Extends: {errors.Error}
 
 Indicates the failure of an assertion. For details, see
 [`Class: assert.AssertionError`][].
 
-## Class: RangeError
+## Class: `RangeError`
 
 * Extends: {errors.Error}
 
@@ -374,7 +374,7 @@ require('net').connect(-1);
 Node.js will generate and throw `RangeError` instances *immediately* as a form
 of argument validation.
 
-## Class: ReferenceError
+## Class: `ReferenceError`
 
 * Extends: {errors.Error}
 
@@ -394,7 +394,7 @@ Unless an application is dynamically generating and running code,
 `ReferenceError` instances should always be considered a bug in the code
 or its dependencies.
 
-## Class: SyntaxError
+## Class: `SyntaxError`
 
 * Extends: {errors.Error}
 
@@ -414,7 +414,7 @@ try {
 `SyntaxError` instances are unrecoverable in the context that created them –
 they may only be caught by other contexts.
 
-## Class: SystemError
+## Class: `SystemError`
 
 * Extends: {errors.Error}
 
@@ -435,27 +435,27 @@ attempts to read a file that does not exist.
 * `port` {number} If present, the network connection port that is not available
 * `syscall` {string} The name of the system call that triggered the error
 
-### error.address
+### `error.address`
 
 * {string}
 
 If present, `error.address` is a string describing the address to which a
 network connection failed.
 
-### error.code
+### `error.code`
 
 * {string}
 
 The `error.code` property is a string representing the error code.
 
-### error.dest
+### `error.dest`
 
 * {string}
 
 If present, `error.dest` is the file path destination when reporting a file
 system error.
 
-### error.errno
+### `error.errno`
 
 * {number}
 
@@ -467,31 +467,31 @@ On Windows the error number provided by the system will be normalized by libuv.
 To get the string representation of the error code, use
 [`util.getSystemErrorName(error.errno)`][].
 
-### error.info
+### `error.info`
 
 * {Object}
 
 If present, `error.info` is an object with details about the error condition.
 
-### error.message
+### `error.message`
 
 * {string}
 
 `error.message` is a system-provided human-readable description of the error.
 
-### error.path
+### `error.path`
 
 * {string}
 
 If present, `error.path` is a string containing a relevant invalid pathname.
 
-### error.port
+### `error.port`
 
 * {number}
 
 If present, `error.port` is the network connection port that is not available.
 
-### error.syscall
+### `error.syscall`
 
 * {string}
 
@@ -558,7 +558,7 @@ program. For a comprehensive list, see the [`errno`(3) man page][].
   encountered by [`http`][] or [`net`][] — often a sign that a `socket.end()`
   was not properly called.
 
-## Class: TypeError
+## Class: `TypeError`
 
 * Extends {errors.Error}
 
@@ -594,20 +594,20 @@ Errors originating in `crypto` or `tls` are of class `Error`, and in addition to
 the standard `.code` and `.message` properties, may have some additional
 OpenSSL-specific properties.
 
-### error.opensslErrorStack
+### `error.opensslErrorStack`
 
 An array of errors that can give context to where in the OpenSSL library an
 error originates from.
 
-### error.function
+### `error.function`
 
 The OpenSSL function the error originates in.
 
-### error.library
+### `error.library`
 
 The OpenSSL library the error originates in.
 
-### error.reason
+### `error.reason`
 
 A human-readable string describing the reason for the error.
 
@@ -615,7 +615,7 @@ A human-readable string describing the reason for the error.
 ## Node.js Error Codes
 
 <a id="ERR_AMBIGUOUS_ARGUMENT"></a>
-### ERR_AMBIGUOUS_ARGUMENT
+### `ERR_AMBIGUOUS_ARGUMENT`
 
 A function argument is being used in a way that suggests that the function
 signature may be misunderstood. This is thrown by the `assert` module when the
@@ -625,42 +625,42 @@ is the expected message rather than the message the `AssertionError` will
 display if `block` does not throw.
 
 <a id="ERR_ARG_NOT_ITERABLE"></a>
-### ERR_ARG_NOT_ITERABLE
+### `ERR_ARG_NOT_ITERABLE`
 
 An iterable argument (i.e. a value that works with `for...of` loops) was
 required, but not provided to a Node.js API.
 
 <a id="ERR_ASSERTION"></a>
-### ERR_ASSERTION
+### `ERR_ASSERTION`
 
 A special type of error that can be triggered whenever Node.js detects an
 exceptional logic violation that should never occur. These are raised typically
 by the `assert` module.
 
 <a id="ERR_ASYNC_CALLBACK"></a>
-### ERR_ASYNC_CALLBACK
+### `ERR_ASYNC_CALLBACK`
 
 An attempt was made to register something that is not a function as an
 `AsyncHooks` callback.
 
 <a id="ERR_ASYNC_TYPE"></a>
-### ERR_ASYNC_TYPE
+### `ERR_ASYNC_TYPE`
 
 The type of an asynchronous resource was invalid. Users are also able
 to define their own types if using the public embedder API.
 
 <a id="ERR_BROTLI_COMPRESSION_FAILED"></a>
-### ERR_BROTLI_COMPRESSION_FAILED
+### `ERR_BROTLI_COMPRESSION_FAILED`
 
 Data passed to a Brotli stream was not successfully compressed.
 
 <a id="ERR_BROTLI_INVALID_PARAM"></a>
-### ERR_BROTLI_INVALID_PARAM
+### `ERR_BROTLI_INVALID_PARAM`
 
 An invalid parameter key was passed during construction of a Brotli stream.
 
 <a id="ERR_BUFFER_CONTEXT_NOT_AVAILABLE"></a>
-### ERR_BUFFER_CONTEXT_NOT_AVAILABLE
+### `ERR_BUFFER_CONTEXT_NOT_AVAILABLE`
 
 An attempt was made to create a Node.js `Buffer` instance from addon or embedder
 code, while in a JS engine Context that is not associated with a Node.js
@@ -673,50 +673,50 @@ prototype of the resulting object. `Uint8Array`s are generally accepted in all
 Node.js core APIs where `Buffer`s are; they are available in all Contexts.
 
 <a id="ERR_BUFFER_OUT_OF_BOUNDS"></a>
-### ERR_BUFFER_OUT_OF_BOUNDS
+### `ERR_BUFFER_OUT_OF_BOUNDS`
 
 An operation outside the bounds of a `Buffer` was attempted.
 
 <a id="ERR_BUFFER_TOO_LARGE"></a>
-### ERR_BUFFER_TOO_LARGE
+### `ERR_BUFFER_TOO_LARGE`
 
 An attempt has been made to create a `Buffer` larger than the maximum allowed
 size.
 
 <a id="ERR_CANNOT_WATCH_SIGINT"></a>
-### ERR_CANNOT_WATCH_SIGINT
+### `ERR_CANNOT_WATCH_SIGINT`
 
 Node.js was unable to watch for the `SIGINT` signal.
 
 <a id="ERR_CHILD_CLOSED_BEFORE_REPLY"></a>
-### ERR_CHILD_CLOSED_BEFORE_REPLY
+### `ERR_CHILD_CLOSED_BEFORE_REPLY`
 
 A child process was closed before the parent received a reply.
 
 <a id="ERR_CHILD_PROCESS_IPC_REQUIRED"></a>
-### ERR_CHILD_PROCESS_IPC_REQUIRED
+### `ERR_CHILD_PROCESS_IPC_REQUIRED`
 
 Used when a child process is being forked without specifying an IPC channel.
 
 <a id="ERR_CHILD_PROCESS_STDIO_MAXBUFFER"></a>
-### ERR_CHILD_PROCESS_STDIO_MAXBUFFER
+### `ERR_CHILD_PROCESS_STDIO_MAXBUFFER`
 
 Used when the main process is trying to read data from the child process's
 STDERR/STDOUT, and the data's length is longer than the `maxBuffer` option.
 
 <a id="ERR_CONSOLE_WRITABLE_STREAM"></a>
-### ERR_CONSOLE_WRITABLE_STREAM
+### `ERR_CONSOLE_WRITABLE_STREAM`
 
 `Console` was instantiated without `stdout` stream, or `Console` has a
 non-writable `stdout` or `stderr` stream.
 
 <a id="ERR_CONSTRUCT_CALL_REQUIRED"></a>
-### ERR_CONSTRUCT_CALL_REQUIRED
+### `ERR_CONSTRUCT_CALL_REQUIRED`
 
 A constructor for a class was called without `new`.
 
 <a id="ERR_CONSTRUCT_CALL_INVALID"></a>
-### ERR_CONSTRUCT_CALL_INVALID
+### `ERR_CONSTRUCT_CALL_INVALID`
 <!--
 added: v12.5.0
 -->
@@ -724,120 +724,120 @@ added: v12.5.0
 A class constructor was called that is not callable.
 
 <a id="ERR_CPU_USAGE"></a>
-### ERR_CPU_USAGE
+### `ERR_CPU_USAGE`
 
 The native call from `process.cpuUsage` could not be processed.
 
 <a id="ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED"></a>
-### ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED
+### `ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED`
 
 A client certificate engine was requested that is not supported by the version
 of OpenSSL being used.
 
 <a id="ERR_CRYPTO_ECDH_INVALID_FORMAT"></a>
-### ERR_CRYPTO_ECDH_INVALID_FORMAT
+### `ERR_CRYPTO_ECDH_INVALID_FORMAT`
 
 An invalid value for the `format` argument was passed to the `crypto.ECDH()`
 class `getPublicKey()` method.
 
 <a id="ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY"></a>
-### ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY
+### `ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY`
 
 An invalid value for the `key` argument has been passed to the
 `crypto.ECDH()` class `computeSecret()` method. It means that the public
 key lies outside of the elliptic curve.
 
 <a id="ERR_CRYPTO_ENGINE_UNKNOWN"></a>
-### ERR_CRYPTO_ENGINE_UNKNOWN
+### `ERR_CRYPTO_ENGINE_UNKNOWN`
 
 An invalid crypto engine identifier was passed to
 [`require('crypto').setEngine()`][].
 
 <a id="ERR_CRYPTO_FIPS_FORCED"></a>
-### ERR_CRYPTO_FIPS_FORCED
+### `ERR_CRYPTO_FIPS_FORCED`
 
 The [`--force-fips`][] command-line argument was used but there was an attempt
 to enable or disable FIPS mode in the `crypto` module.
 
 <a id="ERR_CRYPTO_FIPS_UNAVAILABLE"></a>
-### ERR_CRYPTO_FIPS_UNAVAILABLE
+### `ERR_CRYPTO_FIPS_UNAVAILABLE`
 
 An attempt was made to enable or disable FIPS mode, but FIPS mode was not
 available.
 
 <a id="ERR_CRYPTO_HASH_FINALIZED"></a>
-### ERR_CRYPTO_HASH_FINALIZED
+### `ERR_CRYPTO_HASH_FINALIZED`
 
 [`hash.digest()`][] was called multiple times. The `hash.digest()` method must
 be called no more than one time per instance of a `Hash` object.
 
 <a id="ERR_CRYPTO_HASH_UPDATE_FAILED"></a>
-### ERR_CRYPTO_HASH_UPDATE_FAILED
+### `ERR_CRYPTO_HASH_UPDATE_FAILED`
 
 [`hash.update()`][] failed for any reason. This should rarely, if ever, happen.
 
 <a id="ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS"></a>
-### ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS
+### `ERR_CRYPTO_INCOMPATIBLE_KEY_OPTIONS`
 
 The selected public or private key encoding is incompatible with other options.
 
 <a id="ERR_CRYPTO_INVALID_DIGEST"></a>
-### ERR_CRYPTO_INVALID_DIGEST
+### `ERR_CRYPTO_INVALID_DIGEST`
 
 An invalid [crypto digest algorithm][] was specified.
 
 <a id="ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE"></a>
-### ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE
+### `ERR_CRYPTO_INVALID_KEY_OBJECT_TYPE`
 
 The given crypto key object's type is invalid for the attempted operation.
 
 <a id="ERR_CRYPTO_INVALID_STATE"></a>
-### ERR_CRYPTO_INVALID_STATE
+### `ERR_CRYPTO_INVALID_STATE`
 
 A crypto method was used on an object that was in an invalid state. For
 instance, calling [`cipher.getAuthTag()`][] before calling `cipher.final()`.
 
 <a id="ERR_CRYPTO_PBKDF2_ERROR"></a>
-### ERR_CRYPTO_PBKDF2_ERROR
+### `ERR_CRYPTO_PBKDF2_ERROR`
 
 The PBKDF2 algorithm failed for unspecified reasons. OpenSSL does not provide
 more details and therefore neither does Node.js.
 
 <a id="ERR_CRYPTO_SCRYPT_INVALID_PARAMETER"></a>
-### ERR_CRYPTO_SCRYPT_INVALID_PARAMETER
+### `ERR_CRYPTO_SCRYPT_INVALID_PARAMETER`
 
 One or more [`crypto.scrypt()`][] or [`crypto.scryptSync()`][] parameters are
 outside their legal range.
 
 <a id="ERR_CRYPTO_SCRYPT_NOT_SUPPORTED"></a>
-### ERR_CRYPTO_SCRYPT_NOT_SUPPORTED
+### `ERR_CRYPTO_SCRYPT_NOT_SUPPORTED`
 
 Node.js was compiled without `scrypt` support. Not possible with the official
 release binaries but can happen with custom builds, including distro builds.
 
 <a id="ERR_CRYPTO_SIGN_KEY_REQUIRED"></a>
-### ERR_CRYPTO_SIGN_KEY_REQUIRED
+### `ERR_CRYPTO_SIGN_KEY_REQUIRED`
 
 A signing `key` was not provided to the [`sign.sign()`][] method.
 
 <a id="ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH"></a>
-### ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH
+### `ERR_CRYPTO_TIMING_SAFE_EQUAL_LENGTH`
 
 [`crypto.timingSafeEqual()`][] was called with `Buffer`, `TypedArray`, or
 `DataView` arguments of different lengths.
 
 <a id="ERR_DIR_CLOSED"></a>
-### ERR_DIR_CLOSED
+### `ERR_DIR_CLOSED`
 
 The [`fs.Dir`][] was previously closed.
 
 <a id="ERR_DNS_SET_SERVERS_FAILED"></a>
-### ERR_DNS_SET_SERVERS_FAILED
+### `ERR_DNS_SET_SERVERS_FAILED`
 
 `c-ares` failed to set the DNS server.
 
 <a id="ERR_DOMAIN_CALLBACK_NOT_AVAILABLE"></a>
-### ERR_DOMAIN_CALLBACK_NOT_AVAILABLE
+### `ERR_DOMAIN_CALLBACK_NOT_AVAILABLE`
 
 The `domain` module was not usable since it could not establish the required
 error handling hooks, because
@@ -845,7 +845,7 @@ error handling hooks, because
 earlier point in time.
 
 <a id="ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE"></a>
-### ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE
+### `ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE`
 
 [`process.setUncaughtExceptionCaptureCallback()`][] could not be called
 because the `domain` module has been loaded at an earlier point in time.
@@ -854,170 +854,170 @@ The stack trace is extended to include the point in time at which the
 `domain` module had been loaded.
 
 <a id="ERR_ENCODING_INVALID_ENCODED_DATA"></a>
-### ERR_ENCODING_INVALID_ENCODED_DATA
+### `ERR_ENCODING_INVALID_ENCODED_DATA`
 
 Data provided to `TextDecoder()` API was invalid according to the encoding
 provided.
 
 <a id="ERR_ENCODING_NOT_SUPPORTED"></a>
-### ERR_ENCODING_NOT_SUPPORTED
+### `ERR_ENCODING_NOT_SUPPORTED`
 
 Encoding provided to `TextDecoder()` API was not one of the
 [WHATWG Supported Encodings][].
 
 <a id="ERR_FALSY_VALUE_REJECTION"></a>
-### ERR_FALSY_VALUE_REJECTION
+### `ERR_FALSY_VALUE_REJECTION`
 
 A `Promise` that was callbackified via `util.callbackify()` was rejected with a
 falsy value.
 
 <a id="ERR_FS_FILE_TOO_LARGE"></a>
-### ERR_FS_FILE_TOO_LARGE
+### `ERR_FS_FILE_TOO_LARGE`
 
 An attempt has been made to read a file whose size is larger than the maximum
 allowed size for a `Buffer`.
 
 <a id="ERR_FS_INVALID_SYMLINK_TYPE"></a>
-### ERR_FS_INVALID_SYMLINK_TYPE
+### `ERR_FS_INVALID_SYMLINK_TYPE`
 
 An invalid symlink type was passed to the [`fs.symlink()`][] or
 [`fs.symlinkSync()`][] methods.
 
 <a id="ERR_HTTP_HEADERS_SENT"></a>
-### ERR_HTTP_HEADERS_SENT
+### `ERR_HTTP_HEADERS_SENT`
 
 An attempt was made to add more headers after the headers had already been sent.
 
 <a id="ERR_HTTP_INVALID_HEADER_VALUE"></a>
-### ERR_HTTP_INVALID_HEADER_VALUE
+### `ERR_HTTP_INVALID_HEADER_VALUE`
 
 An invalid HTTP header value was specified.
 
 <a id="ERR_HTTP_INVALID_STATUS_CODE"></a>
-### ERR_HTTP_INVALID_STATUS_CODE
+### `ERR_HTTP_INVALID_STATUS_CODE`
 
 Status code was outside the regular status code range (100-999).
 
 <a id="ERR_HTTP_TRAILER_INVALID"></a>
-### ERR_HTTP_TRAILER_INVALID
+### `ERR_HTTP_TRAILER_INVALID`
 
 The `Trailer` header was set even though the transfer encoding does not support
 that.
 
 <a id="ERR_HTTP2_ALTSVC_INVALID_ORIGIN"></a>
-### ERR_HTTP2_ALTSVC_INVALID_ORIGIN
+### `ERR_HTTP2_ALTSVC_INVALID_ORIGIN`
 
 HTTP/2 ALTSVC frames require a valid origin.
 
 <a id="ERR_HTTP2_ALTSVC_LENGTH"></a>
-### ERR_HTTP2_ALTSVC_LENGTH
+### `ERR_HTTP2_ALTSVC_LENGTH`
 
 HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes.
 
 <a id="ERR_HTTP2_CONNECT_AUTHORITY"></a>
-### ERR_HTTP2_CONNECT_AUTHORITY
+### `ERR_HTTP2_CONNECT_AUTHORITY`
 
 For HTTP/2 requests using the `CONNECT` method, the `:authority` pseudo-header
 is required.
 
 <a id="ERR_HTTP2_CONNECT_PATH"></a>
-### ERR_HTTP2_CONNECT_PATH
+### `ERR_HTTP2_CONNECT_PATH`
 
 For HTTP/2 requests using the `CONNECT` method, the `:path` pseudo-header is
 forbidden.
 
 <a id="ERR_HTTP2_CONNECT_SCHEME"></a>
-### ERR_HTTP2_CONNECT_SCHEME
+### `ERR_HTTP2_CONNECT_SCHEME`
 
 For HTTP/2 requests using the `CONNECT` method, the `:scheme` pseudo-header is
 forbidden.
 
 <a id="ERR_HTTP2_ERROR"></a>
-### ERR_HTTP2_ERROR
+### `ERR_HTTP2_ERROR`
 
 A non-specific HTTP/2 error has occurred.
 
 <a id="ERR_HTTP2_GOAWAY_SESSION"></a>
-### ERR_HTTP2_GOAWAY_SESSION
+### `ERR_HTTP2_GOAWAY_SESSION`
 
 New HTTP/2 Streams may not be opened after the `Http2Session` has received a
 `GOAWAY` frame from the connected peer.
 
 <a id="ERR_HTTP2_HEADERS_AFTER_RESPOND"></a>
-### ERR_HTTP2_HEADERS_AFTER_RESPOND
+### `ERR_HTTP2_HEADERS_AFTER_RESPOND`
 
 An additional headers was specified after an HTTP/2 response was initiated.
 
 <a id="ERR_HTTP2_HEADERS_SENT"></a>
-### ERR_HTTP2_HEADERS_SENT
+### `ERR_HTTP2_HEADERS_SENT`
 
 An attempt was made to send multiple response headers.
 
 <a id="ERR_HTTP2_HEADER_SINGLE_VALUE"></a>
-### ERR_HTTP2_HEADER_SINGLE_VALUE
+### `ERR_HTTP2_HEADER_SINGLE_VALUE`
 
 Multiple values were provided for an HTTP/2 header field that was required to
 have only a single value.
 
 <a id="ERR_HTTP2_INFO_STATUS_NOT_ALLOWED"></a>
-### ERR_HTTP2_INFO_STATUS_NOT_ALLOWED
+### `ERR_HTTP2_INFO_STATUS_NOT_ALLOWED`
 
 Informational HTTP status codes (`1xx`) may not be set as the response status
 code on HTTP/2 responses.
 
 <a id="ERR_HTTP2_INVALID_CONNECTION_HEADERS"></a>
-### ERR_HTTP2_INVALID_CONNECTION_HEADERS
+### `ERR_HTTP2_INVALID_CONNECTION_HEADERS`
 
 HTTP/1 connection specific headers are forbidden to be used in HTTP/2
 requests and responses.
 
 <a id="ERR_HTTP2_INVALID_HEADER_VALUE"></a>
-### ERR_HTTP2_INVALID_HEADER_VALUE
+### `ERR_HTTP2_INVALID_HEADER_VALUE`
 
 An invalid HTTP/2 header value was specified.
 
 <a id="ERR_HTTP2_INVALID_INFO_STATUS"></a>
-### ERR_HTTP2_INVALID_INFO_STATUS
+### `ERR_HTTP2_INVALID_INFO_STATUS`
 
 An invalid HTTP informational status code has been specified. Informational
 status codes must be an integer between `100` and `199` (inclusive).
 
 <a id="ERR_HTTP2_INVALID_ORIGIN"></a>
-### ERR_HTTP2_INVALID_ORIGIN
+### `ERR_HTTP2_INVALID_ORIGIN`
 
 HTTP/2 `ORIGIN` frames require a valid origin.
 
 <a id="ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH"></a>
-### ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH
+### `ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH`
 
 Input `Buffer` and `Uint8Array` instances passed to the
 `http2.getUnpackedSettings()` API must have a length that is a multiple of
 six.
 
 <a id="ERR_HTTP2_INVALID_PSEUDOHEADER"></a>
-### ERR_HTTP2_INVALID_PSEUDOHEADER
+### `ERR_HTTP2_INVALID_PSEUDOHEADER`
 
 Only valid HTTP/2 pseudoheaders (`:status`, `:path`, `:authority`, `:scheme`,
 and `:method`) may be used.
 
 <a id="ERR_HTTP2_INVALID_SESSION"></a>
-### ERR_HTTP2_INVALID_SESSION
+### `ERR_HTTP2_INVALID_SESSION`
 
 An action was performed on an `Http2Session` object that had already been
 destroyed.
 
 <a id="ERR_HTTP2_INVALID_SETTING_VALUE"></a>
-### ERR_HTTP2_INVALID_SETTING_VALUE
+### `ERR_HTTP2_INVALID_SETTING_VALUE`
 
 An invalid value has been specified for an HTTP/2 setting.
 
 <a id="ERR_HTTP2_INVALID_STREAM"></a>
-### ERR_HTTP2_INVALID_STREAM
+### `ERR_HTTP2_INVALID_STREAM`
 
 An operation was performed on a stream that had already been destroyed.
 
 <a id="ERR_HTTP2_MAX_PENDING_SETTINGS_ACK"></a>
-### ERR_HTTP2_MAX_PENDING_SETTINGS_ACK
+### `ERR_HTTP2_MAX_PENDING_SETTINGS_ACK`
 
 Whenever an HTTP/2 `SETTINGS` frame is sent to a connected peer, the peer is
 required to send an acknowledgment that it has received and applied the new
@@ -1026,127 +1026,127 @@ be sent at any given time. This error code is used when that limit has been
 reached.
 
 <a id="ERR_HTTP2_NESTED_PUSH"></a>
-### ERR_HTTP2_NESTED_PUSH
+### `ERR_HTTP2_NESTED_PUSH`
 
 An attempt was made to initiate a new push stream from within a push stream.
 Nested push streams are not permitted.
 
 <a id="ERR_HTTP2_NO_SOCKET_MANIPULATION"></a>
-### ERR_HTTP2_NO_SOCKET_MANIPULATION
+### `ERR_HTTP2_NO_SOCKET_MANIPULATION`
 
 An attempt was made to directly manipulate (read, write, pause, resume, etc.) a
 socket attached to an `Http2Session`.
 
 <a id="ERR_HTTP2_ORIGIN_LENGTH"></a>
-### ERR_HTTP2_ORIGIN_LENGTH
+### `ERR_HTTP2_ORIGIN_LENGTH`
 
 HTTP/2 `ORIGIN` frames are limited to a length of 16382 bytes.
 
 <a id="ERR_HTTP2_OUT_OF_STREAMS"></a>
-### ERR_HTTP2_OUT_OF_STREAMS
+### `ERR_HTTP2_OUT_OF_STREAMS`
 
 The number of streams created on a single HTTP/2 session reached the maximum
 limit.
 
 <a id="ERR_HTTP2_PAYLOAD_FORBIDDEN"></a>
-### ERR_HTTP2_PAYLOAD_FORBIDDEN
+### `ERR_HTTP2_PAYLOAD_FORBIDDEN`
 
 A message payload was specified for an HTTP response code for which a payload is
 forbidden.
 
 <a id="ERR_HTTP2_PING_CANCEL"></a>
-### ERR_HTTP2_PING_CANCEL
+### `ERR_HTTP2_PING_CANCEL`
 
 An HTTP/2 ping was canceled.
 
 <a id="ERR_HTTP2_PING_LENGTH"></a>
-### ERR_HTTP2_PING_LENGTH
+### `ERR_HTTP2_PING_LENGTH`
 
 HTTP/2 ping payloads must be exactly 8 bytes in length.
 
 <a id="ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED"></a>
-### ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED
+### `ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED`
 
 An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header
 key names that begin with the `:` prefix.
 
 <a id="ERR_HTTP2_PUSH_DISABLED"></a>
-### ERR_HTTP2_PUSH_DISABLED
+### `ERR_HTTP2_PUSH_DISABLED`
 
 An attempt was made to create a push stream, which had been disabled by the
 client.
 
 <a id="ERR_HTTP2_SEND_FILE"></a>
-### ERR_HTTP2_SEND_FILE
+### `ERR_HTTP2_SEND_FILE`
 
 An attempt was made to use the `Http2Stream.prototype.responseWithFile()` API to
 send a directory.
 
 <a id="ERR_HTTP2_SEND_FILE_NOSEEK"></a>
-### ERR_HTTP2_SEND_FILE_NOSEEK
+### `ERR_HTTP2_SEND_FILE_NOSEEK`
 
 An attempt was made to use the `Http2Stream.prototype.responseWithFile()` API to
 send something other than a regular file, but `offset` or `length` options were
 provided.
 
 <a id="ERR_HTTP2_SESSION_ERROR"></a>
-### ERR_HTTP2_SESSION_ERROR
+### `ERR_HTTP2_SESSION_ERROR`
 
 The `Http2Session` closed with a non-zero error code.
 
 <a id="ERR_HTTP2_SETTINGS_CANCEL"></a>
-### ERR_HTTP2_SETTINGS_CANCEL
+### `ERR_HTTP2_SETTINGS_CANCEL`
 
 The `Http2Session` settings canceled.
 
 <a id="ERR_HTTP2_SOCKET_BOUND"></a>
-### ERR_HTTP2_SOCKET_BOUND
+### `ERR_HTTP2_SOCKET_BOUND`
 
 An attempt was made to connect a `Http2Session` object to a `net.Socket` or
 `tls.TLSSocket` that had already been bound to another `Http2Session` object.
 
 <a id="ERR_HTTP2_SOCKET_UNBOUND"></a>
-### ERR_HTTP2_SOCKET_UNBOUND
+### `ERR_HTTP2_SOCKET_UNBOUND`
 
 An attempt was made to use the `socket` property of an `Http2Session` that
 has already been closed.
 
 <a id="ERR_HTTP2_STATUS_101"></a>
-### ERR_HTTP2_STATUS_101
+### `ERR_HTTP2_STATUS_101`
 
 Use of the `101` Informational status code is forbidden in HTTP/2.
 
 <a id="ERR_HTTP2_STATUS_INVALID"></a>
-### ERR_HTTP2_STATUS_INVALID
+### `ERR_HTTP2_STATUS_INVALID`
 
 An invalid HTTP status code has been specified. Status codes must be an integer
 between `100` and `599` (inclusive).
 
 <a id="ERR_HTTP2_STREAM_CANCEL"></a>
-### ERR_HTTP2_STREAM_CANCEL
+### `ERR_HTTP2_STREAM_CANCEL`
 
 An `Http2Stream` was destroyed before any data was transmitted to the connected
 peer.
 
 <a id="ERR_HTTP2_STREAM_ERROR"></a>
-### ERR_HTTP2_STREAM_ERROR
+### `ERR_HTTP2_STREAM_ERROR`
 
 A non-zero error code was been specified in an `RST_STREAM` frame.
 
 <a id="ERR_HTTP2_STREAM_SELF_DEPENDENCY"></a>
-### ERR_HTTP2_STREAM_SELF_DEPENDENCY
+### `ERR_HTTP2_STREAM_SELF_DEPENDENCY`
 
 When setting the priority for an HTTP/2 stream, the stream may be marked as
 a dependency for a parent stream. This error code is used when an attempt is
 made to mark a stream and dependent of itself.
 
 <a id="ERR_HTTP2_TRAILERS_ALREADY_SENT"></a>
-### ERR_HTTP2_TRAILERS_ALREADY_SENT
+### `ERR_HTTP2_TRAILERS_ALREADY_SENT`
 
 Trailing headers have already been sent on the `Http2Stream`.
 
 <a id="ERR_HTTP2_TRAILERS_NOT_READY"></a>
-### ERR_HTTP2_TRAILERS_NOT_READY
+### `ERR_HTTP2_TRAILERS_NOT_READY`
 
 The `http2stream.sendTrailers()` method cannot be called until after the
 `'wantTrailers'` event is emitted on an `Http2Stream` object. The
@@ -1154,25 +1154,25 @@ The `http2stream.sendTrailers()` method cannot be called until after the
 is set for the `Http2Stream`.
 
 <a id="ERR_HTTP2_UNSUPPORTED_PROTOCOL"></a>
-### ERR_HTTP2_UNSUPPORTED_PROTOCOL
+### `ERR_HTTP2_UNSUPPORTED_PROTOCOL`
 
 `http2.connect()` was passed a URL that uses any protocol other than `http:` or
 `https:`.
 
 <a id="ERR_INTERNAL_ASSERTION"></a>
-### ERR_INTERNAL_ASSERTION
+### `ERR_INTERNAL_ASSERTION`
 
 There was a bug in Node.js or incorrect usage of Node.js internals.
 To fix the error, open an issue at https://github.com/nodejs/node/issues.
 
 <a id="ERR_INCOMPATIBLE_OPTION_PAIR"></a>
-### ERR_INCOMPATIBLE_OPTION_PAIR
+### `ERR_INCOMPATIBLE_OPTION_PAIR`
 
 An option pair is incompatible with each other and can not be used at the same
 time.
 
 <a id="ERR_INPUT_TYPE_NOT_ALLOWED"></a>
-### ERR_INPUT_TYPE_NOT_ALLOWED
+### `ERR_INPUT_TYPE_NOT_ALLOWED`
 
 > Stability: 1 - Experimental
 
@@ -1180,99 +1180,99 @@ The `--input-type` flag was used to attempt to execute a file. This flag can
 only be used with input via `--eval`, `--print` or `STDIN`.
 
 <a id="ERR_INSPECTOR_ALREADY_CONNECTED"></a>
-### ERR_INSPECTOR_ALREADY_CONNECTED
+### `ERR_INSPECTOR_ALREADY_CONNECTED`
 
 While using the `inspector` module, an attempt was made to connect when the
 inspector was already connected.
 
 <a id="ERR_INSPECTOR_CLOSED"></a>
-### ERR_INSPECTOR_CLOSED
+### `ERR_INSPECTOR_CLOSED`
 
 While using the `inspector` module, an attempt was made to use the inspector
 after the session had already closed.
 
 <a id="ERR_INSPECTOR_COMMAND"></a>
-### ERR_INSPECTOR_COMMAND
+### `ERR_INSPECTOR_COMMAND`
 
 An error occurred while issuing a command via the `inspector` module.
 
 <a id="ERR_INSPECTOR_NOT_ACTIVE"></a>
-### ERR_INSPECTOR_NOT_ACTIVE
+### `ERR_INSPECTOR_NOT_ACTIVE`
 
 The `inspector` is not active when `inspector.waitForDebugger()` is called.
 
 <a id="ERR_INSPECTOR_NOT_AVAILABLE"></a>
-### ERR_INSPECTOR_NOT_AVAILABLE
+### `ERR_INSPECTOR_NOT_AVAILABLE`
 
 The `inspector` module is not available for use.
 
 <a id="ERR_INSPECTOR_NOT_CONNECTED"></a>
-### ERR_INSPECTOR_NOT_CONNECTED
+### `ERR_INSPECTOR_NOT_CONNECTED`
 
 While using the `inspector` module, an attempt was made to use the inspector
 before it was connected.
 
 <a id="ERR_INSPECTOR_NOT_WORKER"></a>
-### ERR_INSPECTOR_NOT_WORKER
+### `ERR_INSPECTOR_NOT_WORKER`
 
 An API was called on the main thread that can only be used from
 the worker thread.
 
 <a id="ERR_INVALID_ADDRESS_FAMILY"></a>
-### ERR_INVALID_ADDRESS_FAMILY
+### `ERR_INVALID_ADDRESS_FAMILY`
 
 The provided address family is not understood by the Node.js API.
 
 <a id="ERR_INVALID_ARG_TYPE"></a>
-### ERR_INVALID_ARG_TYPE
+### `ERR_INVALID_ARG_TYPE`
 
 An argument of the wrong type was passed to a Node.js API.
 
 <a id="ERR_INVALID_ARG_VALUE"></a>
-### ERR_INVALID_ARG_VALUE
+### `ERR_INVALID_ARG_VALUE`
 
 An invalid or unsupported value was passed for a given argument.
 
 <a id="ERR_INVALID_ASYNC_ID"></a>
-### ERR_INVALID_ASYNC_ID
+### `ERR_INVALID_ASYNC_ID`
 
 An invalid `asyncId` or `triggerAsyncId` was passed using `AsyncHooks`. An id
 less than -1 should never happen.
 
 <a id="ERR_INVALID_BUFFER_SIZE"></a>
-### ERR_INVALID_BUFFER_SIZE
+### `ERR_INVALID_BUFFER_SIZE`
 
 A swap was performed on a `Buffer` but its size was not compatible with the
 operation.
 
 <a id="ERR_INVALID_CALLBACK"></a>
-### ERR_INVALID_CALLBACK
+### `ERR_INVALID_CALLBACK`
 
 A callback function was required but was not been provided to a Node.js API.
 
 <a id="ERR_INVALID_CHAR"></a>
-### ERR_INVALID_CHAR
+### `ERR_INVALID_CHAR`
 
 Invalid characters were detected in headers.
 
 <a id="ERR_INVALID_CURSOR_POS"></a>
-### ERR_INVALID_CURSOR_POS
+### `ERR_INVALID_CURSOR_POS`
 
 A cursor on a given stream cannot be moved to a specified row without a
 specified column.
 
 <a id="ERR_INVALID_FD"></a>
-### ERR_INVALID_FD
+### `ERR_INVALID_FD`
 
 A file descriptor ('fd') was not valid (e.g. it was a negative value).
 
 <a id="ERR_INVALID_FD_TYPE"></a>
-### ERR_INVALID_FD_TYPE
+### `ERR_INVALID_FD_TYPE`
 
 A file descriptor ('fd') type was not valid.
 
 <a id="ERR_INVALID_FILE_URL_HOST"></a>
-### ERR_INVALID_FILE_URL_HOST
+### `ERR_INVALID_FILE_URL_HOST`
 
 A Node.js API that consumes `file:` URLs (such as certain functions in the
 [`fs`][] module) encountered a file URL with an incompatible host. This
@@ -1280,94 +1280,94 @@ situation can only occur on Unix-like systems where only `localhost` or an empty
 host is supported.
 
 <a id="ERR_INVALID_FILE_URL_PATH"></a>
-### ERR_INVALID_FILE_URL_PATH
+### `ERR_INVALID_FILE_URL_PATH`
 
 A Node.js API that consumes `file:` URLs (such as certain functions in the
 [`fs`][] module) encountered a file URL with an incompatible path. The exact
 semantics for determining whether a path can be used is platform-dependent.
 
 <a id="ERR_INVALID_HANDLE_TYPE"></a>
-### ERR_INVALID_HANDLE_TYPE
+### `ERR_INVALID_HANDLE_TYPE`
 
 An attempt was made to send an unsupported "handle" over an IPC communication
 channel to a child process. See [`subprocess.send()`][] and [`process.send()`][]
 for more information.
 
 <a id="ERR_INVALID_HTTP_TOKEN"></a>
-### ERR_INVALID_HTTP_TOKEN
+### `ERR_INVALID_HTTP_TOKEN`
 
 An invalid HTTP token was supplied.
 
 <a id="ERR_INVALID_IP_ADDRESS"></a>
-### ERR_INVALID_IP_ADDRESS
+### `ERR_INVALID_IP_ADDRESS`
 
 An IP address is not valid.
 
 <a id="ERR_INVALID_OPT_VALUE"></a>
-### ERR_INVALID_OPT_VALUE
+### `ERR_INVALID_OPT_VALUE`
 
 An invalid or unexpected value was passed in an options object.
 
 <a id="ERR_INVALID_OPT_VALUE_ENCODING"></a>
-### ERR_INVALID_OPT_VALUE_ENCODING
+### `ERR_INVALID_OPT_VALUE_ENCODING`
 
 An invalid or unknown file encoding was passed.
 
 <a id="ERR_INVALID_PACKAGE_CONFIG"></a>
-### ERR_INVALID_PACKAGE_CONFIG
+### `ERR_INVALID_PACKAGE_CONFIG`
 
 An invalid `package.json` file was found which failed parsing.
 
 <a id="ERR_INVALID_PERFORMANCE_MARK"></a>
-### ERR_INVALID_PERFORMANCE_MARK
+### `ERR_INVALID_PERFORMANCE_MARK`
 
 While using the Performance Timing API (`perf_hooks`), a performance mark is
 invalid.
 
 <a id="ERR_INVALID_PROTOCOL"></a>
-### ERR_INVALID_PROTOCOL
+### `ERR_INVALID_PROTOCOL`
 
 An invalid `options.protocol` was passed to `http.request()`.
 
 <a id="ERR_INVALID_REPL_EVAL_CONFIG"></a>
-### ERR_INVALID_REPL_EVAL_CONFIG
+### `ERR_INVALID_REPL_EVAL_CONFIG`
 
 Both `breakEvalOnSigint` and `eval` options were set in the [`REPL`][] config,
 which is not supported.
 
 <a id="ERR_INVALID_REPL_INPUT"></a>
-### ERR_INVALID_REPL_INPUT
+### `ERR_INVALID_REPL_INPUT`
 
 The input may not be used in the [`REPL`][]. All prohibited inputs are
 documented in the [`REPL`][]'s documentation.
 
 <a id="ERR_INVALID_RETURN_PROPERTY"></a>
-### ERR_INVALID_RETURN_PROPERTY
+### `ERR_INVALID_RETURN_PROPERTY`
 
 Thrown in case a function option does not provide a valid value for one of its
 returned object properties on execution.
 
 <a id="ERR_INVALID_RETURN_PROPERTY_VALUE"></a>
-### ERR_INVALID_RETURN_PROPERTY_VALUE
+### `ERR_INVALID_RETURN_PROPERTY_VALUE`
 
 Thrown in case a function option does not provide an expected value
 type for one of its returned object properties on execution.
 
 <a id="ERR_INVALID_RETURN_VALUE"></a>
-### ERR_INVALID_RETURN_VALUE
+### `ERR_INVALID_RETURN_VALUE`
 
 Thrown in case a function option does not return an expected value
 type on execution, such as when a function is expected to return a promise.
 
 <a id="ERR_INVALID_SYNC_FORK_INPUT"></a>
-### ERR_INVALID_SYNC_FORK_INPUT
+### `ERR_INVALID_SYNC_FORK_INPUT`
 
 A `Buffer`, `TypedArray`, `DataView` or `string` was provided as stdio input to
 an asynchronous fork. See the documentation for the [`child_process`][] module
 for more information.
 
 <a id="ERR_INVALID_THIS"></a>
-### ERR_INVALID_THIS
+### `ERR_INVALID_THIS`
 
 A Node.js API function was called with an incompatible `this` value.
 
@@ -1380,12 +1380,12 @@ urlSearchParams.has.call(buf, 'foo');
 ```
 
 <a id="ERR_INVALID_TRANSFER_OBJECT"></a>
-### ERR_INVALID_TRANSFER_OBJECT
+### `ERR_INVALID_TRANSFER_OBJECT`
 
 An invalid transfer object was passed to `postMessage()`.
 
 <a id="ERR_INVALID_TUPLE"></a>
-### ERR_INVALID_TUPLE
+### `ERR_INVALID_TUPLE`
 
 An element in the `iterable` provided to the [WHATWG][WHATWG URL API]
 [`URLSearchParams` constructor][`new URLSearchParams(iterable)`] did not
@@ -1393,12 +1393,12 @@ represent a `[name, value]` tuple – that is, if an element is not iterable, or
 does not consist of exactly two elements.
 
 <a id="ERR_INVALID_URI"></a>
-### ERR_INVALID_URI
+### `ERR_INVALID_URI`
 
 An invalid URI was passed.
 
 <a id="ERR_INVALID_URL"></a>
-### ERR_INVALID_URL
+### `ERR_INVALID_URL`
 
 An invalid URL was passed to the [WHATWG][WHATWG URL API]
 [`URL` constructor][`new URL(input)`] to be parsed. The thrown error object
@@ -1406,7 +1406,7 @@ typically has an additional property `'input'` that contains the URL that failed
 to parse.
 
 <a id="ERR_INVALID_URL_SCHEME"></a>
-### ERR_INVALID_URL_SCHEME
+### `ERR_INVALID_URL_SCHEME`
 
 An attempt was made to use a URL of an incompatible scheme (protocol) for a
 specific purpose. It is only used in the [WHATWG URL API][] support in the
@@ -1414,47 +1414,47 @@ specific purpose. It is only used in the [WHATWG URL API][] support in the
 in other Node.js APIs as well in the future.
 
 <a id="ERR_IPC_CHANNEL_CLOSED"></a>
-### ERR_IPC_CHANNEL_CLOSED
+### `ERR_IPC_CHANNEL_CLOSED`
 
 An attempt was made to use an IPC communication channel that was already closed.
 
 <a id="ERR_IPC_DISCONNECTED"></a>
-### ERR_IPC_DISCONNECTED
+### `ERR_IPC_DISCONNECTED`
 
 An attempt was made to disconnect an IPC communication channel that was already
 disconnected. See the documentation for the [`child_process`][] module
 for more information.
 
 <a id="ERR_IPC_ONE_PIPE"></a>
-### ERR_IPC_ONE_PIPE
+### `ERR_IPC_ONE_PIPE`
 
 An attempt was made to create a child Node.js process using more than one IPC
 communication channel. See the documentation for the [`child_process`][] module
 for more information.
 
 <a id="ERR_IPC_SYNC_FORK"></a>
-### ERR_IPC_SYNC_FORK
+### `ERR_IPC_SYNC_FORK`
 
 An attempt was made to open an IPC communication channel with a synchronously
 forked Node.js process. See the documentation for the [`child_process`][] module
 for more information.
 
 <a id="ERR_MANIFEST_ASSERT_INTEGRITY"></a>
-### ERR_MANIFEST_ASSERT_INTEGRITY
+### `ERR_MANIFEST_ASSERT_INTEGRITY`
 
 An attempt was made to load a resource, but the resource did not match the
 integrity defined by the policy manifest. See the documentation for [policy][]
 manifests for more information.
 
 <a id="ERR_MANIFEST_DEPENDENCY_MISSING"></a>
-### ERR_MANIFEST_DEPENDENCY_MISSING
+### `ERR_MANIFEST_DEPENDENCY_MISSING`
 
 An attempt was made to load a resource, but the resource was not listed as a
 dependency from the location that attempted to load it. See the documentation
 for [policy][] manifests for more information.
 
 <a id="ERR_MANIFEST_INTEGRITY_MISMATCH"></a>
-### ERR_MANIFEST_INTEGRITY_MISMATCH
+### `ERR_MANIFEST_INTEGRITY_MISMATCH`
 
 An attempt was made to load a policy manifest, but the manifest had multiple
 entries for a resource which did not match each other. Update the manifest
@@ -1462,43 +1462,43 @@ entries to match in order to resolve this error. See the documentation for
 [policy][] manifests for more information.
 
 <a id="ERR_MANIFEST_INVALID_RESOURCE_FIELD"></a>
-### ERR_MANIFEST_INVALID_RESOURCE_FIELD
+### `ERR_MANIFEST_INVALID_RESOURCE_FIELD`
 
 A policy manifest resource had an invalid value for one of its fields. Update
 the manifest entry to match in order to resolve this error. See the
 documentation for [policy][] manifests for more information.
 
 <a id="ERR_MANIFEST_PARSE_POLICY"></a>
-### ERR_MANIFEST_PARSE_POLICY
+### `ERR_MANIFEST_PARSE_POLICY`
 
 An attempt was made to load a policy manifest, but the manifest was unable to
 be parsed. See the documentation for [policy][] manifests for more information.
 
 <a id="ERR_MANIFEST_TDZ"></a>
-### ERR_MANIFEST_TDZ
+### `ERR_MANIFEST_TDZ`
 
 An attempt was made to read from a policy manifest, but the manifest
 initialization has not yet taken place. This is likely a bug in Node.js.
 
 <a id="ERR_MANIFEST_UNKNOWN_ONERROR"></a>
-### ERR_MANIFEST_UNKNOWN_ONERROR
+### `ERR_MANIFEST_UNKNOWN_ONERROR`
 
 A policy manifest was loaded, but had an unknown value for its "onerror"
 behavior. See the documentation for [policy][] manifests for more information.
 
 <a id="ERR_MEMORY_ALLOCATION_FAILED"></a>
-### ERR_MEMORY_ALLOCATION_FAILED
+### `ERR_MEMORY_ALLOCATION_FAILED`
 
 An attempt was made to allocate memory (usually in the C++ layer) but it
 failed.
 
 <a id="ERR_METHOD_NOT_IMPLEMENTED"></a>
-### ERR_METHOD_NOT_IMPLEMENTED
+### `ERR_METHOD_NOT_IMPLEMENTED`
 
 A method is required but not implemented.
 
 <a id="ERR_MISSING_ARGS"></a>
-### ERR_MISSING_ARGS
+### `ERR_MISSING_ARGS`
 
 A required argument of a Node.js API was not passed. This is only used for
 strict compliance with the API specification (which in some cases may accept
@@ -1507,7 +1507,7 @@ strict compliance with the API specification (which in some cases may accept
 [`ERR_INVALID_ARG_TYPE`][] error code may be used instead.
 
 <a id="ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK"></a>
-### ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK
+### `ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK`
 
 > Stability: 1 - Experimental
 
@@ -1515,32 +1515,32 @@ An [ES Module][] loader hook specified `format: 'dynamic'` but did not provide
 a `dynamicInstantiate` hook.
 
 <a id="ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST"></a>
-### ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST
+### `ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST`
 
 A `MessagePort` was found in the object passed to a `postMessage()` call,
 but not provided in the `transferList` for that call.
 
 <a id="ERR_MISSING_PASSPHRASE"></a>
-### ERR_MISSING_PASSPHRASE
+### `ERR_MISSING_PASSPHRASE`
 
 An attempt was made to read an encrypted key without specifying a passphrase.
 
 <a id="ERR_MISSING_PLATFORM_FOR_WORKER"></a>
-### ERR_MISSING_PLATFORM_FOR_WORKER
+### `ERR_MISSING_PLATFORM_FOR_WORKER`
 
 The V8 platform used by this instance of Node.js does not support creating
 Workers. This is caused by lack of embedder support for Workers. In particular,
 this error will not occur with standard builds of Node.js.
 
 <a id="ERR_MODULE_NOT_FOUND"></a>
-### ERR_MODULE_NOT_FOUND
+### `ERR_MODULE_NOT_FOUND`
 
 > Stability: 1 - Experimental
 
 An [ES Module][] could not be resolved.
 
 <a id="ERR_MULTIPLE_CALLBACK"></a>
-### ERR_MULTIPLE_CALLBACK
+### `ERR_MULTIPLE_CALLBACK`
 
 A callback was called more than once.
 
@@ -1549,210 +1549,210 @@ can either be fulfilled or rejected but not both at the same time. The latter
 would be possible by calling a callback more than once.
 
 <a id="ERR_NAPI_CONS_FUNCTION"></a>
-### ERR_NAPI_CONS_FUNCTION
+### `ERR_NAPI_CONS_FUNCTION`
 
 While using `N-API`, a constructor passed was not a function.
 
 <a id="ERR_NAPI_INVALID_DATAVIEW_ARGS"></a>
-### ERR_NAPI_INVALID_DATAVIEW_ARGS
+### `ERR_NAPI_INVALID_DATAVIEW_ARGS`
 
 While calling `napi_create_dataview()`, a given `offset` was outside the bounds
 of the dataview or `offset + length` was larger than a length of given `buffer`.
 
 <a id="ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT"></a>
-### ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT
+### `ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENT`
 
 While calling `napi_create_typedarray()`, the provided `offset` was not a
 multiple of the element size.
 
 <a id="ERR_NAPI_INVALID_TYPEDARRAY_LENGTH"></a>
-### ERR_NAPI_INVALID_TYPEDARRAY_LENGTH
+### `ERR_NAPI_INVALID_TYPEDARRAY_LENGTH`
 
 While calling `napi_create_typedarray()`, `(length * size_of_element) +
 byte_offset` was larger than the length of given `buffer`.
 
 <a id="ERR_NAPI_TSFN_CALL_JS"></a>
-### ERR_NAPI_TSFN_CALL_JS
+### `ERR_NAPI_TSFN_CALL_JS`
 
 An error occurred while invoking the JavaScript portion of the thread-safe
 function.
 
 <a id="ERR_NAPI_TSFN_GET_UNDEFINED"></a>
-### ERR_NAPI_TSFN_GET_UNDEFINED
+### `ERR_NAPI_TSFN_GET_UNDEFINED`
 
 An error occurred while attempting to retrieve the JavaScript `undefined`
 value.
 
 <a id="ERR_NAPI_TSFN_START_IDLE_LOOP"></a>
-### ERR_NAPI_TSFN_START_IDLE_LOOP
+### `ERR_NAPI_TSFN_START_IDLE_LOOP`
 
 On the main thread, values are removed from the queue associated with the
 thread-safe function in an idle loop. This error indicates that an error
 has occurred when attempting to start the loop.
 
 <a id="ERR_NAPI_TSFN_STOP_IDLE_LOOP"></a>
-### ERR_NAPI_TSFN_STOP_IDLE_LOOP
+### `ERR_NAPI_TSFN_STOP_IDLE_LOOP`
 
 Once no more items are left in the queue, the idle loop must be suspended. This
 error indicates that the idle loop has failed to stop.
 
 <a id="ERR_NO_CRYPTO"></a>
-### ERR_NO_CRYPTO
+### `ERR_NO_CRYPTO`
 
 An attempt was made to use crypto features while Node.js was not compiled with
 OpenSSL crypto support.
 
 <a id="ERR_NO_ICU"></a>
-### ERR_NO_ICU
+### `ERR_NO_ICU`
 
 An attempt was made to use features that require [ICU][], but Node.js was not
 compiled with ICU support.
 
 <a id="ERR_NON_CONTEXT_AWARE_DISABLED"></a>
-### ERR_NON_CONTEXT_AWARE_DISABLED
+### `ERR_NON_CONTEXT_AWARE_DISABLED`
 
 A non-context-aware native addon was loaded in a process that disallows them.
 
 <a id="ERR_OUT_OF_RANGE"></a>
-### ERR_OUT_OF_RANGE
+### `ERR_OUT_OF_RANGE`
 
 A given value is out of the accepted range.
 
 <a id="ERR_REQUIRE_ESM"></a>
-### ERR_REQUIRE_ESM
+### `ERR_REQUIRE_ESM`
 
 > Stability: 1 - Experimental
 
 An attempt was made to `require()` an [ES Module][].
 
 <a id="ERR_SCRIPT_EXECUTION_INTERRUPTED"></a>
-### ERR_SCRIPT_EXECUTION_INTERRUPTED
+### `ERR_SCRIPT_EXECUTION_INTERRUPTED`
 
 Script execution was interrupted by `SIGINT` (For example, when Ctrl+C was
 pressed).
 
 <a id="ERR_SCRIPT_EXECUTION_TIMEOUT"></a>
-### ERR_SCRIPT_EXECUTION_TIMEOUT
+### `ERR_SCRIPT_EXECUTION_TIMEOUT`
 
 Script execution timed out, possibly due to bugs in the script being executed.
 
 <a id="ERR_SERVER_ALREADY_LISTEN"></a>
-### ERR_SERVER_ALREADY_LISTEN
+### `ERR_SERVER_ALREADY_LISTEN`
 
 The [`server.listen()`][] method was called while a `net.Server` was already
 listening. This applies to all instances of `net.Server`, including HTTP, HTTPS,
 and HTTP/2 `Server` instances.
 
 <a id="ERR_SERVER_NOT_RUNNING"></a>
-### ERR_SERVER_NOT_RUNNING
+### `ERR_SERVER_NOT_RUNNING`
 
 The [`server.close()`][] method was called when a `net.Server` was not
 running. This applies to all instances of `net.Server`, including HTTP, HTTPS,
 and HTTP/2 `Server` instances.
 
 <a id="ERR_SOCKET_ALREADY_BOUND"></a>
-### ERR_SOCKET_ALREADY_BOUND
+### `ERR_SOCKET_ALREADY_BOUND`
 
 An attempt was made to bind a socket that has already been bound.
 
 <a id="ERR_SOCKET_BAD_BUFFER_SIZE"></a>
-### ERR_SOCKET_BAD_BUFFER_SIZE
+### `ERR_SOCKET_BAD_BUFFER_SIZE`
 
 An invalid (negative) size was passed for either the `recvBufferSize` or
 `sendBufferSize` options in [`dgram.createSocket()`][].
 
 <a id="ERR_SOCKET_BAD_PORT"></a>
-### ERR_SOCKET_BAD_PORT
+### `ERR_SOCKET_BAD_PORT`
 
 An API function expecting a port >= 0 and < 65536 received an invalid value.
 
 <a id="ERR_SOCKET_BAD_TYPE"></a>
-### ERR_SOCKET_BAD_TYPE
+### `ERR_SOCKET_BAD_TYPE`
 
 An API function expecting a socket type (`udp4` or `udp6`) received an invalid
 value.
 
 <a id="ERR_SOCKET_BUFFER_SIZE"></a>
-### ERR_SOCKET_BUFFER_SIZE
+### `ERR_SOCKET_BUFFER_SIZE`
 
 While using [`dgram.createSocket()`][], the size of the receive or send `Buffer`
 could not be determined.
 
 <a id="ERR_SOCKET_CANNOT_SEND"></a>
-### ERR_SOCKET_CANNOT_SEND
+### `ERR_SOCKET_CANNOT_SEND`
 
 Data could be sent on a socket.
 
 <a id="ERR_SOCKET_CLOSED"></a>
-### ERR_SOCKET_CLOSED
+### `ERR_SOCKET_CLOSED`
 
 An attempt was made to operate on an already closed socket.
 
 <a id="ERR_SOCKET_DGRAM_IS_CONNECTED"></a>
-### ERR_SOCKET_DGRAM_IS_CONNECTED
+### `ERR_SOCKET_DGRAM_IS_CONNECTED`
 
 A [`dgram.connect()`][] call was made on an already connected socket.
 
 <a id="ERR_SOCKET_DGRAM_NOT_CONNECTED"></a>
-### ERR_SOCKET_DGRAM_NOT_CONNECTED
+### `ERR_SOCKET_DGRAM_NOT_CONNECTED`
 
 A [`dgram.disconnect()`][] or [`dgram.remoteAddress()`][] call was made on a
 disconnected socket.
 
 <a id="ERR_SOCKET_DGRAM_NOT_RUNNING"></a>
-### ERR_SOCKET_DGRAM_NOT_RUNNING
+### `ERR_SOCKET_DGRAM_NOT_RUNNING`
 
 A call was made and the UDP subsystem was not running.
 
 <a id="ERR_SRI_PARSE"></a>
-### ERR_SRI_PARSE
+### `ERR_SRI_PARSE`
 
 A string was provided for a Subresource Integrity check, but was unable to be
 parsed. Check the format of integrity attributes by looking at the
 [Subresource Integrity specification][].
 
 <a id="ERR_STREAM_CANNOT_PIPE"></a>
-### ERR_STREAM_CANNOT_PIPE
+### `ERR_STREAM_CANNOT_PIPE`
 
 An attempt was made to call [`stream.pipe()`][] on a [`Writable`][] stream.
 
 <a id="ERR_STREAM_DESTROYED"></a>
-### ERR_STREAM_DESTROYED
+### `ERR_STREAM_DESTROYED`
 
 A stream method was called that cannot complete because the stream was
 destroyed using `stream.destroy()`.
 
 <a id="ERR_STREAM_ALREADY_FINISHED"></a>
-### ERR_STREAM_ALREADY_FINISHED
+### `ERR_STREAM_ALREADY_FINISHED`
 
 A stream method was called that cannot complete because the stream was
 finished.
 
 <a id="ERR_STREAM_NULL_VALUES"></a>
-### ERR_STREAM_NULL_VALUES
+### `ERR_STREAM_NULL_VALUES`
 
 An attempt was made to call [`stream.write()`][] with a `null` chunk.
 
 <a id="ERR_STREAM_PREMATURE_CLOSE"></a>
-### ERR_STREAM_PREMATURE_CLOSE
+### `ERR_STREAM_PREMATURE_CLOSE`
 
 An error returned by `stream.finished()` and `stream.pipeline()`, when a stream
 or a pipeline ends non gracefully with no explicit error.
 
 <a id="ERR_STREAM_PUSH_AFTER_EOF"></a>
-### ERR_STREAM_PUSH_AFTER_EOF
+### `ERR_STREAM_PUSH_AFTER_EOF`
 
 An attempt was made to call [`stream.push()`][] after a `null`(EOF) had been
 pushed to the stream.
 
 <a id="ERR_STREAM_UNSHIFT_AFTER_END_EVENT"></a>
-### ERR_STREAM_UNSHIFT_AFTER_END_EVENT
+### `ERR_STREAM_UNSHIFT_AFTER_END_EVENT`
 
 An attempt was made to call [`stream.unshift()`][] after the `'end'` event was
 emitted.
 
 <a id="ERR_STREAM_WRAP"></a>
-### ERR_STREAM_WRAP
+### `ERR_STREAM_WRAP`
 
 Prevents an abort if a string decoder was set on the Socket or if the decoder
 is in `objectMode`.
@@ -1765,38 +1765,38 @@ instance.setEncoding('utf8');
 ```
 
 <a id="ERR_STREAM_WRITE_AFTER_END"></a>
-### ERR_STREAM_WRITE_AFTER_END
+### `ERR_STREAM_WRITE_AFTER_END`
 
 An attempt was made to call [`stream.write()`][] after `stream.end()` has been
 called.
 
 <a id="ERR_STRING_TOO_LONG"></a>
-### ERR_STRING_TOO_LONG
+### `ERR_STRING_TOO_LONG`
 
 An attempt has been made to create a string longer than the maximum allowed
 length.
 
 <a id="ERR_SYNTHETIC"></a>
-### ERR_SYNTHETIC
+### `ERR_SYNTHETIC`
 
 An artificial error object used to capture the call stack for diagnostic
 reports.
 
 <a id="ERR_SYSTEM_ERROR"></a>
-### ERR_SYSTEM_ERROR
+### `ERR_SYSTEM_ERROR`
 
 An unspecified or non-specific system error has occurred within the Node.js
 process. The error object will have an `err.info` object property with
 additional details.
 
 <a id="ERR_TLS_CERT_ALTNAME_INVALID"></a>
-### ERR_TLS_CERT_ALTNAME_INVALID
+### `ERR_TLS_CERT_ALTNAME_INVALID`
 
 While using TLS, the hostname/IP of the peer did not match any of the
 `subjectAltNames` in its certificate.
 
 <a id="ERR_TLS_DH_PARAM_SIZE"></a>
-### ERR_TLS_DH_PARAM_SIZE
+### `ERR_TLS_DH_PARAM_SIZE`
 
 While using TLS, the parameter offered for the Diffie-Hellman (`DH`)
 key-agreement protocol is too small. By default, the key length must be greater
@@ -1804,13 +1804,13 @@ than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly
 recommended to use 2048 bits or larger for stronger security.
 
 <a id="ERR_TLS_HANDSHAKE_TIMEOUT"></a>
-### ERR_TLS_HANDSHAKE_TIMEOUT
+### `ERR_TLS_HANDSHAKE_TIMEOUT`
 
 A TLS/SSL handshake timed out. In this case, the server must also abort the
 connection.
 
 <a id="ERR_TLS_INVALID_CONTEXT">
-### ERR_TLS_INVALID_CONTEXT
+### `ERR_TLS_INVALID_CONTEXT`
 <!-- YAML
 added: v13.3.0
 -->
@@ -1818,41 +1818,41 @@ added: v13.3.0
 The context must be a `SecureContext`.
 
 <a id="ERR_TLS_INVALID_PROTOCOL_METHOD"></a>
-### ERR_TLS_INVALID_PROTOCOL_METHOD
+### `ERR_TLS_INVALID_PROTOCOL_METHOD`
 
 The specified  `secureProtocol` method is invalid. It is  either unknown, or
 disabled because it is insecure.
 
 <a id="ERR_TLS_INVALID_PROTOCOL_VERSION"></a>
-### ERR_TLS_INVALID_PROTOCOL_VERSION
+### `ERR_TLS_INVALID_PROTOCOL_VERSION`
 
 Valid TLS protocol versions are `'TLSv1'`, `'TLSv1.1'`, or `'TLSv1.2'`.
 
 <a id="ERR_TLS_PROTOCOL_VERSION_CONFLICT"></a>
-### ERR_TLS_PROTOCOL_VERSION_CONFLICT
+### `ERR_TLS_PROTOCOL_VERSION_CONFLICT`
 
 Attempting to set a TLS protocol `minVersion` or `maxVersion` conflicts with an
 attempt to set the `secureProtocol` explicitly. Use one mechanism or the other.
 
 <a id="ERR_TLS_RENEGOTIATION_DISABLED"></a>
-### ERR_TLS_RENEGOTIATION_DISABLED
+### `ERR_TLS_RENEGOTIATION_DISABLED`
 
 An attempt was made to renegotiate TLS on a socket instance with TLS disabled.
 
 <a id="ERR_TLS_REQUIRED_SERVER_NAME"></a>
-### ERR_TLS_REQUIRED_SERVER_NAME
+### `ERR_TLS_REQUIRED_SERVER_NAME`
 
 While using TLS, the `server.addContext()` method was called without providing
 a hostname in the first parameter.
 
 <a id="ERR_TLS_SESSION_ATTACK"></a>
-### ERR_TLS_SESSION_ATTACK
+### `ERR_TLS_SESSION_ATTACK`
 
 An excessive amount of TLS renegotiations is detected, which is a potential
 vector for denial-of-service attacks.
 
 <a id="ERR_TLS_SNI_FROM_SERVER"></a>
-### ERR_TLS_SNI_FROM_SERVER
+### `ERR_TLS_SNI_FROM_SERVER`
 
 An attempt was made to issue Server Name Indication from a TLS server-side
 socket, which is only valid from a client.
@@ -1863,19 +1863,19 @@ socket, which is only valid from a client.
 Failed to set PSK identity hint. Hint may be too long.
 
 <a id="ERR_TRACE_EVENTS_CATEGORY_REQUIRED"></a>
-### ERR_TRACE_EVENTS_CATEGORY_REQUIRED
+### `ERR_TRACE_EVENTS_CATEGORY_REQUIRED`
 
 The `trace_events.createTracing()` method requires at least one trace event
 category.
 
 <a id="ERR_TRACE_EVENTS_UNAVAILABLE"></a>
-### ERR_TRACE_EVENTS_UNAVAILABLE
+### `ERR_TRACE_EVENTS_UNAVAILABLE`
 
 The `trace_events` module could not be loaded because Node.js was compiled with
 the `--without-v8-platform` flag.
 
 <a id="ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER"></a>
-### ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER
+### `ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER`
 
 A `SharedArrayBuffer` whose memory is not managed by the JavaScript engine
 or by Node.js was encountered during serialization. Such a `SharedArrayBuffer`
@@ -1885,22 +1885,22 @@ This can only happen when native addons create `SharedArrayBuffer`s in
 "externalized" mode, or put existing `SharedArrayBuffer` into externalized mode.
 
 <a id="ERR_TRANSFORM_ALREADY_TRANSFORMING"></a>
-### ERR_TRANSFORM_ALREADY_TRANSFORMING
+### `ERR_TRANSFORM_ALREADY_TRANSFORMING`
 
 A `Transform` stream finished while it was still transforming.
 
 <a id="ERR_TRANSFORM_WITH_LENGTH_0"></a>
-### ERR_TRANSFORM_WITH_LENGTH_0
+### `ERR_TRANSFORM_WITH_LENGTH_0`
 
 A `Transform` stream finished with data still in the write buffer.
 
 <a id="ERR_TTY_INIT_FAILED"></a>
-### ERR_TTY_INIT_FAILED
+### `ERR_TTY_INIT_FAILED`
 
 The initialization of a TTY failed due to a system error.
 
 <a id="ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET"></a>
-### ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET
+### `ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET`
 
 [`process.setUncaughtExceptionCaptureCallback()`][] was called twice,
 without first resetting the callback to `null`.
@@ -1909,35 +1909,35 @@ This error is designed to prevent accidentally overwriting a callback registered
 from another module.
 
 <a id="ERR_UNESCAPED_CHARACTERS"></a>
-### ERR_UNESCAPED_CHARACTERS
+### `ERR_UNESCAPED_CHARACTERS`
 
 A string that contained unescaped characters was received.
 
 <a id="ERR_UNHANDLED_ERROR"></a>
-### ERR_UNHANDLED_ERROR
+### `ERR_UNHANDLED_ERROR`
 
 An unhandled error occurred (for instance, when an `'error'` event is emitted
 by an [`EventEmitter`][] but an `'error'` handler is not registered).
 
 <a id="ERR_UNKNOWN_BUILTIN_MODULE"></a>
-### ERR_UNKNOWN_BUILTIN_MODULE
+### `ERR_UNKNOWN_BUILTIN_MODULE`
 
 Used to identify a specific kind of internal Node.js error that should not
 typically be triggered by user code. Instances of this error point to an
 internal bug within the Node.js binary itself.
 
 <a id="ERR_UNKNOWN_CREDENTIAL"></a>
-### ERR_UNKNOWN_CREDENTIAL
+### `ERR_UNKNOWN_CREDENTIAL`
 
 A Unix group or user identifier that does not exist was passed.
 
 <a id="ERR_UNKNOWN_ENCODING"></a>
-### ERR_UNKNOWN_ENCODING
+### `ERR_UNKNOWN_ENCODING`
 
 An invalid or unknown encoding option was passed to an API.
 
 <a id="ERR_UNKNOWN_FILE_EXTENSION"></a>
-### ERR_UNKNOWN_FILE_EXTENSION
+### `ERR_UNKNOWN_FILE_EXTENSION`
 
 > Stability: 1 - Experimental
 
@@ -1945,36 +1945,36 @@ An attempt was made to load a module with an unknown or unsupported file
 extension.
 
 <a id="ERR_UNKNOWN_MODULE_FORMAT"></a>
-### ERR_UNKNOWN_MODULE_FORMAT
+### `ERR_UNKNOWN_MODULE_FORMAT`
 
 > Stability: 1 - Experimental
 
 An attempt was made to load a module with an unknown or unsupported format.
 
 <a id="ERR_UNKNOWN_SIGNAL"></a>
-### ERR_UNKNOWN_SIGNAL
+### `ERR_UNKNOWN_SIGNAL`
 
 An invalid or unknown process signal was passed to an API expecting a valid
 signal (such as [`subprocess.kill()`][]).
 
 <a id="ERR_V8BREAKITERATOR"></a>
-### ERR_V8BREAKITERATOR
+### `ERR_V8BREAKITERATOR`
 
 The V8 `BreakIterator` API was used but the full ICU data set is not installed.
 
 <a id="ERR_VALID_PERFORMANCE_ENTRY_TYPE"></a>
-### ERR_VALID_PERFORMANCE_ENTRY_TYPE
+### `ERR_VALID_PERFORMANCE_ENTRY_TYPE`
 
 While using the Performance Timing API (`perf_hooks`), no valid performance
 entry types were found.
 
 <a id="ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING"></a>
-### ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING
+### `ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING`
 
 A dynamic import callback was not specified.
 
 <a id="ERR_VM_MODULE_ALREADY_LINKED"></a>
-### ERR_VM_MODULE_ALREADY_LINKED
+### `ERR_VM_MODULE_ALREADY_LINKED`
 
 The module attempted to be linked is not eligible for linking, because of one of
 the following reasons:
@@ -1984,72 +1984,72 @@ the following reasons:
 * Linking has failed for this module (`linkingStatus` is `'errored'`)
 
 <a id="ERR_VM_MODULE_DIFFERENT_CONTEXT"></a>
-### ERR_VM_MODULE_DIFFERENT_CONTEXT
+### `ERR_VM_MODULE_DIFFERENT_CONTEXT`
 
 The module being returned from the linker function is from a different context
 than the parent module. Linked modules must share the same context.
 
 <a id="ERR_VM_MODULE_LINKING_ERRORED"></a>
-### ERR_VM_MODULE_LINKING_ERRORED
+### `ERR_VM_MODULE_LINKING_ERRORED`
 
 The linker function returned a module for which linking has failed.
 
 <a id="ERR_VM_MODULE_NOT_MODULE"></a>
-### ERR_VM_MODULE_NOT_MODULE
+### `ERR_VM_MODULE_NOT_MODULE`
 
 The fulfilled value of a linking promise is not a `vm.Module` object.
 
 <a id="ERR_VM_MODULE_STATUS"></a>
-### ERR_VM_MODULE_STATUS
+### `ERR_VM_MODULE_STATUS`
 
 The current module's status does not allow for this operation. The specific
 meaning of the error depends on the specific function.
 
 <a id="ERR_WASI_ALREADY_STARTED"></a>
-### ERR_WASI_ALREADY_STARTED
+### `ERR_WASI_ALREADY_STARTED`
 
 The WASI instance has already started.
 
 <a id="ERR_WORKER_INVALID_EXEC_ARGV"></a>
-### ERR_WORKER_INVALID_EXEC_ARGV
+### `ERR_WORKER_INVALID_EXEC_ARGV`
 
 The `execArgv` option passed to the `Worker` constructor contains
 invalid flags.
 
 <a id="ERR_WORKER_OUT_OF_MEMORY"></a>
-### ERR_WORKER_OUT_OF_MEMORY
+### `ERR_WORKER_OUT_OF_MEMORY`
 
 The `Worker` instance terminated because it reached its memory limit.
 
 <a id="ERR_WORKER_PATH"></a>
-### ERR_WORKER_PATH
+### `ERR_WORKER_PATH`
 
 The path for the main script of a worker is neither an absolute path
 nor a relative path starting with `./` or `../`.
 
 <a id="ERR_WORKER_UNSERIALIZABLE_ERROR"></a>
-### ERR_WORKER_UNSERIALIZABLE_ERROR
+### `ERR_WORKER_UNSERIALIZABLE_ERROR`
 
 All attempts at serializing an uncaught exception from a worker thread failed.
 
 <a id="ERR_WORKER_UNSUPPORTED_EXTENSION"></a>
-### ERR_WORKER_UNSUPPORTED_EXTENSION
+### `ERR_WORKER_UNSUPPORTED_EXTENSION`
 
 The pathname used for the main script of a worker has an
 unknown file extension.
 
 <a id="ERR_WORKER_UNSUPPORTED_OPERATION"></a>
-### ERR_WORKER_UNSUPPORTED_OPERATION
+### `ERR_WORKER_UNSUPPORTED_OPERATION`
 
 The requested functionality is not supported in worker threads.
 
 <a id="ERR_ZLIB_INITIALIZATION_FAILED"></a>
-### ERR_ZLIB_INITIALIZATION_FAILED
+### `ERR_ZLIB_INITIALIZATION_FAILED`
 
 Creation of a [`zlib`][] object failed due to incorrect configuration.
 
 <a id="HPE_HEADER_OVERFLOW"></a>
-### HPE_HEADER_OVERFLOW
+### `HPE_HEADER_OVERFLOW`
 <!-- YAML
 changes:
   - version: v11.4.0
@@ -2063,7 +2063,7 @@ HTTP parsing will abort without a request or response object being created, and
 an `Error` with this code will be emitted.
 
 <a id="MODULE_NOT_FOUND"></a>
-### MODULE_NOT_FOUND
+### `MODULE_NOT_FOUND`
 <!-- YAML
 changes:
   - version: v12.0.0
@@ -2079,7 +2079,7 @@ A module file could not be resolved while attempting a [`require()`][] or
 > been removed.
 
 <a id="ERR_CANNOT_TRANSFER_OBJECT"></a>
-### ERR_CANNOT_TRANSFER_OBJECT
+### `ERR_CANNOT_TRANSFER_OBJECT`
 <!--
 added: v10.5.0
 removed: v12.5.0
@@ -2089,7 +2089,7 @@ The value passed to `postMessage()` contained an object that is not supported
 for transferring.
 
 <a id="ERR_CLOSED_MESSAGE_PORT"></a>
-### ERR_CLOSED_MESSAGE_PORT
+### `ERR_CLOSED_MESSAGE_PORT`
 <!-- YAML
 added: v10.5.0
 removed: v11.12.0
@@ -2099,7 +2099,7 @@ There was an attempt to use a `MessagePort` instance in a closed
 state, usually after `.close()` has been called.
 
 <a id="ERR_CRYPTO_HASH_DIGEST_NO_UTF16"></a>
-### ERR_CRYPTO_HASH_DIGEST_NO_UTF16
+### `ERR_CRYPTO_HASH_DIGEST_NO_UTF16`
 <!-- YAML
 added: v9.0.0
 removed: v12.12.0
@@ -2111,7 +2111,7 @@ causing the method to return a string rather than a `Buffer`, the UTF-16
 encoding (e.g. `ucs` or `utf16le`) is not supported.
 
 <a id="ERR_HTTP2_FRAME_ERROR"></a>
-### ERR_HTTP2_FRAME_ERROR
+### `ERR_HTTP2_FRAME_ERROR`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2121,7 +2121,7 @@ Used when a failure occurs sending an individual frame on the HTTP/2
 session.
 
 <a id="ERR_HTTP2_HEADERS_OBJECT"></a>
-### ERR_HTTP2_HEADERS_OBJECT
+### `ERR_HTTP2_HEADERS_OBJECT`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2130,7 +2130,7 @@ removed: v10.0.0
 Used when an HTTP/2 Headers Object is expected.
 
 <a id="ERR_HTTP2_HEADER_REQUIRED"></a>
-### ERR_HTTP2_HEADER_REQUIRED
+### `ERR_HTTP2_HEADER_REQUIRED`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2139,7 +2139,7 @@ removed: v10.0.0
 Used when a required header is missing in an HTTP/2 message.
 
 <a id="ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND"></a>
-### ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND
+### `ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2149,7 +2149,7 @@ HTTP/2 informational headers must only be sent *prior* to calling the
 `Http2Stream.prototype.respond()` method.
 
 <a id="ERR_HTTP2_STREAM_CLOSED"></a>
-### ERR_HTTP2_STREAM_CLOSED
+### `ERR_HTTP2_STREAM_CLOSED`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2159,7 +2159,7 @@ Used when an action has been performed on an HTTP/2 Stream that has already
 been closed.
 
 <a id="ERR_HTTP_INVALID_CHAR"></a>
-### ERR_HTTP_INVALID_CHAR
+### `ERR_HTTP_INVALID_CHAR`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2169,7 +2169,7 @@ Used when an invalid character is found in an HTTP response status message
 (reason phrase).
 
 <a id="ERR_INDEX_OUT_OF_RANGE"></a>
-### ERR_INDEX_OUT_OF_RANGE
+### `ERR_INDEX_OUT_OF_RANGE`
 <!-- YAML
   added: v10.0.0
   removed: v11.0.0
@@ -2177,7 +2177,7 @@ Used when an invalid character is found in an HTTP response status message
 A given index was out of the accepted range (e.g. negative offsets).
 
 <a id="ERR_NAPI_CONS_PROTOTYPE_OBJECT"></a>
-### ERR_NAPI_CONS_PROTOTYPE_OBJECT
+### `ERR_NAPI_CONS_PROTOTYPE_OBJECT`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2186,13 +2186,13 @@ removed: v10.0.0
 Used by the `N-API` when `Constructor.prototype` is not an object.
 
 <a id="ERR_NO_LONGER_SUPPORTED"></a>
-### ERR_NO_LONGER_SUPPORTED
+### `ERR_NO_LONGER_SUPPORTED`
 
 A Node.js API was called in an unsupported manner, such as
 `Buffer.write(string, encoding, offset[, length])`.
 
 <a id="ERR_OUTOFMEMORY"></a>
-### ERR_OUTOFMEMORY
+### `ERR_OUTOFMEMORY`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2202,7 +2202,7 @@ Used generically to identify that an operation caused an out of memory
 condition.
 
 <a id="ERR_PARSE_HISTORY_DATA"></a>
-### ERR_PARSE_HISTORY_DATA
+### `ERR_PARSE_HISTORY_DATA`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2211,7 +2211,7 @@ removed: v10.0.0
 The `repl` module was unable to parse data from the REPL history file.
 
 <a id="ERR_STDERR_CLOSE"></a>
-### ERR_STDERR_CLOSE
+### `ERR_STDERR_CLOSE`
 <!-- YAML
 removed: v10.12.0
 changes:
@@ -2226,7 +2226,7 @@ An attempt was made to close the `process.stderr` stream. By design, Node.js
 does not allow `stdout` or `stderr` streams to be closed by user code.
 
 <a id="ERR_STDOUT_CLOSE"></a>
-### ERR_STDOUT_CLOSE
+### `ERR_STDOUT_CLOSE`
 <!-- YAML
 removed: v10.12.0
 changes:
@@ -2241,7 +2241,7 @@ An attempt was made to close the `process.stdout` stream. By design, Node.js
 does not allow `stdout` or `stderr` streams to be closed by user code.
 
 <a id="ERR_STREAM_READ_NOT_IMPLEMENTED"></a>
-### ERR_STREAM_READ_NOT_IMPLEMENTED
+### `ERR_STREAM_READ_NOT_IMPLEMENTED`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2251,7 +2251,7 @@ Used when an attempt is made to use a readable stream that has not implemented
 [`readable._read()`][].
 
 <a id="ERR_TLS_RENEGOTIATION_FAILED"></a>
-### ERR_TLS_RENEGOTIATION_FAILED
+### `ERR_TLS_RENEGOTIATION_FAILED`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2260,7 +2260,7 @@ removed: v10.0.0
 Used when a TLS renegotiation request has failed in a non-specific way.
 
 <a id="ERR_UNKNOWN_BUILTIN_MODULE"></a>
-### ERR_UNKNOWN_BUILTIN_MODULE
+### `ERR_UNKNOWN_BUILTIN_MODULE`
 <!-- YAML
 added: v8.0.0
 removed: v9.0.0
@@ -2272,7 +2272,7 @@ code. Instances of this error point to an internal bug within the Node.js
 binary itself.
 
 <a id="ERR_UNKNOWN_STDIN_TYPE"></a>
-### ERR_UNKNOWN_STDIN_TYPE
+### `ERR_UNKNOWN_STDIN_TYPE`
 <!-- YAML
 added: v8.0.0
 removed: v11.7.0
@@ -2283,7 +2283,7 @@ type. This error is usually an indication of a bug within Node.js itself,
 although it is possible for user code to trigger it.
 
 <a id="ERR_UNKNOWN_STREAM_TYPE"></a>
-### ERR_UNKNOWN_STREAM_TYPE
+### `ERR_UNKNOWN_STREAM_TYPE`
 <!-- YAML
 added: v8.0.0
 removed: v11.7.0
@@ -2294,7 +2294,7 @@ An attempt was made to launch a Node.js process with an unknown `stdout` or
 itself, although it is possible for user code to trigger it.
 
 <a id="ERR_VALUE_OUT_OF_RANGE"></a>
-### ERR_VALUE_OUT_OF_RANGE
+### `ERR_VALUE_OUT_OF_RANGE`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2303,12 +2303,12 @@ removed: v10.0.0
 Used when a given value is out of the accepted range.
 
 <a id="ERR_VM_MODULE_NOT_LINKED"></a>
-### ERR_VM_MODULE_NOT_LINKED
+### `ERR_VM_MODULE_NOT_LINKED`
 
 The module must be successfully linked before instantiation.
 
 <a id="ERR_ZLIB_BINDING_CLOSED"></a>
-### ERR_ZLIB_BINDING_CLOSED
+### `ERR_ZLIB_BINDING_CLOSED`
 <!-- YAML
 added: v9.0.0
 removed: v10.0.0
@@ -2323,7 +2323,7 @@ These errors have never been released, but had been present on master between
 releases.
 
 <a id="ERR_ENTRY_TYPE_MISMATCH"></a>
-#### ERR_ENTRY_TYPE_MISMATCH
+#### `ERR_ENTRY_TYPE_MISMATCH`
 
 > Stability: 1 - Experimental
 
@@ -2335,48 +2335,48 @@ a `.js` file where the nearest parent `package.json` either lacks a `"type"`
 field or contains `"type": "commonjs"`.
 
 <a id="ERR_FS_WATCHER_ALREADY_STARTED"></a>
-#### ERR_FS_WATCHER_ALREADY_STARTED
+#### `ERR_FS_WATCHER_ALREADY_STARTED`
 
 An attempt was made to start a watcher returned by `fs.watch()` that has
 already been started.
 
 <a id="ERR_FS_WATCHER_NOT_STARTED"></a>
-#### ERR_FS_WATCHER_NOT_STARTED
+#### `ERR_FS_WATCHER_NOT_STARTED`
 
 An attempt was made to initiate operations on a watcher returned by
 `fs.watch()` that has not yet been started.
 
 <a id="ERR_HTTP2_ALREADY_SHUTDOWN"></a>
-#### ERR_HTTP2_ALREADY_SHUTDOWN
+#### `ERR_HTTP2_ALREADY_SHUTDOWN`
 
 Occurs with multiple attempts to shutdown an HTTP/2 session.
 
 <a id="ERR_HTTP2_ERROR"></a>
-#### ERR_HTTP2_ERROR
+#### `ERR_HTTP2_ERROR`
 
 A non-specific HTTP/2 error has occurred.
 
 <a id="ERR_INVALID_REPL_HISTORY"></a>
-#### ERR_INVALID_REPL_HISTORY
+#### `ERR_INVALID_REPL_HISTORY`
 
 Used in the `repl` in case the old history file is used and an error occurred
 while trying to read and parse it.
 
 <a id="ERR_INVALID_REPL_TYPE"></a>
-#### ERR_INVALID_REPL_TYPE
+#### `ERR_INVALID_REPL_TYPE`
 
 > Stability: 1 - Experimental
 
 The `--entry-type=...` flag is not compatible with the Node.js REPL.
 
 <a id="ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK"></a>
-#### ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK
+#### `ERR_MISSING_DYNAMIC_INSTANTIATE_HOOK`
 
 Used when an [ES Module][] loader hook specifies `format: 'dynamic'` but does
 not provide a `dynamicInstantiate` hook.
 
 <a id="ERR_STREAM_HAS_STRINGDECODER"></a>
-#### ERR_STREAM_HAS_STRINGDECODER
+#### `ERR_STREAM_HAS_STRINGDECODER`
 
 Used to prevent an abort if a string decoder was set on the Socket.
 
@@ -2388,13 +2388,13 @@ instance.setEncoding('utf8');
 ```
 
 <a id="ERR_STRING_TOO_LARGE"></a>
-#### ERR_STRING_TOO_LARGE
+#### `ERR_STRING_TOO_LARGE`
 
 An attempt has been made to create a string larger than the maximum allowed
 size.
 
 <a id="ERR_TTY_WRITABLE_NOT_READABLE"></a>
-#### ERR_TTY_WRITABLE_NOT_READABLE
+#### `ERR_TTY_WRITABLE_NOT_READABLE`
 
 This `Error` is thrown when a read is attempted on a TTY `WriteStream`,
 such as `process.stdout.on('data')`.