From c775c99db9867f9d1e2a61383d3e4fd392340860 Mon Sep 17 00:00:00 2001 From: DL6ER Date: Sat, 16 Jun 2018 18:59:18 +0200 Subject: [PATCH] Review comments Signed-off-by: DL6ER --- docs/ftldns/blockingmode.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/ftldns/blockingmode.md b/docs/ftldns/blockingmode.md index c39b150..de6c68e 100644 --- a/docs/ftldns/blockingmode.md +++ b/docs/ftldns/blockingmode.md @@ -28,7 +28,6 @@ Following [RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture, ##### Disadvantage - Blocking page cannot be shown and whitelisting has to be performed from the dashboard or CLI -- Client's may try to resolve blocked domains more often when they think that `NXDOMAIN` cannot be the correct reply ## Pi-hole's IP (IPv6 NODATA) blocking @@ -91,6 +90,6 @@ Blocked queries will be answered with an empty response (no answer section) and ``` ##### Advantages & Disadvantages -Similar to `NULL` blocking, but experiments suggest that client's may try to resolve blocked domains more often compared to `NULL` blocking. +Similar to `NULL` blocking, but experiments suggest that clients may try to resolve blocked domains more often compared to `NULL` blocking. {!abbreviations.md!}