summaryrefslogtreecommitdiffstats
path: root/doc/user/timer.t
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>2008-07-15 21:49:31 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>2008-07-15 21:49:31 +0000
commit4dc6a4684f59ec33e621895e5296e924238d89c8 (patch)
treebcb9e92c11c025c2a68e6a002e6cf59fccba0414 /doc/user/timer.t
parentSpacing. (diff)
downloadrtems-4dc6a4684f59ec33e621895e5296e924238d89c8.tar.bz2
2008-07-15 Joel Sherrill <joel.sherrill@OARcorp.com>
* user/barrier.t, user/clock.t, user/dpmem.t, user/msg.t, user/part.t, user/region.t, user/rtmon.t, user/sem.t, user/task.t, user/timer.t: Correct documentation typos noticed and thankfully reported by Fabrício de Novaes Kucinskis <fabricio@dea.inpe.br>
Diffstat (limited to '')
-rw-r--r--doc/user/timer.t2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/timer.t b/doc/user/timer.t
index 3b929a6e40..de9dc5a04a 100644
--- a/doc/user/timer.t
+++ b/doc/user/timer.t
@@ -68,7 +68,7 @@ in task rather than interrupt space, the application is
allowed a bit more flexibility in what operations a timer
service routine can perform. For example, the Timer Server
can be configured to have a floating point context in which case
-it would be save to perform floating point operations
+it would be safe to perform floating point operations
from a task-based timer. Most of the time, executing floating
point instructions from an interrupt service routine
is not considered safe. However, since the Timer Server task