From c61eb46149380c867daa3f678056d55fcc8aa9c7 Mon Sep 17 00:00:00 2001 From: Matt Kraai Date: Fri, 21 Dec 2018 09:15:16 -0800 Subject: [PATCH] Fix misspelling of "capacity" --- book/src/by-example/tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/by-example/tasks.md b/book/src/by-example/tasks.md index 0b51d8b93d..b950f703af 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