[297-old-text-about-multiple-classes-guards] Updated doc about one class vs classes...

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index 7befc88735fb55d510b5c3f4b02339878c7372eb..1973f0a369e2f14be04bd4682a7336d18524431f 100644 (file)
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -4455,11 +4455,11 @@ as long as it is valid IPv4 address.</para>
       the clients when client classification is in use, to assure that the
       desired subnet is selected for a given client type.</para>
 
-      <para>If a subnet is associated with some classes, only the clients
-      belonging to any of these classes can use this subnet. If there are no
+      <para>If a subnet is associated with a class, only the clients
+      belonging to this class can use this subnet. If there are no
       classes specified for a subnet, any client connected to a given shared
       network can use this subnet. A common mistake is to assume that the
-      subnet including client classes is preferred over subnets without
+      subnet including a client class is preferred over subnets without
       client classes. Consider the following example:
 
 <screen>
@@ -4505,7 +4505,7 @@ as long as it is valid IPv4 address.</para>
       where cable modems should use one subnet and other devices should use
       another subnet within the same shared network. In this case it is required
       to apply classification on all subnets. The following example defines two
-      classes of devices. The subnet selection is  made based on option 93 values.
+      classes of devices. The subnet selection is made based on option 93 values.
 <screen>
 {
     "client-classes": [

diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index 968eee6006516d2f47b1952f74fd3fc762d574ad..33075797a8a41f157bd4fcea5b0af42e54fa6cc8 100644 (file)
--- a/doc/guide/dhcp6-srv.xml
+++ b/doc/guide/dhcp6-srv.xml
@@ -4093,11 +4093,11 @@ as long as it is valid IPv6 address.</para>
       the clients when client classification is in use, to assure that the
       desired subnet is selected for a given client type.</para>
 
-      <para>If a subnet is associated with some classes, only the clients
-      belonging to any of these classes can use this subnet. If there are no
+      <para>If a subnet is associated with a class, only the clients
+      belonging to this class can use this subnet. If there are no
       classes specified for a subnet, any client connected to a given shared
       network can use this subnet. A common mistake is to assume that the
-      subnet including client classes is preferred over subnets without
+      subnet including a client class is preferred over subnets without
       client classes. Consider the following example:
 
 <screen>