isc-projects · lyqfjcs · Oct 23, 2025
diff --git a/src/bin/agent/ca_messages.mes b/src/bin/agent/ca_messages.mes
@@ -45,7 +45,7 @@ encounters an unrecoverable error from within the event loop.
 
 % CTRL_AGENT_HTTPS_SERVICE_REUSE_FAILED failed to reuse HTTPS service bound to address: %1 port: %2
 This error message indicates that the server has failed reusing existing
-HTTPS service on the specified address and port. The server can not swith from
+HTTPS service on the specified address and port. The server can not switch from
 HTTPS to HTTP sockets using the same address and port.
 
 % CTRL_AGENT_HTTPS_SERVICE_STARTED HTTPS service bound to address: %1 port: %2
@@ -58,9 +58,9 @@ This informational message indicates that the server has reused existing
 HTTPS service on the specified address and port. Note that any change in
 the TLS setup has been applied.
 
-% CTRL_AGENT_HTTP_SERVICE_REUSE_FAILED failed to reused HTTP service bound to address: %1 port: %2
+% CTRL_AGENT_HTTP_SERVICE_REUSE_FAILED failed to reuse HTTP service bound to address: %1 port: %2
 This error message indicates that the server has failed reusing existing
-HTTP service on the specified address and port. The server can not swith from
+HTTP service on the specified address and port. The server can not switch from
 HTTP to HTTPS sockets using the same address and port.
 
 % CTRL_AGENT_HTTP_SERVICE_STARTED HTTP service bound to address: %1 port: %2
@@ -74,7 +74,7 @@ HTTP service on the specified address and port.
 
 % CTRL_AGENT_IS_DEPRECATED Kea Control Agent is deprecated. Its function has been moved to Kea servers.
 This warning message indicates that the Control Agent has been deprecated.
-All its function has been moved to Kea servers.
+All its functions have been moved to Kea servers.
 
 % CTRL_AGENT_RUN_EXIT application is exiting the event loop
 Logged at debug log level 0.

diff --git a/src/bin/dhcp4/dhcp4_messages.mes b/src/bin/dhcp4/dhcp4_messages.mes
@@ -509,7 +509,7 @@ This debug message is printed when a callout installed on the pkt4_receive
 hook point sets the next step to SKIP. For this particular hook point, the
 value setting of the flag instructs the server to drop the packet.
 
-% DHCP4_HOOK_PACKET_SEND_DROP %1: prepared DHCPv4 response was not sent because a callout set the next ste to DROP
+% DHCP4_HOOK_PACKET_SEND_DROP %1: prepared DHCPv4 response was not sent because a callout set the next step to DROP
 Logged at debug log level 15.
 This debug message is printed when a callout installed on the pkt4_send
 hook point set the next step to DROP. For this particular hook point, the setting
@@ -519,7 +519,7 @@ the server processed client's request and acted on it (e.g. possibly
 allocated a lease). The argument specifies the client and transaction
 identification information.
 
-% DHCP4_HOOK_PACKET_SEND_SKIP %1: prepared response is not sent, because a callout set the next stp to SKIP
+% DHCP4_HOOK_PACKET_SEND_SKIP %1: prepared response is not sent, because a callout set the next step to SKIP
 Logged at debug log level 40.
 This debug message is printed when a callout installed on the pkt4_send
 hook point sets the next step to SKIP. For this particular hook point, this
@@ -789,7 +789,7 @@ requested-ip-address option (if present).
 Logged at debug log level 50.
 A debug message issued when an option failed to unpack correctly, making it
 impossible to unpack the remaining options in the packet.  The server will
-server will still attempt to service the packet.
+still attempt to service the packet.
 
 % DHCP4_PACKET_PACK %1: preparing on-wire format of the packet to be sent
 Logged at debug log level 50.
@@ -1174,7 +1174,7 @@ and will send DHCPNAK if the received message was DHCPREQUEST.
 The argument includes the client and the transaction identification
 information.
 
-% DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED All packets will be send to source address of an incoming packet - use only for testing
+% DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED All packets will be sent to source address of an incoming packet - use only for testing
 This message is printed then KEA_TEST_SEND_RESPONSES_TO_SOURCE
 environment variable is set. It's causing Kea to send packets to
 source address of incoming packet. Usable just in testing environment

diff --git a/src/bin/dhcp6/dhcp6_messages.mes b/src/bin/dhcp6/dhcp6_messages.mes
@@ -424,7 +424,7 @@ This debug message is printed when a callout installed on buffer6_send
 hook point set the next step to SKIP value. For this particular hook point, the
 SKIP setting a callout instructs the server to drop the packet.
 Server completed all the processing (e.g. may have assigned, updated
-or released leases), but the response will not be send to the client.
+or released leases), but the response will not be sent to the client.
 The argument includes the client and transaction identification
 information.
 
@@ -467,7 +467,7 @@ This debug message is printed when a callout installed on lease6_release
 hook point set the next step to SKIP value. For this particular hook point, that
 setting by a callout instructs the server to not release
 a lease. If client requested release of multiples leases (by sending
-multiple IA options), the server will retains this particular lease and
+multiple IA options), the server will retain this particular lease and
 will proceed with other renewals as usual. The argument holds the
 client and transaction identification information.
 
@@ -496,7 +496,7 @@ This debug message is printed when a callout installed on the pkt6_receive
 hook point sets the next step to SKIP. For this particular hook point, the
 value setting instructs the server to drop the packet.
 
-% DHCP6_HOOK_PACKET_SEND_DROP %1: prepared DHCPv6 response was not sent because a callout set the next ste to DROP
+% DHCP6_HOOK_PACKET_SEND_DROP %1: prepared DHCPv6 response was not sent because a callout set the next step to DROP
 Logged at debug log level 15.
 This debug message is printed when a callout installed on the pkt6_send
 hook point set the next step to DROP. For this particular hook point, the setting

diff --git a/src/hooks/d2/gss_tsig/gss_tsig_messages.mes b/src/hooks/d2/gss_tsig/gss_tsig_messages.mes
@@ -49,7 +49,7 @@ created a new GSS-TSIG key. The name of the new key is displayed.
 This warning message is issued when the setup of a new GSS-TSIG key failed.
 The name of the new key and the error are displayed.
 
-% GSS_TSIG_NEW_KEY_SETUP_SUCCEED new GSS-TSIG key '%1' setup succeed.
+% GSS_TSIG_NEW_KEY_SETUP_SUCCEED new GSS-TSIG key '%1' setup succeeded.
 Logged at debug log level 40.
 This debug message is issued when the setup of a new GSS-TSIG key
 successfully finished. The name of the new key is displayed.
@@ -63,7 +63,7 @@ TKEY lifetime) were removed. The number of removed keys is displayed.
 This info message indicates that the GSS-TSIG hooks library has
 been unloaded successfully.
 
-% GSS_TSIG_VERIFIED GSS-TSIG verify successed.
+% GSS_TSIG_VERIFIED GSS-TSIG verify succeeded.
 Logged at debug log level 40.
 A debug message issued when GSS-TSIG verification succeeded.
 
@@ -160,7 +160,7 @@ is null.
 
 % TKEY_EXCHANGE_FAIL_RESPONSE_ERROR GSS-TKEY exchange failed because the response contains an error: %1.
 This error message indicated that GSS-TKEY exchange failed because the response
-contains an error. The argument details the reponse error.
+contains an error. The argument details the response error.
 
 % TKEY_EXCHANGE_FAIL_TKEY_ERROR GSS-TKEY exchange failed because the response contains TKEY error: %1.
 This error message indicated that GSS-TKEY exchange failed because the response

diff --git a/src/hooks/dhcp/high_availability/ha_messages.mes b/src/hooks/dhcp/high_availability/ha_messages.mes
@@ -93,7 +93,7 @@ such clients and if the number of such clients exceeds the max-unacked-clients
 threshold, the server will transition to the partner-down state. The first
 argument specifies the relationship name. The second argument contains client
 identification information. The third argument specifies the number of
-clients to which the server has failed to respond. The forth argument specifies
+clients to which the server has failed to respond. The fourth argument specifies
 the number of additional clients which, if not provisioned, will cause the
 server to transition to the partner-down state.
 
@@ -113,7 +113,7 @@ such clients and if the number of such clients exceeds the max-unacked-clients
 threshold, the server will transition to the partner-down state. The first
 argument specifies the relationship name. The second argument contains client
 identification information. The third argument specifies the number of clients
-to which the server has failed to respond. The forth argument specifies the
+to which the server has failed to respond. The fourth argument specifies the
 number of additional clients which, if not provisioned, will cause the server
 to transition to the partner-down state.
 
@@ -685,7 +685,7 @@ The argument contains a reason for the error.
 % HA_SUBNET4_SELECT_INVALID_HA_SERVER_NAME %1: invalid ha-server-name value for subnet %2
 This error message is issued when the received DHCPv4 query is dropped
 by this server because the specified ha-server-name value in the subnet's
-user-context has non-string type or is empty. It is a server's misconifguration.
+user-context has non-string type or is empty. It is a server's misconfiguration.
 The first argument is the client identification information. The second argument
 is a subnet prefix.
 
@@ -732,7 +732,7 @@ The argument contains a reason for the error.
 % HA_SUBNET6_SELECT_INVALID_HA_SERVER_NAME %1: invalid ha-server-name value for subnet %2
 This error message is issued when the received DHCPv6 query is dropped
 by this server because the specified ha-server-name value in the subnet's
-user-context has non-string type or is empty. It is a server's misconifguration.
+user-context has non-string type or is empty. It is a server's misconfiguration.
 The first argument is the client identification information. The second argument
 is a subnet prefix.
 

diff --git a/src/hooks/dhcp/mysql/mysql_fb_messages.mes b/src/hooks/dhcp/mysql/mysql_fb_messages.mes
@@ -48,7 +48,7 @@ This error message is issued when TLS for the connection was required but
 TLS is not used.
 
 % LEGAL_LOG_MYSQL_ROLLBACK rolling back MySQL database
-The code has issued a rollback call.  All outstanding transaction will
+The code has issued a rollback call.  All outstanding transactions will
 be rolled back and not committed to the database.
 
 % LEGAL_LOG_MYSQL_START_TRANSACTION starting new MySQL transaction

diff --git a/src/hooks/dhcp/pgsql/pgsql_fb_messages.mes b/src/hooks/dhcp/pgsql/pgsql_fb_messages.mes
@@ -25,7 +25,7 @@ is typically a network or database server issue.
 
 % LEGAL_LOG_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL log database: %1
 This is an error message issued when a legal log hook library experienced
-and error freeing database SQL resources as part of closing its connection to
+an error freeing database SQL resources as part of closing its connection to
 the PostgreSQL database.  The connection is closed as part of normal server
 shutdown.  This error is most likely a programmatic issue that is highly
 unlikely to occur or negatively impact server operation.
@@ -51,7 +51,7 @@ should be of the form 'keyword=value keyword=value...' is included in
 the message.
 
 % LEGAL_LOG_PGSQL_ROLLBACK rolling back PostgreSQL database
-The code has issued a rollback call.  All outstanding transaction will
+The code has issued a rollback call.  All outstanding transactions will
 be rolled back and not committed to the database.
 
 % LEGAL_LOG_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction

diff --git a/src/hooks/dhcp/pgsql/pgsql_lb_messages.mes b/src/hooks/dhcp/pgsql/pgsql_lb_messages.mes
@@ -234,7 +234,7 @@ This message is issued only once.
 
 % PGSQL_LB_ROLLBACK rolling back PostgreSQL database
 Logged at debug log level 50.
-The code has issued a rollback call. All outstanding transaction will
+The code has issued a rollback call. All outstanding transactions will
 be rolled back and not committed to the database.
 
 % PGSQL_LB_UPDATE_ADDR4 updating IPv4 lease for address %1

diff --git a/src/hooks/dhcp/radius/radius_messages.mes b/src/hooks/dhcp/radius/radius_messages.mes
@@ -353,7 +353,7 @@ attributes, so there can be multiple log messages per RADIUS message.
 It displays the message identifier, the exchange identifier and the
 value of the Reply-Message attribute.
 
-% RADIUS_RESUME_FAILED Resuming ithe RADIUS thread pool failed: %1
+% RADIUS_RESUME_FAILED Resuming the RADIUS thread pool failed: %1
 This error message is emitted when an unexpected error occurred while attempting
 to resume the thread pool. This error is highly unlikely and indicates a
 programmatic issue that should be reported as defect.
@@ -398,5 +398,5 @@ of stored records before the failure and the expected number of records
 are displayed.
 
 % RADIUS_THREAD_POOL_STARTED RADIUS thread pool started with %1 threads.
-This informational message is issued when the thread pool is starrted.
+This informational message is issued when the thread pool is started.
 The number of threads is displayed.
diff --git a/src/lib/config/config_messages.mes b/src/lib/config/config_messages.mes
@@ -50,7 +50,7 @@ at the given address and port, has begun to shutdown.
 
 % COMMAND_HTTP_SOCKET_SECURITY_WARNING command socket configuration is NOT SECURE: %1
 This warning message is issued when security enforcement is disabled
-and command socket configuration does not use HTTPS/TLS or  baseic HTTP
+and command socket configuration does not use HTTPS/TLS or  basic HTTP
 authentication. The server will still use the socket as configured but
 is warning that doing so may pose a security risk.
 

diff --git a/src/lib/d2srv/d2_messages.mes b/src/lib/d2srv/d2_messages.mes
@@ -237,7 +237,7 @@ configuration needs to be updated or the source of the FQDN itself should be
 investigated.
 
 % DHCP_DDNS_QUEUE_MGR_QUEUE_FULL application request queue has reached maximum number of entries %1
-This an error message indicating that DHCP-DDNS is receiving DNS update
+This is an error message indicating that DHCP-DDNS is receiving DNS update
 requests faster than they can be processed.  This may mean the maximum queue
 needs to be increased, the DHCP-DDNS clients are simply generating too many
 requests too quickly, or perhaps upstream DNS servers are experiencing
@@ -404,12 +404,12 @@ server or others as appropriate.
 Logged at debug log level 55.
 This is a debug message issued when reverse DNS updates are disabled and
 DHCP_DDNS receives an update request containing a reverse DNS update.  The
-reverse update will not performed.
+reverse update will not be performed.
 
 % DHCP_DDNS_RUN_EXIT application is exiting the event loop
 Logged at debug log level 0.
 This is a debug message issued when the DHCP-DDNS server exits its
-event lo
+event loop
 
 % DHCP_DDNS_SECURITY_CHECKS_DISABLED Invoked with command line option -X, Security checks are disabled!!
 This warning is emitted when internal security checks normally

diff --git a/src/lib/database/db_messages.mes b/src/lib/database/db_messages.mes
@@ -33,7 +33,7 @@ This is logged before running the kea-admin command to automatically initialize
 after getting the schema version initially failed. The full kea-admin command is shown.
 
 % DATABASE_MYSQL_ROLLBACK rolling back MySQL database
-The code has issued a rollback call.  All outstanding transaction will
+The code has issued a rollback call.  All outstanding transactions will
 be rolled back and not committed to the database.
 
 % DATABASE_MYSQL_START_TRANSACTION starting new MySQL transaction
@@ -75,7 +75,7 @@ This is logged before running the kea-admin command to automatically initialize
 after getting the schema version initially failed. The full kea-admin command is shown.
 
 % DATABASE_PGSQL_ROLLBACK rolling back PostgreSQL database
-The code has issued a rollback call.  All outstanding transaction will
+The code has issued a rollback call.  All outstanding transactions will
 be rolled back and not committed to the database.
 
 % DATABASE_PGSQL_ROLLBACK_SAVEPOINT rolling back PostgreSQL database to savepoint: $1

diff --git a/src/lib/dhcpsrv/alloc_engine_messages.mes b/src/lib/dhcpsrv/alloc_engine_messages.mes
@@ -53,7 +53,7 @@ and the client's packet belongs to one or more classes. There may be several
 reasons why a lease was not assigned. One of them may be a case when all
 pools require packet to belong to certain classes and the incoming packet
 didn't belong to any of them. Another case where this information may be
-useful is to point out that the pool reserved to a given class has ran
+useful is to point out that the pool reserved to a given class has run
 out of addresses. When you see this message, you may consider checking your
 pool size and your classification definitions.
 
@@ -335,7 +335,7 @@ and the client's packet belongs to one or more classes. There may be several
 reasons why a lease was not assigned. One of them may be a case when all
 pools require packet to belong to certain classes and the incoming packet
 didn't belong to any of them. Another case where this information may be
-useful is to point out that the pool reserved to a given class has ran
+useful is to point out that the pool reserved to a given class has run
 out of addresses. When you see this message, you may consider checking your
 pool size and your classification definitions.
 
@@ -410,7 +410,7 @@ and returned.
 
 % ALLOC_ENGINE_V6_ALLOC_LEASES_NO_HR no reservations found but leases exist for client %1
 Logged at debug log level 40.
-This message is logged when the allocation engine is in the process if
+This message is logged when the allocation engine is in the process of
 allocating leases for the client, there are no static reservations,
 but lease(s) exist for the client. The allocation engine will remove
 leases which are reserved for other clients, and return all

diff --git a/src/lib/dhcpsrv/dhcpsrv_messages.mes b/src/lib/dhcpsrv/dhcpsrv_messages.mes
@@ -957,7 +957,7 @@ selection.
 
 % DHCPSRV_SUBNET4_SELECT_NO_USABLE_ADDRESS No subnet selected because no suitable address to use for subnet selection was found.
 Logged at debug log level 40.
-A debug message issued when the server was find a suitable address to use for
+A debug message issued when the server could not find a suitable address to use for
 subnet selection.
 
 % DHCPSRV_SUBNET6_SELECT_BY_ADDRESS_NO_MATCH No subnet matches address: %1

diff --git a/src/lib/eval/eval_messages.mes b/src/lib/eval/eval_messages.mes
@@ -11,7 +11,7 @@ $NAMESPACE isc::dhcp
 % EVAL_DEBUG_AND %1: Popping %2 and %3 pushing %4
 Logged at debug log level 55.
 This debug message indicates that two values are popped from
-the value stack.  Then are then combined via logical and and
+the value stack.  They are then combined via logical and and
 the result is pushed onto the value stack.
 
 # For use with TokenBranch
@@ -145,7 +145,7 @@ option or a sub-option as requested in the classification statement.
 % EVAL_DEBUG_OR %1: Popping %2 and %3 pushing %4
 Logged at debug log level 55.
 This debug message indicates that two values are popped from
-the value stack.  Then are then combined via logical or and
+the value stack.  They are then combined via logical or and
 the result is pushed onto the value stack. The string is displayed
 in text.
 

diff --git a/src/lib/hooks/hooks_messages.mes b/src/lib/hooks/hooks_messages.mes
@@ -104,7 +104,7 @@ has been successfully loaded.
 % HOOKS_LIBRARY_LOADING loading hooks library %1
 Logged at debug log level 40.
 This is a debug message output just before the specified library is loaded.
-If the action is successfully, it will be followed by the
+If the action is successful, it will be followed by the
 HOOKS_LIBRARY_LOADED informational message.
 
 % HOOKS_LIBRARY_MULTI_THREADING_COMPATIBLE hooks library %1 reports its multi-threading compatibility as %2

diff --git a/src/lib/log/log_messages.mes b/src/lib/log/log_messages.mes
@@ -65,13 +65,13 @@ This error is generated when the compiler finds a $NAMESPACE directive
 with no arguments.
 
 % LOG_NO_MESSAGE_ID line %1: message definition line found without a message ID
-Within a message file, message are defined by lines starting with a "%".
+Within a message file, messages are defined by lines starting with a "%".
 The rest of the line should comprise the message ID and text describing
 the message.  This error indicates the message compiler found a line in
 the message file comprising just the "%" and nothing else.
 
 % LOG_NO_MESSAGE_TEXT line %1: line found containing a message ID ('%2') and no text
-Within a message file, message are defined by lines starting with a "%".
+Within a message file, messages are defined by lines starting with a "%".
 The rest of the line should comprise the message ID and text describing
 the message.  This error indicates the message compiler found a line
 in the message file comprising just the "%" and message identification,