From d4346b3be25c1f24fb3e126f42ab54cbdadef8ab Mon Sep 17 00:00:00 2001
From: Ilya Mashchenko <ilya@netdata.cloud>
Date: Wed, 19 Jun 2024 14:53:02 +0300
Subject: [PATCH] docs: clarify setting time/disk limits to 0 (#17958)

---
 .../optimizing-metrics-database/change-metrics-storage.md   | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md b/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md
index 5fccf5340b..8d940a7305 100644
--- a/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md
+++ b/docs/netdata-agent/configuration/optimizing-metrics-database/change-metrics-storage.md
@@ -15,9 +15,11 @@ With these defaults, Netdata requires approximately 4 GiB of storage space (incl
 
 ## Retention Settings
 
-> **In a parent-child setup**, these settings manage the shared storage space utilized by the Netdata parent agent for storing metrics collected by both the parent and its child nodes.
+> **In a parent-child setup**, these settings manage the shared storage space utilized by the Netdata parent agent for
+> storing metrics collected by both the parent and its child nodes.
 
-You can fine-tune retention for each tier by setting either the time limit or size limit to zero. This enables various
+You can fine-tune retention for each tier by setting a time limit or size limit. Setting a limit to 0 disables it,
+allowing for no time-based deletion for that tier or using all available space, respectively. This enables various
 retention strategies as shown in the table below:
 
 | Setting                        | Retention Behavior                                                                                                                        |