From: Thomas Markwalder <tmark@isc.org>
Date: Mon, 27 Nov 2017 15:12:23 +0000 (-0500)
Subject: [5416] Minor wordsmithing.
X-Git-Tag: trac5400_base~1^2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fd38dc84f3fe843e3c1584a5142f237dd4a1b55e;p=thirdparty%2Fkea.git

[5416] Minor wordsmithing.
---

diff --git a/src/lib/dhcpsrv/mysql_host_data_source.cc b/src/lib/dhcpsrv/mysql_host_data_source.cc
index b8709bf5d4..96a7fb12f9 100644
--- a/src/lib/dhcpsrv/mysql_host_data_source.cc
+++ b/src/lib/dhcpsrv/mysql_host_data_source.cc
@@ -87,14 +87,14 @@ const uint8_t MAX_IDENTIFIER_TYPE = static_cast<uint8_t>(Host::LAST_IDENTIFIER_T
 /// Database schema contains several unique indexes to guard against adding
 /// multiple hosts for the same client identifier in a single subnet and for
 /// adding multiple hosts with a reservation for the same IPv4 address in a
-/// single subnet. The exceptions that has to be taken into account are
+/// single subnet. The exceptions that have to be taken into account are
 /// listed below:
 /// - zero or null IPv4 address indicates that there is no reservation for the
 ///   IPv4 address for the host,
 /// - zero or null subnet identifier (either IPv4 or IPv6) indicates that
 ///   this subnet identifier must be ignored. Specifically, this is the case
-///   when host reservation is created DHCPv4 server, the IPv6 subnet id should
-///   be ignored. Conversely, when host reservation is created for DHCPv6 server,
+///   when host reservation is for the DHCPv4 server, the IPv6 subnet id should
+///   be ignored. Conversely, when host reservation is created for the DHCPv6 server,
 ///   the IPv4 subnet id should be ignored.
 ///
 /// To exclude those special case values from the unique indexes, the MySQL
diff --git a/src/lib/dhcpsrv/pgsql_host_data_source.cc b/src/lib/dhcpsrv/pgsql_host_data_source.cc
index beee96c06f..ead3b672ce 100644
--- a/src/lib/dhcpsrv/pgsql_host_data_source.cc
+++ b/src/lib/dhcpsrv/pgsql_host_data_source.cc
@@ -61,15 +61,15 @@ const size_t DHCP_IDENTIFIER_MAX_LEN = 128;
 /// Database schema contains several unique indexes to guard against adding
 /// multiple hosts for the same client identifier in a single subnet and for
 /// adding multiple hosts with a reservation for the same IPv4 address in a
-/// single subnet. The exceptions that has to be taken into account are
+/// single subnet. The exceptions that have to be taken into account are
 /// listed below:
 /// - zero or null IPv4 address indicates that there is no reservation for the
 ///   IPv4 address for the host,
 /// - zero or null subnet identifier (either IPv4 or IPv6) indicates that
 ///   this subnet identifier must be ignored. Specifically, this is the case
-///   when host reservation is created DHCPv4 server, the IPv6 subnet id should
-///   be ignored. Conversely, when host reservation is created for DHCPv6 server,
-///   the IPv4 subnet id should be ignored.
+///   when host reservation is created for the DHCPv4 server, the IPv6 subnet id
+///   should be ignored. Conversely, when host reservation is created for the
+///   DHCPv6 server, the IPv4 subnet id should be ignored.
 ///
 /// To exclude those special case values, the Postgres backend uses partial
 /// indexes, i.e. the only values that are included in the index are those that