typo

diff --git a/docs/markdown/authoritative/backend-generic-sql.md b/docs/markdown/authoritative/backend-generic-sql.md
index 6bcc02e78bd1f3af1a81eb9a0d239022bf005086..f3037b21fe3376292614462a564448f2e7368572 100644 (file)
--- a/docs/markdown/authoritative/backend-generic-sql.md
+++ b/docs/markdown/authoritative/backend-generic-sql.md
@@ -104,7 +104,7 @@ serial set to `0` in the database. The serial in SOA responses is set to the
 highest value of the `change_date` field in the "records" table.
 
 
-# Handeling DNSSEC signed zones
+# Handling DNSSEC signed zones
 To enable DNSSEC processing, the `backend-dnssec` option must be set to 'yes'.
 
 ## Rules for filling out DNSSEC fields

diff --git a/docs/markdown/authoritative/dnssec.md b/docs/markdown/authoritative/dnssec.md
index c5841996091ea21101946a942b1661622d061db9..cc4c3f7c938f39a3eb9052cc7f0f3fbfedbc869d 100644 (file)
--- a/docs/markdown/authoritative/dnssec.md
+++ b/docs/markdown/authoritative/dnssec.md
@@ -294,7 +294,7 @@ changes in database schemas as shown in the [upgrade documentation](upgrading.md
 **Warning**: Once the relevant `backend-dnssec` switch has been set, stricter
 rules apply for filling out the database! The short version is: run
 `pdnsutil rectify-all-zones`, even those not secured with DNSSEC! For more
-information, see the [DNSSEC documentation for Generic SQL backends](backend-generic-sql.md#handeling-dnssec-signed-zones).
+information, see the [DNSSEC documentation for Generic SQL backends](backend-generic-sql.md#handling-dnssec-signed-zones).
 
 To deliver a correctly signed zone with the [DNSSEC defaults](#dnssec-defaults),
 invoke: