Fix typos in overview documentation.

doc/overview/coro.qbk

@@ -133,8 +133,8 @@ A coro can have both a `Yield` and `Return` that are non void at the same time.
 
 [heading Result]
 
-The result type of a coroutine is dermined by both `Yield` and `Return`. Note
-that in the follwing table only the yield output value is considered, i.e.
+The result type of a coroutine is determined by both `Yield` and `Return`. Note
+that in the following table only the yield output value is considered, i.e.
 `T(U)` means `T`.
 
 [table:result_type Result type deduction

doc/overview/cpp20_coroutines.qbk

@@ -251,7 +251,7 @@ namespace into scope:
 Note: To use these operators we must explicitly specify the `use_awaitable`
 completion token.
 
-[heading Lightweight Coroutines Implementing Asynchonous Operations]
+[heading Lightweight Coroutines Implementing Asynchronous Operations]
 
 The `co_composed` template facilitates a lightweight implementation of
 user-defined asynchronous operations using C++20 coroutines. The following

doc/overview/deferred.qbk

@@ -57,7 +57,7 @@ write:
 
 [link boost_asio.reference.deferred deferred],
 [link boost_asio.reference.deferred_t deferred_t],
-[link boost_asio.examples.cpp14_examples.deferred Deferred examples (C++11)],
+[link boost_asio.examples.cpp11_examples.deferred Deferred examples (C++11)],
 [link boost_asio.examples.cpp14_examples.deferred Deferred examples (C++14)].
 
 [endsect]

doc/overview/immediate_completion.qbk

@@ -13,7 +13,7 @@ execution of a completion handler when an asynchronous operation completes
 immediately.
 
 When a supported operation completes immediately (that is, within the
-initiating function) the associated immmediate executor is obtained, and the
+initiating function) the associated immediate executor is obtained, and the
 completion handler is delivered through that executor as if by using
 `boost::asio::dispatch` on that executor. By default, the immediate executor delivers
 the completion handler as if using `boost::asio::post` via the operation's I/O

doc/overview/implementation.qbk

@@ -27,7 +27,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -49,7 +49,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -62,7 +62,7 @@ Scatter-Gather:
 Demultiplexing mechanism:
 
 * If `BOOST_ASIO_HAS_IO_URING` is defined, uses `io_uring` for file-related
-asynchonous operations.
+asynchronous operations.
 
 * Uses `epoll` for demultiplexing other event sources.
 
@@ -77,7 +77,7 @@ that calls `io_context::run()`, `io_context::run_one()`, `io_context::poll()` or
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -99,7 +99,7 @@ calls `io_context::run()`, `io_context::run_one()`, `io_context::poll()` or
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -122,7 +122,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -144,7 +144,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -166,7 +166,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -189,7 +189,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -212,7 +212,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -235,7 +235,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -257,7 +257,7 @@ Threads:
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:
@@ -298,7 +298,7 @@ is created on construction of the first `basic_deadline_timer` or
 
 * One or more additional threads per `io_context` to emulate asynchronous host
 resolution. By default, only one thread is created, but this behaviour may be
-altered via the "resolver" / "threads" [link boost_asio.overview.configuration
+altered via the "resolver" / "threads" [link boost_asio.overview.core.configuration
 configuration option].
 
 Scatter-Gather:

doc/overview/iostreams.qbk

@@ -23,7 +23,7 @@ simple servers. For example:
   io_context ioc;
 
   ip::tcp::endpoint endpoint(tcp::v4(), 80);
-  ip::tcp::acceptor acceptor(ios, endpoint);
+  ip::tcp::acceptor acceptor(ioc, endpoint);
 
   for (;;)
   {