From: Marcin Siodelski Date: Fri, 24 Sep 2021 08:56:05 +0000 (+0000) Subject: [#2050] Apply 6 suggestion(s) to 2 file(s) X-Git-Tag: Kea-2.0.0~25 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ab0539c48df9357c38658f02b7ddfff4eea68048;p=thirdparty%2Fkea.git [#2050] Apply 6 suggestion(s) to 2 file(s) --- diff --git a/doc/examples/template-power-user-home/kea-dhcp4-1.conf b/doc/examples/template-power-user-home/kea-dhcp4-1.conf index 755e3d90c5..d5ba001ce6 100644 --- a/doc/examples/template-power-user-home/kea-dhcp4-1.conf +++ b/doc/examples/template-power-user-home/kea-dhcp4-1.conf @@ -85,7 +85,7 @@ // This parameter points to this server instance. The respective // HA peers must have this parameter set to their own names. "this-server-name": "server1", - // The HA mode is set to host-standby. In this mode, the active server handles + // The HA mode is set to hot-standby. In this mode, the active server handles // all the traffic. The standby takes over if the primary becomes unavailable. "mode": "hot-standby", // Heartbeat is to be sent every 10 seconds if no other control @@ -146,7 +146,7 @@ "subnet": "192.168.1.0/24", // There are no relays in this network, so we need to tell Kea that this subnet - // is reachable directly via the ethX interface. + // is reachable directly via the specified interface. "interface": "enp0s8", // Specify a dynamic address pool. @@ -160,7 +160,7 @@ // least routers option, as without this option your clients will not be able to reach // their default gateway and will not have Internet connectivity. If you have many // subnets and they share the same options (e.g. DNS servers typically is the same - // everywhere), you may define options in the global scope, so you don't repeat them + // everywhere), you may define options at the global scope, so you don't repeat them // for every network. "option-data": [ { diff --git a/doc/examples/template-power-user-home/kea-dhcp4-2.conf b/doc/examples/template-power-user-home/kea-dhcp4-2.conf index 6c7bcaadce..e9f3298721 100644 --- a/doc/examples/template-power-user-home/kea-dhcp4-2.conf +++ b/doc/examples/template-power-user-home/kea-dhcp4-2.conf @@ -1,4 +1,4 @@ -// This is an example configuration of the Kea DHCPv4 server 1: +// This is an example configuration of the Kea DHCPv4 server 2: // // - uses High Availability hooks library and Lease Commands hooks library // to enable High Availability function for the DHCP server. This config @@ -85,7 +85,7 @@ // This parameter points to this server instance. The respective // HA peers must have this parameter set to their own names. "this-server-name": "server2", - // The HA mode is set to host-standby. In this mode, the active server handles + // The HA mode is set to hot-standby. In this mode, the active server handles // all the traffic. The standby takes over if the primary becomes unavailable. "mode": "hot-standby", // Heartbeat is to be sent every 10 seconds if no other control @@ -160,7 +160,7 @@ // least routers option, as without this option your clients will not be able to reach // their default gateway and will not have Internet connectivity. If you have many // subnets and they share the same options (e.g. DNS servers typically is the same - // everywhere), you may define options in the global scope, so you don't repeat them + // everywhere), you may define options at the global scope, so you don't repeat them // for every network. "option-data": [ {