diff options
| author | Daryl Haresign <github@daryl.haresign.com> | 2015-04-25 00:00:31 -0400 |
|---|---|---|
| committer | Saúl Ibarra Corretgé <saghul@gmail.com> | 2015-04-28 22:36:33 +0200 |
| commit | 706362083e7b083d7cc1a157a180dcc007988d75 (patch) | |
| tree | 26af50ee1cdc211bd44e26ec2a14dbb9c611b84a /docs/src | |
| parent | 8fac49d0fcf85d3147cbb1ed8b0481d9001c4860 (diff) | |
| download | libuv-706362083e7b083d7cc1a157a180dcc007988d75.tar.gz libuv-706362083e7b083d7cc1a157a180dcc007988d75.zip | |
docs: add some missing words
PR-URL: https://github.com/libuv/libuv/pull/332
Reviewed-By: Saúl Ibarra Corretgé <saghul@gmail.com>
Diffstat (limited to 'docs/src')
| -rw-r--r-- | docs/src/design.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/src/design.rst b/docs/src/design.rst index 63141bed..34c3cff6 100644 --- a/docs/src/design.rst +++ b/docs/src/design.rst @@ -40,7 +40,7 @@ The I/O loop The I/O (or event) loop is the central part of libuv. It establishes the content for all I/O operations, and it's meant to be tied to a single thread. One can run multiple event loops as long as each runs in a different thread. The libuv event loop (or any other API involving -the loop or handles, for that matter) **is not thread-safe** except stated otherwise. +the loop or handles, for that matter) **is not thread-safe** except where stated otherwise. The event loop follows the rather usual single threaded asynchronous I/O approach: all (network) I/O is performed on non-blocking sockets which are polled using the best mechanism available @@ -113,7 +113,7 @@ stages of a loop iteration: .. note:: While the polling mechanism is different, libuv makes the execution model consistent - Unix systems and Windows. + across Unix systems and Windows. File I/O |