fix lint issues in doc/api/http2.md

Author: mcollina

doc/api/http2.md

@@ -1117,7 +1117,7 @@ When sending a request, header values must not contain characters outside the
 characters.
 
 This strict validation can be relaxed via the `httpValidation` option of
-[`http2.connect()`][], which allows control characters in header values
+[`http2.connect()`](#http2connectauthority-options-listener), which allows control characters in header values
 when set to `'relaxed'` or `'insecure'`.
 
 When a `ClientHttp2Session` is first created, the socket may not yet be
@@ -2986,9 +2986,9 @@ changes:
       values, aligning with the [Fetch specification][].
     * `'insecure'`: Disables all header value validation (equivalent to
       `insecureHTTPParser` in HTTP/1).
-    When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
-    automatically disabled.
-    **Default:** `'strict'`.
+      When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
+      automatically disabled.
+      **Default:** `'strict'`.
   * `...options` {Object} Any [`net.createServer()`][] option can be provided.
 * `onRequestHandler` {Function} See [Compatibility API][]
 * Returns: {Http2Server}
@@ -3186,9 +3186,9 @@ changes:
       values, aligning with the [Fetch specification][].
     * `'insecure'`: Disables all header value validation (equivalent to
       `insecureHTTPParser` in HTTP/1).
-    When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
-    automatically disabled.
-    **Default:** `'strict'`.
+      When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
+      automatically disabled.
+      **Default:** `'strict'`.
   * `http1Options` {Object} An options object for configuring the HTTP/1
     fallback when `allowHTTP1` is `true`. These options are passed to the
     underlying HTTP/1 server. See [`http.createServer()`][] for available
@@ -3371,9 +3371,9 @@ changes:
       values, aligning with the [Fetch specification][].
     * `'insecure'`: Disables all header value validation (equivalent to
       `insecureHTTPParser` in HTTP/1).
-    When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
-    automatically disabled.
-    **Default:** `'strict'`.
+      When set to `'relaxed'` or `'insecure'`, `strictSingleValueFields` is
+      automatically disabled.
+      **Default:** `'strict'`.
 * `listener` {Function} Will be registered as a one-time listener of the
   [`'connect'`][] event.
 * Returns: {ClientHttp2Session}
@@ -5072,6 +5072,7 @@ you need to implement any fall-back behavior yourself.
 [ALPN negotiation]: #alpn-negotiation
 [Compatibility API]: #compatibility-api
 [DEP0202]: deprecations.md#dep0202-http1incomingmessage-and-http1serverresponse-options-of-http2-servers
+[Fetch specification]: https://fetch.spec.whatwg.org/
 [HTTP/1]: http.md
 [HTTP/2]: https://tools.ietf.org/html/rfc7540
 [HTTP/2 Headers Object]: #headers-object
@@ -5134,4 +5135,3 @@ you need to implement any fall-back behavior yourself.
 [`tls.createServer()`]: tls.md#tlscreateserveroptions-secureconnectionlistener
 [`writable.writableFinished`]: stream.md#writablewritablefinished
 [error code]: #error-codes-for-rst_stream-and-goaway
-[Fetch specification]: https://fetch.spec.whatwg.org/