docs: fix typos in upgrade info

diff --git a/docs/markdown/authoritative/upgrading.md b/docs/markdown/authoritative/upgrading.md
index db63fb65114e77403b1f309b0d6fecf8a28a7b92..37197855baf4399da7a7c46d45e071b067682347 100644 (file)
--- a/docs/markdown/authoritative/upgrading.md
+++ b/docs/markdown/authoritative/upgrading.md
@@ -54,8 +54,8 @@ The API path has changed to `/api/v1`.
 Incompatible change: `SOA-EDIT-API` now follows `SOA-EDIT-DNSUPDATE` instead of `SOA-EDIT` (incl. the fact that it now has a default value of `DEFAULT`).
 You must update your existing `SOA-EDIT-API` metadata (set `SOA-EDIT` to your previous `SOA-EDIT-API` value, and `SOA-EDIT-API` to `SOA-EDIT` to keep the old behaviour).
 
-## Ressource Record Changes
-Since PowerDNS 4.0.0 the CAA ressource record (type 257) is supported. In PowerDNS 3.4.x type 257 was used for a proprietary MBOXFW ressource record, which 
-was removed from PowerDNS 4.0. Hence, if you used CAA records with 3.4.x (stored in the DB with wrong type=MBOXFW but worked fined) and upgrade to 4.0,
+## Resource Record Changes
+Since PowerDNS 4.0.0 the CAA resource record (type 257) is supported. Before PowerDNS 4.0.0 type 257 was used for a proprietary MBOXFW resource record, which
+was removed from PowerDNS 4.0. Hence, if you used CAA records with 3.4.x (stored in the DB with wrong type=MBOXFW but worked fine) and upgrade to 4.0,
 PowerDNS will fail to parse this records and will throw an exception on all queries for a label with MBOXFW records. Thus, make sure to clean up the
 records in the DB.