update examples

1 files changed, 5 insertions, 5 deletions

diff --git a/examples/preemption.rs b/examples/preemption.rs
index 057e4fd..256b9bd 100644
--- a/examples/preemption.rs
+++ b/examples/preemption.rs
@@ -1,4 +1,4 @@
-//! Two tasks running at different priorities with access to the same resource
+//! Two tasks running at *different* priorities with access to the same resource
 #![deny(unsafe_code)]
 #![feature(const_fn)]
 #![feature(proc_macro)]
@@ -17,7 +17,7 @@ app! {
     },
 
     tasks: {
-        // the task `SYS_TICK` has higher priority than `TIM2`
+        // The `SYS_TICK` task has higher priority than `TIM2`
         SYS_TICK: {
             path: sys_tick,
             priority: 2,
@@ -45,7 +45,7 @@ fn idle() -> ! {
 fn sys_tick(_t: &mut Threshold, r: SYS_TICK::Resources) {
     // ..
 
-    // this task can't be preempted by `tim2` so it has direct access to the
+    // This task can't be preempted by `tim2` so it has direct access to the
     // resource data
     **r.COUNTER += 1;
 
@@ -55,10 +55,10 @@ fn sys_tick(_t: &mut Threshold, r: SYS_TICK::Resources) {
 fn tim2(t: &mut Threshold, mut r: TIM2::Resources) {
     // ..
 
-    // as this task runs at lower priority it needs a critical section to
+    // As this task runs at lower priority it needs a critical section to
     // prevent `sys_tick` from preempting it while it modifies this resource
     // data. The critical section is required to prevent data races which can
-    // lead to data corruption or data loss
+    // lead to undefined behavior
     r.COUNTER.claim_mut(t, |counter, _t| { **counter += 1; });
 
     // ..