From: Suzanne Goldlust Date: Wed, 1 Jun 2022 21:07:52 +0000 (+0000) Subject: Apply 1 suggestion(s) to 1 file(s) X-Git-Tag: Kea-2.1.7~157 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=215f9acaa16331c7baf05b39f275ba34c5023f93;p=thirdparty%2Fkea.git Apply 1 suggestion(s) to 1 file(s) --- diff --git a/doc/sphinx/arm/config.rst b/doc/sphinx/arm/config.rst index 036e239492..5f7d481788 100644 --- a/doc/sphinx/arm/config.rst +++ b/doc/sphinx/arm/config.rst @@ -186,13 +186,13 @@ use user-context. Kea supports user contexts at the following levels: global scope, interfaces configuration, shared networks, subnets, client classes, option data and definitions, host -reservations, control socket, DHCP-DDNS, loggers, leases and server ID. These +reservations, control socket, DHCP-DDNS, loggers, leases, and server ID. These are supported in both DHCPv4 and DHCPv6, with the exception of server ID, which is DHCPv6 only. -User context can be added and edited easily in structures suported by API commands. +User context can be added and edited easily in structures supported by API commands. -We encourage Kea users to utilize this functions to store information +We encourage Kea users to utilize these functions to store information used by other systems and custom hooks. For example, the `subnet4-update` command can be used to add user context data