doc/user: misc nits

config-fallback: I forgot the config-serve-stale label in there,
now reported as duplicate.  I'm still getting reports of
> WARNING: undefined label: 'config-serve-stale' [ref.ref]
in 3 places (config-cache.rst:170, config-rfc7706.rst:9, rfc-list.rst:337)
but I have no idea why that happens.

diff --git a/doc/user/config-dnssec.rst b/doc/user/config-dnssec.rst
index c9f07739efd2cec149611aab38684fb093d4372f..88a5349f3b4f3a322006c9bb90378d7465a30517 100644 (file)
--- a/doc/user/config-dnssec.rst
+++ b/doc/user/config-dnssec.rst
@@ -73,7 +73,7 @@ Following :option:`dnssec <dnssec: <options>>` section allows to modify DNSSEC c
    .. option:: negative-trust-anchors: <list of domain names>
 
       When you use a domain name as an *negative trust anchor* (NTA), DNSSEC validation will be turned off at/below these names.
-      If you want to disable DNSSEC validation completely, set ``dnssec: false`` instead.
+      If you want to disable DNSSEC validation completely, set ``dnssec/enable: false`` instead (see above).
 
       .. code-block:: yaml
 

diff --git a/doc/user/config-fallback.rst b/doc/user/config-fallback.rst
index 7a45abb904003d80e966b595910490e238918815..0b8619e1bc0e0581d513dbe8a1a72701f291c33d 100644 (file)
--- a/doc/user/config-fallback.rst
+++ b/doc/user/config-fallback.rst
@@ -1,6 +1,6 @@
 .. SPDX-License-Identifier: GPL-3.0-or-later
 
-.. _config-serve-stale:
+.. _config-fallback:
 
 Fallback on resolution failure
 ==============================

diff --git a/doc/user/deployment-systemd.rst b/doc/user/deployment-systemd.rst
index fc52e98ac9262ab3d7d80bd21fedf6333928f8a3..5918fefc573178fe8dc501c77c65ded4642e58f7 100644 (file)
--- a/doc/user/deployment-systemd.rst
+++ b/doc/user/deployment-systemd.rst
@@ -13,8 +13,8 @@ If you don't have systemd service file for Knot Resolver already installed in yo
 
 
 .. literalinclude:: ../../systemd/knot-resolver.service.in
-    :language: bash
+    :language: systemd
 
 .. note::
 
-    Replace words surrounded by ``@`` to some real values (i.e. ``@user@`` to a user you want Knot Resolver to run as).
\ No newline at end of file
+    Replace words surrounded by ``@`` to some real values (i.e. ``@user@`` to a user you want Knot Resolver to run as).

diff --git a/doc/user/gettingstarted-config.rst b/doc/user/gettingstarted-config.rst
index 1968ee5ba9386eec00849693dbf0c1282c77ef44..a63e81ed63c1dcc24e103473e9425efc4a9a3659 100644 (file)
--- a/doc/user/gettingstarted-config.rst
+++ b/doc/user/gettingstarted-config.rst
@@ -36,6 +36,7 @@ If you update the configuration file while Knot Resolver is running, you can for
 
    **Reloading configuration** may fail, even when your configuration is valid, because some options cannot be changed while running.
    You can always find an explanation of the error in the log accesed by the ``journalctl -eu knot-resolver`` command.
+.. for these cases see: git grep '\<_deny_' python/
 
 ===============================
 Listening on network interfaces

diff --git a/python/knot_resolver/manager/server.py b/python/knot_resolver/manager/server.py
index 509f8996ac93abd03e3a49db9e0a8c6ecf476255..f2c0698772bac75e792ffaee023b252d135b9906 100644 (file)
--- a/python/knot_resolver/manager/server.py
+++ b/python/knot_resolver/manager/server.py
@@ -111,7 +111,7 @@ class Server:
     ) -> Result[None, str]:
         if config_old.management != config_new.management:
             return Result.err(
-                "/server/management: Changing management API address/uTruenix-socket dynamically is not allowed as it's really dangerous."
+                "/server/management: Changing management API address/unix-socket dynamically is not allowed as it's really dangerous."
                 " If you really need this feature, please contact the developers and explain why. Technically,"
                 " there are no problems in supporting it. We are only blocking the dynamic changes because"
                 " we think the consequences of leaving this footgun unprotected are worse than its usefulness."