aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar bors[bot] <26634292+bors[bot]@users.noreply.github.com> 2021-09-27 11:43:24 +0000
committerGravatar GitHub <noreply@github.com> 2021-09-27 11:43:24 +0000
commit58a492057654610055b2cad08a227e0b76a57a77 (patch)
tree59ea5ed576ca7427630eb8303e2761145f0b836a
parent380a20859cf09c631467c4c49db27dd359f231c0 (diff)
parentf37a928c360ab902fa1fb1b0b92c23ee748c06e7 (diff)
downloadrtic-58a492057654610055b2cad08a227e0b76a57a77.tar.gz
rtic-58a492057654610055b2cad08a227e0b76a57a77.tar.zst
rtic-58a492057654610055b2cad08a227e0b76a57a77.zip
Merge #534
534: Fixing bad english r=AfoHT a=korken89 Co-authored-by: Emil Fresk <emil.fresk@gmail.com>
-rw-r--r--book/en/src/by-example/hardware_tasks.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/book/en/src/by-example/hardware_tasks.md b/book/en/src/by-example/hardware_tasks.md
index cb0cf9f6..d5968761 100644
--- a/book/en/src/by-example/hardware_tasks.md
+++ b/book/en/src/by-example/hardware_tasks.md
@@ -1,6 +1,6 @@
# Hardware tasks
-In it's core RTIC is based on using the interrupt controller in the hardware to do scheduling and
+At its core RTIC is based on using the interrupt controller in the hardware to do scheduling and
run tasks, as all tasks in the framework are run as interrupt handlers (except `#[init]` and
`#[idle]`). This also means that you can directly bind tasks to interrupt handlers.