From a7868fc4ae49d6fbaf548b1039b4b25e9bddd72a Mon Sep 17 00:00:00 2001 From: zabdalimov Date: Fri, 21 Jun 2024 14:52:25 +0200 Subject: [PATCH] fix few typos in README.md PR-URL: https://github.com/isaacs/node-lru-cache/pull/337 Credit: @zabdalimov Close: #337 Reviewed-by: @isaacs --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9bfca74..c07f15e 100644 --- a/README.md +++ b/README.md @@ -131,7 +131,7 @@ will of course only have an effect on subsequent method calls. The maximum number of items that remain in the cache (assuming no TTL pruning or explicit deletions). Note that fewer items may be stored if size calculation is used, and `maxSize` is exceeded. -This must be a positive finite intger. +This must be a positive finite integer. At least one of `max`, `maxSize`, or `TTL` is required. This must be a positive integer if set. @@ -700,7 +700,7 @@ If you call `fetch()` multiple times with the same key value, then every call after the first will resolve on the same promise1, _even if they have different settings that would otherwise change -the behvavior of the fetch_, such as `noDeleteOnFetchRejection` +the behavior of the fetch_, such as `noDeleteOnFetchRejection` or `ignoreFetchAbort`. In most cases, this is not a problem (in fact, only fetching @@ -1066,7 +1066,7 @@ This cache never stores undefined values, as `undefined` is used internally in a few places to indicate that a key is not in the cache. -You may call `cache.set(key, undefined)`, but this is just an +You may call `cache.set(key, undefined)`, but this is just an alias for `cache.delete(key)`. Note that this has the effect that `cache.has(key)` will return _false_ after setting it to undefined.