From: Razvan Becheriu <razvan@isc.org>
Date: Thu, 5 Oct 2023 15:29:45 +0000 (+0300)
Subject: [#3046] fixed indentation and typos
X-Git-Tag: Kea-2.5.3~25
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=238690345fb49f6bbf102bbd5461ae8ecea9685b;p=thirdparty%2Fkea.git

[#3046] fixed indentation and typos
---

diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index 0ffbe78e18..4c051fbaea 100644
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -3462,8 +3462,8 @@ The default configuration and values would appear as follows:
 
    "Dhcp4": {
         "dhcp-ddns": {
-           // Connectivity parameters
-           "enable-updates": false,
+            // Connectivity parameters
+            "enable-updates": false,
             "server-ip": "127.0.0.1",
             "server-port":53001,
             "sender-ip":"",
@@ -3558,7 +3558,7 @@ offers four modes of conflict resolution-related behavior:
 
     For backward compatibility, ddns-use-conflict-resolution is still accepted in
     JSON configuration.  The server will replace the value internally, with the
-    ``ddns-conflict-resolution-mode`` and an appropriate vavlue: `
+    ``ddns-conflict-resolution-mode`` and an appropriate value: `
     `check-with-dhcid`` for ``true`` and ``no-check-with-dhcid`` for ``false``.
 
 .. note::
diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst
index 7804715d7a..1fd2bcf649 100644
--- a/doc/sphinx/arm/dhcp6-srv.rst
+++ b/doc/sphinx/arm/dhcp6-srv.rst
@@ -3055,8 +3055,8 @@ The default configuration and values would appear as follows:
 
    "Dhcp6": {
         "dhcp-ddns": {
-           // Connectivity parameters
-           "enable-updates": false,
+            // Connectivity parameters
+            "enable-updates": false,
             "server-ip": "127.0.0.1",
             "server-port":53001,
             "sender-ip":"",
@@ -3151,7 +3151,7 @@ offers four modes of conflict resolution-related behavior:
 
     For backward compatibility, ddns-use-conflict-resolution is still accepted in
     JSON configuration.  The server will replace the value internally, with the
-    ``ddns-conflict-resolution-mode`` and an appropriate vavlue: `
+    ``ddns-conflict-resolution-mode`` and an appropriate value: `
     `check-with-dhcid`` for ``true`` and ``no-check-with-dhcid`` for ``false``.
 
 .. note::