summaryrefslogtreecommitdiffstats
path: root/tokio/src/sync/mod.rs
diff options
context:
space:
mode:
authorMatthijs Brobbel <m1brobbel@gmail.com>2020-04-29 22:06:40 +0200
committerGitHub <noreply@github.com>2020-04-29 13:06:40 -0700
commitc52b78b7925f883289853dee5748b93a89e29bb1 (patch)
tree7c3226ac208f594b2136223aac8c64e2b3a2097a /tokio/src/sync/mod.rs
parent1d280608366d15728ac0983ef71e5ea389e0169d (diff)
chore: fix a typo (#2461)
Diffstat (limited to 'tokio/src/sync/mod.rs')
-rw-r--r--tokio/src/sync/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/tokio/src/sync/mod.rs b/tokio/src/sync/mod.rs
index 8a6aabde..263ec62c 100644
--- a/tokio/src/sync/mod.rs
+++ b/tokio/src/sync/mod.rs
@@ -126,7 +126,7 @@
//! pressure.
//!
//! A common concurrency pattern for resource management is to spawn a task
-//! dedicated to managing that resource and using message passing betwen other
+//! dedicated to managing that resource and using message passing between other
//! tasks to interact with the resource. The resource may be anything that may
//! not be concurrently used. Some examples include a socket and program state.
//! For example, if multiple tasks need to send data over a single socket, spawn