diff --git a/docs/performance/hit-ratio.md b/docs/performance/hit-ratio.md
index 8409ef5..fe09078 100644
--- a/docs/performance/hit-ratio.md
+++ b/docs/performance/hit-ratio.md
@@ -46,6 +46,6 @@ This trace is described as "references to a CODASYL database for a one hour peri
 
 ### Conclusion
 
-`S3-FIFO` (otter) is inferior to `W-TinyLFU` (theine) on lfu friendly traces (databases, search, analytics), but has a greater or equal hit ratio on web traces.
+`S3-FIFO` (otter) is inferior to `W-TinyLFU` (theine) on lfu friendly traces (databases, search, analytics) and has a greater or equal hit ratio on web traces. But it is still worth recognizing that `W-TinyLFU` is superior to `S3-FIFO` as a general-purpose eviction policy.
 
 In summary, we have that `S3-FIFO` is competitive with `W-TinyLFU` and `ARC`. Also, it provides a substantial improvement to `LRU` across a variety of traces.
diff --git a/docs/performance/memory-consumption.md b/docs/performance/memory-consumption.md
index ed2697c..04a40d0 100644
--- a/docs/performance/memory-consumption.md
+++ b/docs/performance/memory-consumption.md
@@ -34,4 +34,4 @@ In this benchmark, the cache capacity is 1000000 elements.
 
 At small cache sizes, the buffers used in otter slightly worsen memory consumption, but as the cache size increases, the per entry overhead affects memory consumption much more, which is why otter starts to show great results.
 
-Also, ristretto's performance is questionable, as its per entry overhead is quite high. This is most likely caused by the bloom filter used in it, which rejects a lot of items in advance or it is another consequence of a bug that causes poor hit ratio.
+Also, ristretto's performance is questionable, as its per entry overhead is quite high. This is most likely caused by the bloom filter used in it, which rejects a lot of items in advance, or it is another consequence of a bug that causes poor hit ratio.