Fix misspelling of "capacity"

This commit is contained in:
Matt Kraai 2018-12-21 09:15:16 -08:00 committed by GitHub
parent 61bb830285
commit c61eb46149
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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 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 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 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 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 capacity is not specified then the second `spawn.foo` call in `UART0` would