doc: adjust a/an word usage

doc/api/net.md

@@ -1434,7 +1434,7 @@ read by the original process. To begin reading data from a paused socket, call
 The server can be a TCP server or an [IPC][] server, depending on what it
 [`listen()`][`server.listen()`] to.
 
-Here is an example of an TCP echo server which listens for connections
+Here is an example of a TCP echo server which listens for connections
 on port 8124:
 
 ```js

doc/api/process.md

@@ -340,7 +340,7 @@ changes:
 
 * `err` {Error} The uncaught exception.
 * `origin` {string} Indicates if the exception originates from an unhandled
-  rejection or from an synchronous error. Can either be `'uncaughtException'` or
+  rejection or from a synchronous error. Can either be `'uncaughtException'` or
   `'unhandledRejection'`. The latter is used when in an exception happens in a
   `Promise` based async context (or if a `Promise` is rejected) and
   [`--unhandled-rejections`][] flag set to `strict` or `throw` (which is the

doc/api/util.md

@@ -1283,7 +1283,7 @@ changes:
     be removed from the output. This option is only used when `encoding` is
     `'utf-8'`, `'utf-16be'` or `'utf-16le'`. **Default:** `false`.
 
-Creates an new `TextDecoder` instance. The `encoding` may specify one of the
+Creates a new `TextDecoder` instance. The `encoding` may specify one of the
 supported encodings or an alias.
 
 The `TextDecoder` class is also available on the global object.

doc/api/zlib.md

@@ -128,7 +128,7 @@ The `zlib` module can be used to implement support for the `gzip`, `deflate`
 and `br` content-encoding mechanisms defined by
 [HTTP](https://tools.ietf.org/html/rfc7230#section-4.2).
 
-The HTTP [`Accept-Encoding`][] header is used within an http request to identify
+The HTTP [`Accept-Encoding`][] header is used within an HTTP request to identify
 the compression encodings accepted by the client. The [`Content-Encoding`][]
 header is used to identify the compression encodings actually applied to a
 message.