Apply suggestions from code review

Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>

Author: paulohtb6

modules/manage/partials/monitor-health.adoc

@@ -55,27 +55,27 @@ Use xref:reference:public-metrics-reference.adoc#redpanda_cpu_busy_seconds_total
 
 ==== Memory availability and pressure
 
-To monitor memory, use xref:reference:public-metrics-reference.adoc#redpanda_memory_available_memory[`redpanda_memory_available_memory`] which includes both free memory and reclaimable memory from the batch cache. This provides a more accurate picture than using allocated memory alone, since allocated does not include reclaimable cache memory.
+To monitor memory, use xref:reference:public-metrics-reference.adoc#redpanda_memory_available_memory[`redpanda_memory_available_memory`], which includes both free memory and reclaimable memory from the batch cache. This provides a more accurate picture than using allocated memory alone, since allocated does not include reclaimable cache memory.
 
 To monitor the percentage of memory available:
 
 [,promql]
 ----
-sum(redpanda_memory_available_memory) / (sum(redpanda_memory_free_memory) + sum(redpanda_memory_allocated_memory))
+min(redpanda_memory_available_memory / (redpanda_memory_free_memory + redpanda_memory_allocated_memory))
 ----
 
 To monitor memory pressure (percentage of memory being used), which may be more intuitive for alerting:
 
 [,promql]
 ----
-(1 - (sum(redpanda_memory_available_memory) / (sum(redpanda_memory_free_memory) + sum(redpanda_memory_allocated_memory))))*100
+min(redpanda_memory_available_memory / redpanda_memory_allocated_memory)
 ----
 
 You can also monitor the lowest available memory since process start to understand historical memory pressure:
 
 [,promql]
 ----
-redpanda_memory_available_memory_low_water_mark
+min(redpanda_memory_available_memory_low_water_mark / (redpanda_memory_free_memory + redpanda_memory_allocated_memory))
 ----
 
 ==== Disk used