From d3d650b2c7e8492c96d8a37d85620ff491178632 Mon Sep 17 00:00:00 2001 From: perlindgren Date: Tue, 21 Dec 2021 19:49:09 +0100 Subject: [PATCH] Update tips_monotonic_impl.md text polishing --- book/en/src/by-example/tips_monotonic_impl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/en/src/by-example/tips_monotonic_impl.md b/book/en/src/by-example/tips_monotonic_impl.md index 99e155d049..24df7712c5 100644 --- a/book/en/src/by-example/tips_monotonic_impl.md +++ b/book/en/src/by-example/tips_monotonic_impl.md @@ -9,7 +9,7 @@ Implementing time counting that supports large time spans is generally **difficu implementing time handling was a common problem. Moreover, the relation between time and timers used for scheduling was difficult to understand. -For RTIC 0.6 we have moved to assume the user has a time library, e.g. [`fugit`] or [`embedded_time`], +For RTIC 0.6 we instead assume the user has a time library, e.g. [`fugit`] or [`embedded_time`], as the basis for all time-based operations when implementing `Monotonic`. This makes it almost trivial to implement the `Monotonic` trait allowing the use of any timer in the system for scheduling.