From 4a828c6c0695936b9cf8f1078c42f517e07d0839 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Thu, 16 Jul 2020 18:12:24 -0700 Subject: [PATCH] doc: use correct identifier for callback argument MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In one place, the fs docs use `previousStat` for an argument that is identified as `previous` everywhere else. Use `previous` for consistency. PR-URL: https://github.com/nodejs/node/pull/34405 Reviewed-By: Juan José Arboleda Reviewed-By: Ruben Bridgewater Reviewed-By: Anna Henningsen Reviewed-By: James M Snell Reviewed-By: Luigi Pinca Reviewed-By: Tobias Nießen --- doc/api/fs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/api/fs.md b/doc/api/fs.md index b6e0004abff744..c31a7279f376d1 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -4099,9 +4099,9 @@ Using [`fs.watch()`][] is more efficient than `fs.watchFile` and `fs.unwatchFile` when possible. When a file being watched by `fs.watchFile()` disappears and reappears, -then the `previousStat` reported in the second callback event (the file's -reappearance) will be the same as the `previousStat` of the first callback -event (its disappearance). +then the contents of `previous` in the second callback event (the file's +reappearance) will be the same as the contents of `previous` in the first +callback event (its disappearance). This happens when: