Apply 1 suggestion(s) to 1 file(s)

diff --git a/doc/sphinx/arm/config.rst b/doc/sphinx/arm/config.rst
index 036e239492d340245db0d2282fb6269f53f59a5e..5f7d481788f329684a0b788b003da179df76f4c3 100644 (file)
--- 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