diff options
author | Dimitri Papadopoulos <3234522+DimitriPapadopoulos@users.noreply.github.com> | 2023-05-09 09:06:40 +0200 |
---|---|---|
committer | Pauli <pauli@openssl.org> | 2023-06-15 10:11:46 +1000 |
commit | eb4129e12cdf7fe64b3ce352f539e3dbeb1b1321 (patch) | |
tree | 70ffce338d4927b9053db6c3b7b8e16af9e9b681 /doc/designs/ddd | |
parent | 71cf587ea21c1422640847e358019a51806d2811 (diff) |
Fix typos found by codespell
Typos in doc/man* will be fixed in a different commit.
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20910)
Diffstat (limited to 'doc/designs/ddd')
-rw-r--r-- | doc/designs/ddd/WINDOWS.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/designs/ddd/WINDOWS.md b/doc/designs/ddd/WINDOWS.md index 2c96a9542e..d92c4133d3 100644 --- a/doc/designs/ddd/WINDOWS.md +++ b/doc/designs/ddd/WINDOWS.md @@ -32,7 +32,7 @@ For this reason it's actually common for asynchronous I/O libraries to basically contain two separate implementations of their APIs internally, or at least a substantial chunk of their code (e.g. libuv, nanomsg). It turns out to be easier just to write a poll-based implementation of an I/O reactor and an IOCP-based -implementation than try to overcome the impedence discontinuities. +implementation than try to overcome the impedance discontinuities. The difference between polling and IOCPs is that polling reports *readiness* whereas IOCPs report *completion of an operation*. For example, in the IOCP |