Browse Source

doc: make spelling of behavior consistent

In the api docs there were some instances of behaviour
and many more with behavior.  I was asked as part of a review
on a different PR which one to use and went with behavior
to be consistent with the majority.

Our style guide states that American English spelling is preferred.

PR-URL: https://github.com/nodejs/node/pull/13245
Reviewed-By: Alexey Orlenko <eaglexrlnk@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Kunal Pathak <kunal.pathak@microsoft.com>
v6.x
Michael Dawson 8 years ago
committed by Myles Borins
parent
commit
a7b51af049
No known key found for this signature in database GPG Key ID: 933B01F40B5CA946
  1. 2
      doc/api/crypto.md
  2. 2
      doc/api/process.md
  3. 2
      doc/api/tls.md

2
doc/api/crypto.md

@ -1645,7 +1645,7 @@ the `crypto`, `tls`, and `https` modules and are generally specific to OpenSSL.
<tr>
<td><code>SSL_OP_CIPHER_SERVER_PREFERENCE</code></td>
<td>Attempts to use the server's preferences instead of the client's when
selecting a cipher. Behaviour depends on protocol version. See
selecting a cipher. Behavior depends on protocol version. See
https://www.openssl.org/docs/man1.0.2/ssl/SSL_CTX_set_options.html.</td>
</tr>
<tr>

2
doc/api/process.md

@ -1590,7 +1590,7 @@ important ways:
- TTYs (Terminals): *asynchronous* on Windows, *synchronous* on Unix
- Pipes (and sockets): *synchronous* on Windows, *asynchronous* on Unix
These behaviours are partly for historical reasons, as changing them would
These behaviors are partly for historical reasons, as changing them would
create backwards incompatibility, but they are also expected by some users.
Synchronous writes avoid problems such as output written with `console.log()` or

2
doc/api/tls.md

@ -954,7 +954,7 @@ added: v0.11.13
`"SSLv23_method"`. The possible values are listed as [SSL_METHODS][], use
the function names as strings. For example, `"SSLv3_method"` to force SSL
version 3.
* `secureOptions` {number} Optionally affect the OpenSSL protocol behaviour,
* `secureOptions` {number} Optionally affect the OpenSSL protocol behavior,
which is not usually necessary. This should be used carefully if at all!
Value is a numeric bitmask of the `SSL_OP_*` options from
[OpenSSL Options][].

Loading…
Cancel
Save