This is an automated email from the ASF dual-hosted git repository.
xiaoxiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nuttx.git
The following commit(s) were added to refs/heads/master by this push:
new 8ef723803b docs/implementation: fix minor typos
8ef723803b is described below
commit 8ef723803b41da6cb4227320f63f12134a8ee78a
Author: Yanfeng Liu <[email protected]>
AuthorDate: Sat May 4 06:52:17 2024 +0800
docs/implementation: fix minor typos
This fixes a few minor typos encountered.
Signed-off-by: Yanfeng Liu <[email protected]>
---
Documentation/implementation/bottomhalf_interrupt.rst | 2 +-
Documentation/implementation/critical_sections.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/implementation/bottomhalf_interrupt.rst
b/Documentation/implementation/bottomhalf_interrupt.rst
index 18862dadfe..dbbaa025ae 100644
--- a/Documentation/implementation/bottomhalf_interrupt.rst
+++ b/Documentation/implementation/bottomhalf_interrupt.rst
@@ -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
diff --git a/Documentation/implementation/critical_sections.rst
b/Documentation/implementation/critical_sections.rst
index c5fcd31ffc..227935b012 100644
--- a/Documentation/implementation/critical_sections.rst
+++ b/Documentation/implementation/critical_sections.rst
@@ -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
