mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-09-02 15:05:16 +00:00
Code Issues Releases Wiki Activity

[master] fixing typos in documentation

Browse Source
This commit is contained in:
Wlodek Wencel
2017-09-27 20:34:00 +02:00
parent 28b4f8aa44
commit b9c80fb805
3 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/guide/dhcp4-srv.xml
View File

@@ -3468,7 +3468,7 @@ src/lib/dhcpsrv/cfg_host_operations.cc -->
subnet, it is easier to simply configure additional subnet on top of the 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 existing one. Sometimes, due to address space fragmentation (e.g. only many
disjoint /24s are available) this is the only choice. Also, configuring 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.</para> existing devices.</para>
<para>Another very frequent use case comes from cable networks. There are two types <para>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 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 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 is not a recommended practice in production networks, as the shared network
logic requires additional processing and thus lowers server's performace. logic requires additional processing and thus lowers server's performance.
To avoid unnecessary peformance degradation the shared subnets should only To avoid unnecessary performance degradation the shared subnets should only
be defined when required by the deployment. be defined when required by the deployment.
</para> </para>

4
doc/guide/dhcp6-srv.xml
View File

@@ -3087,8 +3087,8 @@ If not specified, the default value is:
consist of two or more subnets. However, for testing purposes it is allowed 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 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 is not a recommended practice in production networks, as the shared network
logic requires additional processing and thus lowers server's performace. logic requires additional processing and thus lowers server's performance.
To avoid unnecessary peformance degradation the shared subnets should only To avoid unnecessary performance degradation the shared subnets should only
be defined when required by the deployment. be defined when required by the deployment.
</para> </para>

10
doc/guide/hooks.xml
View File

@@ -1239,7 +1239,7 @@ An example deletion by (subnet-id, identifier-type, identifier) looks as follows
</para> </para>
<para><command>lease6-add</command> command requires four <para><command>lease6-add</command> 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 (identity association identifier, a value sent by clients) and
a DUID: a DUID:
<screen> <screen>
@@ -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 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 update to remove the A or AAAA records will be conducted when the
lease is removed due to expiration or being released by a 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.</para> parameter must be specified in fqdn-fwd is set to true.</para>
</listitem> </listitem>
<listitem> <listitem>
@@ -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 not be conducted at the lease insertion time. If configured, a DNS
update to remove the PTR record will be conducted when the lease 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 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.</para> specified in fqdn-fwd is set to true.</para>
</listitem> </listitem>
<listitem> <listitem>
@@ -1535,7 +1535,7 @@ as follows:
<command>leaseX-get</command>, if needed.</para> <command>leaseX-get</command>, if needed.</para>
<para> <para>
An example command updating IPv6 lease looks as follows: An example command updating IPv4 lease looks as follows:
<screen>{ <screen>{
"command": "lease4-update", "command": "lease4-update",
"arguments": { "arguments": {
@@ -1594,7 +1594,7 @@ as follows:
number of leases removed and 0 (success) status code if any number of leases removed and 0 (success) status code if any
leases were removed and 2 (empty) if there were no leases were removed and 2 (empty) if there were no
leases. Status code 1 (error) may be returned in case the 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.</para> encountered.</para>
<para>Note: not all backends support this command.</para> <para>Note: not all backends support this command.</para>