aboutsummaryrefslogtreecommitdiffstats
path: root/docs/src
diff options
context:
space:
mode:
authorgdisirio <gdisirio@35acf78f-673a-0410-8e92-d51de3d6d3f4>2010-03-18 16:01:11 +0000
committergdisirio <gdisirio@35acf78f-673a-0410-8e92-d51de3d6d3f4>2010-03-18 16:01:11 +0000
commitcf1b70f486a2696d523d585e91d0e4e5c7b8021c (patch)
tree8bb98eff1c20929200b6c89da6b87ff47bd99af8 /docs/src
parent7ae3e3227ee895c3ed5ac3358411b07276c7838e (diff)
downloadChibiOS-cf1b70f486a2696d523d585e91d0e4e5c7b8021c.tar.gz
ChibiOS-cf1b70f486a2696d523d585e91d0e4e5c7b8021c.tar.bz2
ChibiOS-cf1b70f486a2696d523d585e91d0e4e5c7b8021c.zip
git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@1749 35acf78f-673a-0410-8e92-d51de3d6d3f4
Diffstat (limited to 'docs/src')
-rw-r--r--docs/src/atomic.dox16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/src/atomic.dox b/docs/src/atomic.dox
index 0e9974ff1..d3bc43ba5 100644
--- a/docs/src/atomic.dox
+++ b/docs/src/atomic.dox
@@ -20,38 +20,38 @@
/**
* @page article_atomic Invoking multiple primitives as a single atomic operation
* It is often necessary to invoke multiple operations involving a
- * reschedulation as a single atomic operation.<br>
+ * reschedule as a single atomic operation.<br>
* ChibiOS/RT already implements APIs that perform complex operations, as
* example the API @p chSemSignalWait() performs two operations atomically.<br>
* If more complex operations are required in your application then it is
* possible to build macro-operations, see the following example:
* @code
chSysLock();
-
+
chSemSignalI(&sem1);
chSemSignalI(&sem2);
chMtxUnlockS();
chSchRescheduleS();
-
+
chSysUnlock();
* @endcode
* The above example performs a signal operation on two semaphores, unlocks the
- * last aquired mutex and finally performs a reschedulation. All the operations
+ * last acquired mutex and finally performs a reschedule. All the operations
* are performed atomically.<br>
- * An hypotetical @p chSemSignalSignalWait() operation could be implemented as
+ * An hypothetical @p chSemSignalSignalWait() operation could be implemented as
* follow:
* @code
chSysLock();
-
+
chSemSignalI(&sem1);
chSemSignalI(&sem2);
chSemWaitS(&Sem3); /* May reschedule or not. */
chSchRescheduleS(); /* This one reschedules if necessary. */
-
+
chSysUnlock();
* @endcode
* In general multiple @ref I-Class and (non rescheduling) @ref S-Class APIs
* can be included and the block is terminated by a rescheduling @ref S-Class
* API. An extra @p chSchRescheduleS() can be present at the very end of the
- * block, it only reschedules if a reschedulation is still required.
+ * block, it only reschedules if a reschedule is still required.
*/