spelling: explicitly

diff --git a/docs/markdown/authoritative/settings.md b/docs/markdown/authoritative/settings.md
index 3f81c1834070f8012a5cb73d1596f4c91ed80d7c..69fc8686c9fa2fb28ac2b0c2f7a7353df8c7d67e 100644 (file)
--- a/docs/markdown/authoritative/settings.md
+++ b/docs/markdown/authoritative/settings.md
@@ -599,7 +599,7 @@ hostnames to check their IP addresses against the specfied whitelist. The resolv
 may take considerable time, especially if those hostnames are slow to resolve. If you
 do not need to NOTIFY the slaves defined in the NS records (e.g. you are using another
 method to distribute the zone data to the slaves), then set `only-notify` to an empty
-value and specify the notification targets explicitely using [`also-notify`](#also-notify)
+value and specify the notification targets explicitly using [`also-notify`](#also-notify)
 and/or `ALSO-NOTIFY` domain metadata to avoid this potential bottleneck.
 
 ## `out-of-zone-additional-processing`

diff --git a/pdns/README-dnsdist.md b/pdns/README-dnsdist.md
index 95442f4c3da9db3820bee9d29c40a891dea92ee8..cb69430e4f26d8bbe4ffb6b4a843045a55ed32f4 100644 (file)
--- a/pdns/README-dnsdist.md
+++ b/pdns/README-dnsdist.md
@@ -1127,7 +1127,7 @@ that can arise in this kind of setup:
    it might be confused by the fact that the source address will be the one from
    the `dnsdist` server.
 
-The first issue can be solved by routing SOA, AXFR and IXFR requests explicitely
+The first issue can be solved by routing SOA, AXFR and IXFR requests explicitly
 to the master:
 
 ```