[5351] Updated the doc

doc/examples/kea4/advanced.json

@@ -101,12 +101,12 @@
     "match-client-id": true,
 
     // The following list defines subnets. Each subnet consists of at
-    // least subnet and pool entries. One extra feature that requires some
-    // explanation is user-context. This is a structure that you can define
-    // in subnets and pools. It is parsed by Kea, but not used directly.
-    // It is intended to keep anything you may want to put there - comments,
-    // extra designations, floor or department names etc. These structures
-    // will be made available to Kea hooks.
+    // least subnet and pool entries. One extra feature that requires
+    // some explanation is user-context. This is a structure that you can
+    // define in subnets, pools and others. It is parsed by Kea, but not
+    // used directly.  It is intended to keep anything you may want to
+    // put there - comments, extra designations, floor or department
+    // names etc. These structures will be made available to Kea hooks.
     // You can define multiple user-contexts in the same scope without
     // the last one replacing previous values. A comment entry is
     // translated into a user-context with a "comment" property so

doc/guide/dhcp4-srv.xml

@@ -4636,8 +4636,11 @@ autogenerated IDs are not stable across configuration changes.</para>
         </para>
 
         <para>
-          User contexts can be specified on either subnet or pool level. One
-          other useful usage is the ability to store comments or descriptions.
+          User contexts can be specified on either global scope,
+          shared network, subnet, pool, client class, option data or
+          definition level but not yet for a host reservation. One
+          other useful usage is the ability to store comments or
+          descriptions.
         </para>
 
         <para>

doc/guide/dhcp6-srv.xml

@@ -4597,8 +4597,11 @@ autogenerated IDs are not stable across configuration changes.
         </para>
 
         <para>
-          User contexts can be specified on either subnet or pool level. One
-          other useful usage is the ability to store comments or descriptions.
+          User contexts can be specified on either global scope,
+          shared network, subnet, pool, client class, option data or
+          definition level but not yet for a host reservation. One
+          other useful usage is the ability to store comments or
+          descriptions.
         </para>
 
         <para>

doc/guide/hooks.xml

@@ -2566,10 +2566,13 @@ both the command and the response.
         common usage.
       </para>
       <para>
-        As of Kea 1.3, the structures that allow user contexts are pools of all
-        types (addresses and prefixes) and subnets. These are supported in both
-        DHCPv4 and DHCPv6. It is expected that other structures will be extended
-        in the future to provide the user context capability.
+        As of Kea 1.3, the structures that allow user contexts are
+        pools of all types (addresses and prefixes) and subnets. Kea
+        1.4 extended to the global scope, shared-networks, client
+        classes, and option data and definitions. These are supported
+        in both DHCPv4 and DHCPv6. It is expected that host
+        reservations and other structures will be extended in the
+        future to provide the user context capability.
       </para>
     </section>