[268-reservation-mode-is-not-global] Minor editorial updates in User's Guide.

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index 43b3e632f38cc2ec707c4ae52608a68a8cd10eeb..b848cb48f5e5c78ec2655366119e9d22b56dcf5f 100644 (file)
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -3797,7 +3797,7 @@ It is merely echoed by the server
 }</screen>
 
 <para>
- Options defined on host level have the highest priority. In other words,
+ Options defined at host level have the highest priority. In other words,
  if there are options defined with the same type on global, subnet, class and
  host level, the host specific values will be used.
 </para>
@@ -3975,8 +3975,8 @@ It is merely echoed by the server
       </simpara></listitem>
 
       </itemizedlist>
-      The parameter can be specified in global, subnet and shared network
-      level.
+      The parameter can be specified at global, subnet and shared network
+      levels.
       </para>
 
       <para>
@@ -4224,7 +4224,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
             // and it must be unique among all shared networks.
             "name": "my-secret-lair-level-1",
 
-            // Subnet selector can be specifed on the shared network level.
+            // Subnet selector can be specifed at the shared network level.
             // Subnets from this shared network will be selected for directly
             // connected clients sending requests to server's "eth0" interface.
             "interface": "eth0",
@@ -4344,12 +4344,12 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
     <para>It is possible to specify interface name in the shared network scope to
     tell the server that this specific shared network is reachable directly (not
     via relays) using local network interface. It is sufficient to specify
-    it once on the shared network level. As all subnets in a shared network are
+    it once at the shared network level. As all subnets in a shared network are
     expected to be used on the same physical link, it is a configuration error
     to attempt to define a shared network using subnets that are reachable over
     different interfaces. It is allowed to specify interface parameter on each
     subnet, although its value must be the same for each subnet. Thus it's
-    usually more convenient to specify it once on the shared network level.
+    usually more convenient to specify it once at the shared network level.
 <screen>
 "shared-networks": [
     {
@@ -4409,9 +4409,9 @@ for each subnet. Here's an example:
         ]
     }
 ]</screen>
-In this particular case the relay IP address specified on network level doesn't
+In this particular case the relay IP address specified at network level doesn't
 have much sense, as it is overridden in both subnets, but it was left there
-as an example of how one could be defined on network level. Note that the
+as an example of how one could be defined at network level. Note that the
 relay agent IP address typically belongs to the subnet it relays packets from,
 but this is not a strict requirement. Therefore Kea accepts any value here
 as long as it is valid IPv4 address.</para>
@@ -4607,7 +4607,7 @@ autogenerated IDs are not stable across configuration changes.</para>
 
       <para>
         It is possible to override default server identifier values by specifying
-        "dhcp-server-identifier" option. This option is only supported on the
+        "dhcp-server-identifier" option. This option is only supported at the
         global, shared network and subnet level. It must not be specified
         on client class and host reservation level.
       </para>
@@ -5284,7 +5284,7 @@ autogenerated IDs are not stable across configuration changes.</para>
         </para>
 
         <para>
-          User contexts can be specified on either global scope,
+          User contexts can be specified at either global scope,
           shared network, subnet, pool, client class, option data or
           definition level, and host reservation. One other useful
           usage is the ability to store comments or descriptions.

diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index 6f48b336fd578318e1d19c1cdd1df5415293e196..4a2eb19718cc22bdd677d3c1c4908ce16ed954d4 100644 (file)
--- a/doc/guide/dhcp6-srv.xml
+++ b/doc/guide/dhcp6-srv.xml
@@ -3456,7 +3456,7 @@ should include options from the isc option space:
 } ]</screen>
 
 <para>
- Options defined on host level have the highest priority. In other words,
+ Options defined at host level have the highest priority. In other words,
  if there are options defined with the same type on global, subnet, class and
  host level, the host specific values will be used.
 </para>
@@ -3603,8 +3603,8 @@ should include options from the isc option space:
       </simpara></listitem>
 
       </itemizedlist>
-      The parameter can be specified in global, subnet and shared network
-      level.
+      The parameter can be specified at global, subnet and shared network
+      levels.
       </para>
 
       <para>
@@ -3980,12 +3980,12 @@ If not specified, the default value is:
     <para>It is possible to specify interface name in the shared network scope to
     tell the server that this specific shared network is reachable directly (not
     via relays) using local network interface. It is sufficient to specify
-    it once in the shared network level. As all subnets in a shared network are
+    it once at the shared network level. As all subnets in a shared network are
     expected to be used on the same physical link, it is a configuration error
     to attempt to make a shared network out of subnets that are reachable over
     different interfaces. It is allowed to specify interface parameter on each
     subnet, although its value must be the same for each subnet. Thus it's
-    usually more convenient to specify it once on the shared network level.
+    usually more convenient to specify it once at the shared network level.
 <screen>
 "shared-networks": [
     {
@@ -4045,9 +4045,9 @@ for each subnet. Here's an example:
         ]
     }
 ]</screen>
-In this particular case the relay IP address specified on network level doesn't
+In this particular case the relay IP address specified at network level doesn't
 have much sense, as it is overridden in both subnets, but it was left there
-as an example of how one could be defined on network level. Note that the
+as an example of how one could be defined at network level. Note that the
 relay agent IP address typically belongs to the subnet it relays packets from,
 but this is not a strict requirement. Therefore Kea accepts any value here
 as long as it is valid IPv6 address.</para>
@@ -5349,7 +5349,7 @@ autogenerated IDs are not stable across configuration changes.
         </para>
 
         <para>
-          User contexts can be specified on either global scope,
+          User contexts can be specified at either global scope,
           shared network, subnet, pool, client class, option data or
           definition level, and host reservation. One other useful
           usage is the ability to store comments or descriptions.