From 7ab0804a27a7b9dc86bd58eb3a5d18f04d7c3eff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Akseli=20Pal=C3=A9n?= <akseli.palen@gmail.com>
Date: Thu, 21 Jun 2018 14:18:29 +0300
Subject: [PATCH] Clarify reconnecting delay

Without clarification `delay` can mean two things: time to the next attempt (wrong) or time passed from the previous attempt (correct). The wrong interpretation is tempting because it makes easy to print "Trying to reconnect in {delay} ms."
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index ff15de9355b..04c653e44cb 100644
--- a/README.md
+++ b/README.md
@@ -180,7 +180,7 @@ emitted.
 
 `client` will emit `reconnecting` when trying to reconnect to the Redis server
 after losing the connection. Listeners are passed an object containing `delay`
-(in ms) and `attempt` (the attempt #) attributes.
+(in ms from the previous try) and `attempt` (the attempt #) attributes.
 
 ### "error"