From 2ff1de317ffbd2263c2e82ada0362d49ab7ded78 Mon Sep 17 00:00:00 2001
From: mich-elle-luna <153109578+mich-elle-luna@users.noreply.github.com>
Date: Mon, 2 Dec 2024 15:42:16 -0800
Subject: [PATCH] Update
 content/integrate/prometheus-with-redis-enterprise/observability.md

Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
---
 .../integrate/prometheus-with-redis-enterprise/observability.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/integrate/prometheus-with-redis-enterprise/observability.md b/content/integrate/prometheus-with-redis-enterprise/observability.md
index 65adb32f1..5f5059919 100644
--- a/content/integrate/prometheus-with-redis-enterprise/observability.md
+++ b/content/integrate/prometheus-with-redis-enterprise/observability.md
@@ -118,7 +118,7 @@ the hit ratio will increase.
 while the percent of used memory will remain below 100%.
 
 **When the working set cannot fit in memory**, the eviction policy will start to evict keys.
-The greater the rate of key eviction, the lower the cache hit ratio.
+It is important to choose a policy that generally evicts rarely-used keys to keep the cache hit ratio as high as possible.
 
 In both cases, keys will may be manually invalidated by the application or evicted through
 the uses of TTLs (time-to-live) and an eviction policy.