Skip to content

Commit 7113f97

Browse files
Improve clarity by changing "but" to "so" in sorted sets documentation (#541)
* Improve clarity by changing "but" to "so" in sorted sets documentation * Update content/develop/data-types/sorted-sets.md --------- Co-authored-by: David Dougherty <david.dougherty@redis.com>
1 parent 0e3feeb commit 7113f97

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/develop/data-types/sorted-sets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ birth year because actually *they are already sorted*.
6363
Implementation note: Sorted sets are implemented via a
6464
dual-ported data structure containing both a skip list and a hash table, so
6565
every time we add an element Redis performs an O(log(N)) operation. That's
66-
good, but when we ask for sorted elements Redis does not have to do any work at
66+
good, so when we ask for sorted elements, Redis does not have to do any work at
6767
all, it's already sorted. Note that the [`ZRANGE`]({{< relref "/commands/zrange" >}}) order is low to high, while the [`ZREVRANGE`]({{< relref "/commands/zrevrange" >}}) order is high to low:
6868

6969
{{< clients-example ss_tutorial zrange >}}

0 commit comments

Comments
 (0)