From 364325dca9f5f55c8cb35285a668eaacf528e0b6 Mon Sep 17 00:00:00 2001
From: Anastasiia Fedotova
 <92315747+anastasiia-fedotova@users.noreply.github.com>
Date: Thu, 21 Dec 2023 09:11:21 +0300
Subject: [PATCH] Update docs/private-dns/overview.md

Co-authored-by: Helen <58733007+el-termikael@users.noreply.github.com>
---
 docs/private-dns/overview.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/private-dns/overview.md b/docs/private-dns/overview.md
index a1cbca0d3..1cbb2e4a8 100644
--- a/docs/private-dns/overview.md
+++ b/docs/private-dns/overview.md
@@ -148,7 +148,12 @@ For cases where pre-installed blocklists with thousands of rules are not enough,
 
 ## Advanced
 
-Here you can set the way AdGuard DNS should respond to blocked domains: Default (zero IP address), NXDOMAIN (indicating the domain does not exist), REFUSED (the server has refused to process the query), and Custom IP (where you can specify an IP address manually).
+Here you can set the way AdGuard DNS must respond to blocked domains:
+
+- Default — zero IP address
+- NXDOMAIN — the domain does not exist
+- REFUSED — the server has refused to process the request
+- Custom IP — you can manually specify an IP address
 
 Additionally, you can adjust the Time-to-Live (TTL) setting. This parameter defines the time period (in seconds) that a client device caches the response to a DNS request. A higher TTL means that even if a previously blocked domain is unblocked, it may still appear as blocked for a certain period. A TTL of 0 indicates that the device will not cache responses.