Skip to content

Commit 319c275

Browse files
committed
doc: use _can_ to describe actions in quic.md
Per Microsoft style guide: > When ability is what you need to express, it's OK to use _can_ to > describe actions or tasks that the reader or program is able to do. > Use _might_ to express possibility. Don't use _may_, which might be > interpreted as providing permission. Refs: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/c/can-may Refs: #34353 (comment) PR-URL: #34613 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de>
1 parent 3ea94ec commit 319c275

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/api/quic.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2465,7 +2465,7 @@ start of a new `QuicServerSession`. It is invoked with three arguments:
24652465
* `servername` {string} The SNI server name specified by the client.
24662466
* `ciphers` {string[]} The array of TLS 1.3 ciphers specified by the client.
24672467

2468-
The `clientHelloHandler` *may* return a new {tls.SecureContext} object that will
2468+
The `clientHelloHandler` can return a new {tls.SecureContext} object that will
24692469
be used to continue the TLS handshake. If the function returns `undefined`, the
24702470
default {tls.SecureContext} will be used. Returning any other value will cause
24712471
an error to be thrown that will destroy the `QuicServerSession` instance.

0 commit comments

Comments
 (0)