From 3e98575aceeaaaaf66c3b87b0c539666af884411 Mon Sep 17 00:00:00 2001 From: Johannes Date: Fri, 17 Feb 2023 18:11:13 +0000 Subject: [PATCH] Fix README typos --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 268842a..52f9682 100644 --- a/README.md +++ b/README.md @@ -41,9 +41,9 @@ The scheduling methods on `TaskManager` are listed below. In all instances `cont to include in your task when processTask is called. - `scheduleTaskAt(time: PointInTime, context: any): Promise` where `time` is the time in either ms since the epoch or a JS Date object. -- `scheduleTaskIn(ms: number, context: any): Promise` where `ms` is the amount of ms for now the task should be scheduled. +- `scheduleTaskIn(ms: number, context: any): Promise` where `ms` is the number of ms from now that the task should be scheduled. - `scheduleEvery(ms: number, context: any): Promise` where `ms` is the interval in milliseconds that the task should be scheduled. -- `cancelTask(taskId: taskId): Promise` where taskId is the id that is returned by any of the scheduling functions. +- `cancelTask(taskId: taskId): Promise` where `taskId` is the id that is returned by any of the scheduling functions. In practice the exact timing that your function will be called will depend on many factors and may not be as precise, especially for times within 30 seconds from the time of scheduling.