Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/api/crypto.md
Original file line number Diff line number Diff line change
Expand Up @@ -6645,7 +6645,7 @@ See the [list of SSL OP Flags][] for details.
</tr>
<tr>
<td><code>SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS</code></td>
<td>Instructs OpenSSL to disable a SSL 3.0/TLS 1.0 vulnerability
<td>Instructs OpenSSL to disable an SSL 3.0/TLS 1.0 vulnerability
workaround added in OpenSSL 0.9.6d.</td>
</tr>
<tr>
Expand Down
12 changes: 6 additions & 6 deletions doc/api/http.md
Original file line number Diff line number Diff line change
Expand Up @@ -1517,7 +1517,7 @@ changes:
- version: v12.0.0
pr-url: https://github.com/nodejs/node/pull/25605
description: The default behavior will return a 431 Request Header
Fields Too Large if a HPE_HEADER_OVERFLOW error occurs.
Fields Too Large if an HPE_HEADER_OVERFLOW error occurs.
- version: v9.4.0
pr-url: https://github.com/nodejs/node/pull/17672
description: The `rawPacket` is the current buffer that just parsed. Adding
Expand All @@ -1543,8 +1543,8 @@ This event is guaranteed to be passed an instance of the {net.Socket} class,
a subclass of {stream.Duplex}, unless the user specifies a socket
type other than {net.Socket}.

Default behavior is to try close the socket with a HTTP '400 Bad Request',
or a HTTP '431 Request Header Fields Too Large' in the case of a
Default behavior is to try close the socket with an HTTP '400 Bad Request',
or an HTTP '431 Request Header Fields Too Large' in the case of an
[`HPE_HEADER_OVERFLOW`][] error. If the socket is not writable or headers
of the current attached [`http.ServerResponse`][] has been sent, it is
immediately destroyed.
Expand Down Expand Up @@ -2703,7 +2703,7 @@ will result in a [`TypeError`][] being thrown.
added: v10.0.0
-->

Sends a HTTP/1.1 102 Processing message to the client, indicating that
Sends an HTTP/1.1 102 Processing message to the client, indicating that
the request body should be sent.

## Class: `http.IncomingMessage`
Expand Down Expand Up @@ -3690,7 +3690,7 @@ changes:
`readableHighWaterMark` and `writableHighWaterMark`. This affects
`highWaterMark` property of both `IncomingMessage` and `ServerResponse`.
**Default:** See [`stream.getDefaultHighWaterMark()`][].
* `insecureHTTPParser` {boolean} If set to `true`, it will use a HTTP parser
* `insecureHTTPParser` {boolean} If set to `true`, it will use an HTTP parser
with leniency flags enabled. Using the insecure parser should be avoided.
See [`--insecure-http-parser`][] for more information.
**Default:** `false`.
Expand Down Expand Up @@ -4001,7 +4001,7 @@ changes:
request to. **Default:** `'localhost'`.
* `hostname` {string} Alias for `host`. To support [`url.parse()`][],
`hostname` will be used if both `host` and `hostname` are specified.
* `insecureHTTPParser` {boolean} If set to `true`, it will use a HTTP parser
* `insecureHTTPParser` {boolean} If set to `true`, it will use an HTTP parser
with leniency flags enabled. Using the insecure parser should be avoided.
See [`--insecure-http-parser`][] for more information.
**Default:** `false`
Expand Down
4 changes: 2 additions & 2 deletions doc/api/http2.md
Original file line number Diff line number Diff line change
Expand Up @@ -3966,7 +3966,7 @@ const server = createSecureServer(
).listen(8000);

function onRequest(req, res) {
// Detects if it is a HTTPS request or HTTP/2
// Detects if it is an HTTPS request or HTTP/2
const { socket: { alpnProtocol } } = req.httpVersion === '2.0' ?
req.stream.session : req;
res.writeHead(200, { 'content-type': 'application/json' });
Expand All @@ -3990,7 +3990,7 @@ const server = createSecureServer(
).listen(4443);

function onRequest(req, res) {
// Detects if it is a HTTPS request or HTTP/2
// Detects if it is an HTTPS request or HTTP/2
const { socket: { alpnProtocol } } = req.httpVersion === '2.0' ?
req.stream.session : req;
res.writeHead(200, { 'content-type': 'application/json' });
Expand Down
2 changes: 1 addition & 1 deletion doc/api/module.md
Original file line number Diff line number Diff line change
Expand Up @@ -364,7 +364,7 @@ changes:
The module compile cache can be enabled either using the [`module.enableCompileCache()`][]
method or the [`NODE_COMPILE_CACHE=dir`][] environment variable. After it is enabled,
whenever Node.js compiles a CommonJS, a ECMAScript Module, or a TypeScript module, it will
whenever Node.js compiles a CommonJS, an ECMAScript Module, or a TypeScript module, it will
use on-disk [V8 code cache][] persisted in the specified directory to speed up the compilation.
This may slow down the first load of a module graph, but subsequent loads of the same module
graph may get a significant speedup if the contents of the modules do not change.
Expand Down
4 changes: 2 additions & 2 deletions doc/api/tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -1212,7 +1212,7 @@ added: v9.9.0
-->

* Returns: {Buffer|undefined} The latest `Finished` message that has been
sent to the socket as part of a SSL/TLS handshake, or `undefined` if
sent to the socket as part of an SSL/TLS handshake, or `undefined` if
no `Finished` message has been sent yet.

As the `Finished` messages are message digests of the complete handshake
Expand Down Expand Up @@ -1355,7 +1355,7 @@ added: v9.9.0
-->

* Returns: {Buffer|undefined} The latest `Finished` message that is expected
or has actually been received from the socket as part of a SSL/TLS handshake,
or has actually been received from the socket as part of an SSL/TLS handshake,
or `undefined` if there is no `Finished` message so far.

As the `Finished` messages are message digests of the complete handshake
Expand Down
Loading