[#4489] Minor fixes

modified:   doc/sphinx/arm/dhcp4-srv.rst
modified:   doc/sphinx/arm/dhcp6-srv.rst

diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index 159e101d9992bf4c12895789426f56291f5268ac..dfb28718c28505702c450821d53d27b3af248094 100644 (file)
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -9205,10 +9205,15 @@ the lease will not be offered.
 
 .. note::
 
-    It is strongly recommended that when configuring subnets to use SFLQ allocation,
-    it be done in maintenance windows such that servers are not actively serving
-    clients for those subnets while the changes are made. This will avoid
-    inconsistencies in SFLQ data.
+    It is strongly recommended that when configuring subnets to use or stop
+    using SFLQ allocation, it be done in maintenance windows such that servers
+    are not actively serving clients for those subnets while the changes are made.
+    This will avoid inconsistencies in SFLQ data.
+    
+    SFLQ data is tracked in terms of pools where each pool has a start address
+    and an end address. Configuration changes that change the address range
+    of a pool or split into multiple new pools will trigger SFLQ data creation
+    for the new pools when the new configuration is applied.
 
 As mentioned before when a server restarts or is reconfigured, it will iterate
 over its subnets and initialize the configured allocator for that subnet's pools.
@@ -9232,7 +9237,7 @@ Allocator.
 .. note::
 
     Lease reclamation must be enabled with a low value for the
-    ``reclaim-timer-wait-time`` parameter, to ensure that the server frequently
+    ``reclaim-timer-wait-time`` parameter to ensure that the server frequently
     collects expired leases and makes them available for allocation via the
     SFLQ data. Expired leases are not considered free by the allocator until they are
     reclaimed by the server. See :ref:`lease-reclamation` for more details about the

diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst
index 4b2ebf70611756d0098ef5a48c5bb9c64e35feb2..d8c03d09d24991daeec3ccb245ad395812767d38 100644 (file)
--- a/doc/sphinx/arm/dhcp6-srv.rst
+++ b/doc/sphinx/arm/dhcp6-srv.rst
@@ -9027,6 +9027,11 @@ the lease will not be offered.
     clients for those subnets while the changes are made. This will avoid
     inconsistencies in SFLQ data.
 
+    SFLQ data is tracked in terms of pools where each pool has a start address
+    and an end address. Configuration changes that change the address range
+    of a pool or split into multiple new pools will trigger SFLQ data creation
+    for the new pools when the new configuration is applied.
+
 As mentioned before when a server restarts or is reconfigured, it will iterate
 over its subnets and initialize the configured allocator for that subnet's pools.
 For the SFLQ Allocator, this will cause the server to request the lease back end
@@ -9049,7 +9054,7 @@ Allocator.
 .. note::
 
     Lease reclamation must be enabled with a low value for the
-    ``reclaim-timer-wait-time`` parameter, to ensure that the server frequently
+    ``reclaim-timer-wait-time`` parameter to ensure that the server frequently
     collects expired leases and makes them available for allocation via the
     SFLQ data. Expired leases are not considered free by the allocator until they are
     reclaimed by the server. See :ref:`lease-reclamation` for more details about the