From b9c80fb805c4d6930a2442586684b0dc6674b5cb Mon Sep 17 00:00:00 2001 From: Wlodek Wencel Date: Wed, 27 Sep 2017 20:34:00 +0200 Subject: [PATCH] [master] fixing typos in documentation --- doc/guide/dhcp4-srv.xml | 6 +++--- doc/guide/dhcp6-srv.xml | 4 ++-- doc/guide/hooks.xml | 10 +++++----- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 2debe85c2a..a4c450c604 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -3468,7 +3468,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc --> subnet, it is easier to simply configure additional subnet on top of the existing one. Sometimes, due to address space fragmentation (e.g. only many disjoint /24s are available) this is the only choice. Also, configuring - additional subnet has the advantage of not distrupting the operation of + additional subnet has the advantage of not disrupting the operation of existing devices. Another very frequent use case comes from cable networks. There are two types @@ -3528,8 +3528,8 @@ src/lib/dhcpsrv/cfg_host_operations.cc --> consist of two or more subnets. However, for testing purposes it is allowed to define a shared network with just one subnet or even an empty one. This is not a recommended practice in production networks, as the shared network - logic requires additional processing and thus lowers server's performace. - To avoid unnecessary peformance degradation the shared subnets should only + logic requires additional processing and thus lowers server's performance. + To avoid unnecessary performance degradation the shared subnets should only be defined when required by the deployment. diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index f9bc5bc68f..53f3b56968 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -3087,8 +3087,8 @@ If not specified, the default value is: consist of two or more subnets. However, for testing purposes it is allowed to define a shared network with just one subnet or even an empty one. This is not a recommended practice in production networks, as the shared network - logic requires additional processing and thus lowers server's performace. - To avoid unnecessary peformance degradation the shared subnets should only + logic requires additional processing and thus lowers server's performance. + To avoid unnecessary performance degradation the shared subnets should only be defined when required by the deployment. diff --git a/doc/guide/hooks.xml b/doc/guide/hooks.xml index 802e94af1d..bf2db722cf 100644 --- a/doc/guide/hooks.xml +++ b/doc/guide/hooks.xml @@ -1239,7 +1239,7 @@ An example deletion by (subnet-id, identifier-type, identifier) looks as follows lease6-add command requires four - paramaters: an IPv6 address, a subnet-id, and IAID value + parameters: an IPv6 address, a subnet-id, and IAID value (identity association identifier, a value sent by clients) and a DUID: @@ -1294,7 +1294,7 @@ The commands can take a number of additional optional parameters: not be conducted at the lease insertion time. If configured, a DNS update to remove the A or AAAA records will be conducted when the lease is removed due to expiration or being released by a - client. If not specifed, the default value is false. Hostname + client. If not specified, the default value is false. Hostname parameter must be specified in fqdn-fwd is set to true. @@ -1304,7 +1304,7 @@ The commands can take a number of additional optional parameters: not be conducted at the lease insertion time. If configured, a DNS update to remove the PTR record will be conducted when the lease is removed due to expiration or being released by a client. If not - specifed, the default value is false. Hostname parameter must be + specified, the default value is false. Hostname parameter must be specified in fqdn-fwd is set to true. @@ -1535,7 +1535,7 @@ as follows: leaseX-get, if needed. - An example command updating IPv6 lease looks as follows: + An example command updating IPv4 lease looks as follows: { "command": "lease4-update", "arguments": { @@ -1594,7 +1594,7 @@ as follows: number of leases removed and 0 (success) status code if any leases were removed and 2 (empty) if there were no leases. Status code 1 (error) may be returned in case the - parameeters are incorrect or some other exception is + parameters are incorrect or some other exception is encountered. Note: not all backends support this command. -- 2.47.2