mirror/rtic
1
0
Fork 0
mirror of https://github.com/rtic-rs/rtic.git synced 2024-12-25 03:19:34 +01:00
Code Issues Projects Releases Packages Wiki Activity

Merge #584

Browse source 
584: mq/minor corrections r=korken89 a=mareq



Co-authored-by: Mareq Balint <mareq@balint.eu>
This commit is contained in:
bors[bot] 2022-01-08 06:19:22 +00:00 committed by GitHub
commit d51aaf3ad3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
book/en/src/by-example/resources.md
View file

@ -6,7 +6,7 @@ storage and safe accesses without the use of `unsafe` code.
RTIC resources are visible only to functions declared within the `#[app]` module and the framework
gives the user complete control (on a per-task basis) over resource accessibility.
Declaration of system-wide resources are by annotating **two** `struct`s within the `#[app]` module
Declaration of system-wide resources is done by annotating **two** `struct`s within the `#[app]` module
with the attribute `#[local]` and `#[shared]`.
Each field in these structures corresponds to a different resource (identified by field name).
The difference between these two sets of resources will be covered below.

2
book/en/src/by-example/software_tasks.md
View file

@ -10,7 +10,7 @@ bound interrupt vector.
These free interrupts used as dispatchers are interrupt vectors not used by hardware tasks.
The `#[task]` attribute used on a function declare it as a software tasks.
The static method `task_name::spawn()` spawn (start) a software task and
The static method `task_name::spawn()` spawns (starts) a software task and
given that there are no higher priority tasks running the task will start executing directly.
A list of “free” and usable interrupts allows the framework to dispatch software tasks.