[5416] Minor wordsmithing.

diff --git a/src/lib/dhcpsrv/mysql_host_data_source.cc b/src/lib/dhcpsrv/mysql_host_data_source.cc
index b8709bf5d420aad6b8ec9405eb596fd9042890e0..96a7fb12f9f16eb55c45c93fabe04576c2455e10 100644 (file)
--- 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 beee96c06f331f196c065e6cd1df03dabcae661d..ead3b672cef53b1be35e1129308672ccd035c10a 100644 (file)
--- 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