From b6357cc32395f1ce9bb0173038f00887bc5b437c Mon Sep 17 00:00:00 2001 From: Arnout Engelen Date: Mon, 4 Aug 2014 20:45:30 +0200 Subject: [PATCH] Use highest/lowest instead of largest/smallest --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6c3a7037..365de5d1 100644 --- a/README.md +++ b/README.md @@ -400,7 +400,7 @@ Additionally, you can supply an options object as the first parameter to `create * `'values'` *(boolean, default: `true`)*: whether the `'data'` event should contain values. If set to `true` and `'keys'` set to `false` then `'data'` events will simply be values, rather than objects with a `'value'` property. Used internally by the `createValueStream()` method. -* `'limit'` *(number, default: `-1`)*: limit the number of results collected by this stream. This number represents a *maximum* number of results and may not be reached if you get to the end of the data first. A value of `-1` means there is no limit. When `reverse=true` the largest keys will be returned instead of the smallest keys. +* `'limit'` *(number, default: `-1`)*: limit the number of results collected by this stream. This number represents a *maximum* number of results and may not be reached if you get to the end of the data first. A value of `-1` means there is no limit. When `reverse=true` the highest keys will be returned instead of the lowest keys. * `'fillCache'` *(boolean, default: `false`)*: wheather LevelDB's LRU-cache should be filled with data read.