From 17459b8f7d2a377a3a406c210cc0665d1ff3a4b0 Mon Sep 17 00:00:00 2001 From: Matt Kraai Date: Fri, 21 Dec 2018 12:52:57 -0800 Subject: [PATCH] Fix grammar --- book/src/by-example/timer-queue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/src/by-example/timer-queue.md b/book/src/by-example/timer-queue.md index f8066c2b17..2e3decddc8 100644 --- a/book/src/by-example/timer-queue.md +++ b/book/src/by-example/timer-queue.md @@ -69,7 +69,7 @@ jitter even though `schedule.foo` was invoked at the *end* of `foo`. Using For the tasks scheduled from `init` we have exact information about their `scheduled` time. For hardware tasks there's no `scheduled` time because these -tasks are asynchronous in nature. For hardware task the runtime provides a +tasks are asynchronous in nature. For hardware tasks the runtime provides a `start` time, which indicates the time at which the task handler started executing.