From 0bebcab624426847fd3933fbb0d01fdae71646e3 Mon Sep 17 00:00:00 2001 From: Jim Fitzpatrick Date: Thu, 30 Nov 2017 09:32:52 -0500 Subject: [PATCH] readme: Formatting --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 63cd7c0..1680006 100644 --- a/README.md +++ b/README.md @@ -56,8 +56,8 @@ An npm search brings up half a dozen retry libraries, if not more. [promise-retry](https://www.npmjs.com/package/promise-retry) has hundreds of thousands of downloads. Why not use one of those? Well, for me, I wanted something more lightweight. In my experience, the retry logic I typically add -is finite and well understood. Most often, it's retry up to three times, with -some form of linear or exponential backoff. This doesn't require any sort of +is finite and well understood. Most often, it's _retry up to three times, with +some form of linear or exponential backoff_. This doesn't require any sort of algorithms to work out how and when the retries should be invoked. With such a small number, it's trivial to figure out how long to wait and list out the delays manually. This concept is simple, but deceivingly capable, as you have