docs/implementation: fix minor typos
This fixes a few minor typos encountered. Signed-off-by: Yanfeng Liu <yfliu2008@qq.com>
This commit is contained in:
parent
4b12062667
commit
8ef723803b
@ -6,7 +6,7 @@ RTOS Interrupts
|
||||
===============
|
||||
|
||||
A well-design RTOS depends on the most minimal of interrupt level processing.
|
||||
This is a very different concept that for bare metal programming:
|
||||
This is a very different concept from that for bare metal programming:
|
||||
|
||||
* With bare metal programming most of the real-time work is usually performed
|
||||
in interrupt handlers. Interrupt handler execution may then extend in time
|
||||
|
@ -408,7 +408,7 @@ You have these options:
|
||||
or code when they could be re-designed to use critical sections over shorter code
|
||||
sequences.
|
||||
|
||||
#. In some cases, use of critical sections or disabling of pre-emption could replaced
|
||||
#. In some cases, use of critical sections or disabling of pre-emption could be replaced
|
||||
with a locking semaphore. The scope of the locking effect for the use of such locks
|
||||
is not global but is limited only to tasks that share the same resource. Critical
|
||||
sections should correctly be used only to protect resources that are shared between
|
||||
|
Loading…
Reference in New Issue
Block a user