diff options
author | Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> | 2023-06-29 08:55:12 +0200 |
---|---|---|
committer | Pauli <pauli@openssl.org> | 2023-07-01 00:10:15 +1000 |
commit | 6a2b8269a8fb31a0c04b5f4f1ac1074c53319135 (patch) | |
tree | 4599f6d1165d5151ef0651698d86ad7f83accd11 /doc/designs/quic-design | |
parent | e8104bb87e05c69bd62c74b43304eed4ab92ad6d (diff) | |
download | openssl-6a2b8269a8fb31a0c04b5f4f1ac1074c53319135.tar.gz |
Fix new typos found by codespell in documentation
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/21322)
Diffstat (limited to 'doc/designs/quic-design')
-rw-r--r-- | doc/designs/quic-design/quic-api-ssl-funcs.md | 2 | ||||
-rw-r--r-- | doc/designs/quic-design/quic-api.md | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/designs/quic-design/quic-api-ssl-funcs.md b/doc/designs/quic-design/quic-api-ssl-funcs.md index da0eefaf47..6ff536b845 100644 --- a/doc/designs/quic-design/quic-api-ssl-funcs.md +++ b/doc/designs/quic-design/quic-api-ssl-funcs.md @@ -835,7 +835,7 @@ Q&A For TLS-Related Calls QUIC always uses AES-128-GCM for Initial packets. At this time the handshake layer has not negotiated a ciphersuite so it has no “current” cipher. We could return AES-128-GCM here, but it seems reasonable to just return NULL as the -encryption is mostly for protection against accidential modification and not +encryption is mostly for protection against accidental modification and not “real” encryption. From the perspective of the Handshake layer encryption is not active yet. An application using QUIC can always interpret NULL as meaning AES-128-GCM is being used if needed as this is implied by using QUIC. diff --git a/doc/designs/quic-design/quic-api.md b/doc/designs/quic-design/quic-api.md index 2317f54c44..c3d21514ad 100644 --- a/doc/designs/quic-design/quic-api.md +++ b/doc/designs/quic-design/quic-api.md @@ -433,7 +433,7 @@ Should not require any changes. | New | Never | Yes | CS | Advances the QUIC state machine to the extent feasible, potentially performing -network I/O. Also compatible with DTLSv1 and supercedes `DTLSv1_handle_timeout` +network I/O. Also compatible with DTLSv1 and supersedes `DTLSv1_handle_timeout` for all use cases. #### `SSL_get_event_timeout` @@ -447,7 +447,7 @@ event, if any. This is similar to the existing `DTLSv1_get_timeout` function, but it is not specific to DTLSv1. It is also usable for DTLSv1 and can become a -protocol-agnostic API for this purpose, superceding `DTLSv1_get_timeout` for all +protocol-agnostic API for this purpose, superseding `DTLSv1_get_timeout` for all use cases. The design is similar to that of `DTLSv1_get_timeout` and uses a `struct @@ -1617,7 +1617,7 @@ initial call to `SSL_read` implying use of a remotely-initiated stream. However, this would mean we are creating state tracking a remotely-initiated stream before the peer has signalled it. This would work in the happy case where the client is connected to a compatible server but may result in strange -inconsistencies of QUIC internal state if a client is accidentially connected to +inconsistencies of QUIC internal state if a client is accidentally connected to an incompatible peer. Since the peer ought to be the authority on the streams it creates, this seems like an undesirable approach. |