diff options
| author | Jorge Aparicio <jorge@japaric.io> | 2018-12-21 19:18:50 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-21 19:18:50 +0100 |
| commit | 0d2d0e1e1c054165b8cbe294fedf1193707cddf2 (patch) | |
| tree | e671ca7acec9f74e82e290aa791d0811ec4627e3 /book | |
| parent | 61bb8302856c25cc03726c485b340d1a04e9ca03 (diff) | |
| parent | c61eb46149380c867daa3f678056d55fcc8aa9c7 (diff) | |
Merge pull request #119 from kraai/patch-1
Fix misspelling of "capacity"
Diffstat (limited to 'book')
| -rw-r--r-- | book/src/by-example/tasks.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/book/src/by-example/tasks.md b/book/src/by-example/tasks.md index 0b51d8b..b950f70 100644 --- a/book/src/by-example/tasks.md +++ b/book/src/by-example/tasks.md @@ -48,7 +48,7 @@ Task dispatchers do *not* use any dynamic memory allocation. The memory required to store messages is statically reserved. The framework will reserve enough space for every context to be able to spawn each task at most once. This is a sensible default but the "inbox" capacity of each task can be controlled using -the `capacicy` argument of the `task` attribute. +the `capacity` argument of the `task` attribute. The example below sets the capacity of the software task `foo` to 4. If the capacity is not specified then the second `spawn.foo` call in `UART0` would |