From 69201fc234562c5aa2a8f5895ddfff2417126419 Mon Sep 17 00:00:00 2001
From: Blaine Bublitz <blaine.bublitz@gmail.com>
Date: Fri, 5 Apr 2019 22:02:12 -0400
Subject: [PATCH] Docs: Change the param timeResolution to precision (closes
 #84)

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 6505a33..93cf69d 100644
--- a/README.md
+++ b/README.md
@@ -122,7 +122,7 @@ Type: `Boolean`
 
 Default: `false`
 
-### `lastRun(task, [timeResolution])`
+### `lastRun(task, [precision])`
 
 Takes a string or function (`task`) and returns a timestamp of the last time the task
 was run successfully. The time will be the time the task started.
@@ -133,7 +133,7 @@ If a task errors, the result of `lastRun` will be undefined because the task
 should probably be re-run from scratch to get into a good state again.
 
 The timestamp is always given in millisecond but the time resolution can be
-rounded using the `timeResolution` parameter. The use case is to be able to compare a build time
+rounded using the `precision` parameter. The use case is to be able to compare a build time
 to a file time attribute. On node v0.10 or with file system like HFS or FAT,
 `fs.stat` time attributes like `mtime` precision is one second.