summaryrefslogtreecommitdiffstats
path: root/examples
diff options
context:
space:
mode:
authorJulian Tescher <jatescher@gmail.com>2018-05-08 14:44:17 -0400
committerCarl Lerche <me@carllerche.com>2018-05-08 11:44:17 -0700
commit06b2c402227b4c0f64912e48966f2751dd872ccc (patch)
tree736fceef44b46484e93559bb5e7d0a06e623b3bc /examples
parent68b82f5721cbfa2076f53fa24961ee9273395b39 (diff)
Fix typos (#348)
Diffstat (limited to 'examples')
-rw-r--r--examples/README.md2
-rw-r--r--examples/chat.rs2
-rw-r--r--examples/echo-udp.rs2
-rw-r--r--examples/echo.rs2
-rw-r--r--examples/proxy.rs2
5 files changed, 5 insertions, 5 deletions
diff --git a/examples/README.md b/examples/README.md
index 19f33ff6..931139e3 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -38,7 +38,7 @@ A high level description of each example is:
in multiple terminals and use it to chat between the terminals.
* [`chat-combinator`](chat-combinator.rs) - Similar to `chat`, but this uses a
- much more functional programming approch using combinators.
+ much more functional programming approach using combinators.
* [`proxy`](proxy.rs) - an example proxy server that will forward all connected
TCP clients to the remote address specified when starting the program.
diff --git a/examples/chat.rs b/examples/chat.rs
index a2eb95e1..36a0041b 100644
--- a/examples/chat.rs
+++ b/examples/chat.rs
@@ -157,7 +157,7 @@ impl Peer {
/// This is where a connected client is managed.
///
-/// A `Peer` is also a future representing completly processing the client.
+/// A `Peer` is also a future representing completely processing the client.
///
/// When a `Peer` is created, the first line (representing the client's name)
/// has already been read. When the socket closes, the `Peer` future completes.
diff --git a/examples/echo-udp.rs b/examples/echo-udp.rs
index e25f0936..9a1b9684 100644
--- a/examples/echo-udp.rs
+++ b/examples/echo-udp.rs
@@ -68,6 +68,6 @@ fn main() {
// `map_err` handles the error by logging it and maps the future to a type
// that can be spawned.
//
- // `tokio::run` spanws the task on the Tokio runtime and starts running.
+ // `tokio::run` spawns the task on the Tokio runtime and starts running.
tokio::run(server.map_err(|e| println!("server error = {:?}", e)));
}
diff --git a/examples/echo.rs b/examples/echo.rs
index e4fe65cc..92d65a90 100644
--- a/examples/echo.rs
+++ b/examples/echo.rs
@@ -3,7 +3,7 @@
//! This server will create a TCP listener, accept connections in a loop, and
//! write back everything that's read off of each TCP connection.
//!
-//! Because the Tokio runtime uses a thread poool, each TCP connection is
+//! Because the Tokio runtime uses a thread pool, each TCP connection is
//! processed concurrently with all other TCP connections across multiple
//! threads.
//!
diff --git a/examples/proxy.rs b/examples/proxy.rs
index 42b740df..bed8314a 100644
--- a/examples/proxy.rs
+++ b/examples/proxy.rs
@@ -1,7 +1,7 @@
//! A proxy that forwards data to another server and forwards that server's
//! responses back to clients.
//!
-//! Because the Tokio runtime uses a thread poool, each TCP connection is
+//! Because the Tokio runtime uses a thread pool, each TCP connection is
//! processed concurrently with all other TCP connections across multiple
//! threads.
//!