aboutsummaryrefslogtreecommitdiff
path: root/book/en/src/by-example/tips_monotonic_impl.md
diff options
context:
space:
mode:
Diffstat (limited to 'book/en/src/by-example/tips_monotonic_impl.md')
-rw-r--r--book/en/src/by-example/tips_monotonic_impl.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/book/en/src/by-example/tips_monotonic_impl.md b/book/en/src/by-example/tips_monotonic_impl.md
index d97b583..7c3449b 100644
--- a/book/en/src/by-example/tips_monotonic_impl.md
+++ b/book/en/src/by-example/tips_monotonic_impl.md
@@ -11,7 +11,7 @@ Moreover, the relation between time and timers used for scheduling was difficult
For RTIC 1.0 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 much easier to correctly implement the `Monotonic` trait allowing the use of
+These libraries make it much easier to correctly implement the `Monotonic` trait, allowing the use of
almost any timer in the system for scheduling.
The trait documents the requirements for each method,