conf: rename server.dnssec-keydir to server.kasp-db

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/migration.rst b/doc/migration.rst
index da0880575..47b6a04cf 100644
--- a/doc/migration.rst
+++ b/doc/migration.rst
@@ -23,21 +23,21 @@ generated by Bind.
    example.com``.
 
    Note: If dynamic updates (DDNS) are enabled for the given zone, you
-   might need to freeze the zone before flushing it.  That can be done
+   might need to freeze the zone before flushing it. That can be done
    similarly: ``rndc freeze example.com``
 
 2. Copy the fresh zone file into the zones storage directory of Knot
-   DNS.  It's default location is ``/var/lib/knot``.
+   DNS. It's default location is ``/var/lib/knot``.
 
 3. We recommend to store DNSSEC keys for each zone in a separate
-   directory.  For this purpose, create a directory
-   ``example.com.keys`` in zones storage directory.  Then copy all
+   directory. For this purpose, create a directory
+   ``example.com.keys`` in zones storage directory. Then copy all
    DNSSEC keys (``*.key`` and ``*.private``) from Bind key directory
    (configured as ``key-directory``) into the newly created one.
 
-4. Add the zone into the Knot DNS configuration file.  Zone
+4. Add the zone into the Knot DNS configuration file. Zone
    configuration should contain at least specification of the zone
-   file (option ``file``), key directory (option ``dnssec-keydir``),
+   file (option ``file``), key directory (option ``kasp-db``),
    and enable automatic DNSSEC signing (option ``dnssec-enable``).
 
    You can follow this example::
@@ -47,6 +47,6 @@ generated by Bind.
         file: "example.com.db"
         storage: "/var/lib/knot"
         dnssec-enable: on
-        dnssec-keydir: "example.com.keys"
+        kasp-db: "example.com.keys"
 
 5. Start Knot DNS and check the log files to make sure that everything went right.