diff options
| author | Christopher Coverdale <chris.coverdale24@gmail.com> | 2019-12-03 20:01:59 +0000 |
|---|---|---|
| committer | Carl Lerche <me@carllerche.com> | 2019-12-03 12:01:59 -0800 |
| commit | 6efe07c3fba8ef103dd2a03328e8b667371803b3 (patch) | |
| tree | 0e787c668c4bde2f39bb4f4bb993d9f1d947f01e /tokio/src/task | |
| parent | 8a2160a913f4901fd4c81d11b0d10237837738de (diff) | |
Fixing minor spelling mistake in task docs (#1889)
Diffstat (limited to 'tokio/src/task')
| -rw-r--r-- | tokio/src/task/mod.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tokio/src/task/mod.rs b/tokio/src/task/mod.rs index 8b84f210..e336ec9c 100644 --- a/tokio/src/task/mod.rs +++ b/tokio/src/task/mod.rs @@ -4,7 +4,7 @@ //! //! A _task_ is a light weight, non-blocking unit of execution. A task is similar //! to an OS thread, but rather than being managed by the OS scheduler, they are -//! managed by the [Tokio runtime][rt]. Another name for this general patterh is +//! managed by the [Tokio runtime][rt]. Another name for this general pattern is //! [green threads]. If you are familiar with [Go's goroutines], [Kotlin's //! coroutines], or [Erlang's processes], you can think of Tokio's tasks as //! something similar. |