[3852] Corrected typos in the new allocation engine messages file

src/lib/dhcpsrv/alloc_engine_messages.mes

@@ -38,7 +38,7 @@ Alternatively, if the you know that the number of concurrently active
 clients is less than the addresses you have available, you may want to
 consider reducing the lease lifetime.  In this way, addresses allocated
 to clients that are no longer active on the network will become available
-available sooner.
+sooner.
 
 % ALLOC_ENGINE_V4_DISCOVER_HR %1: client sending DHCPDISCOVER has reservation for the address %2
 This message is issued when the allocation engine determines that the
@@ -55,31 +55,31 @@ to offer the same lease to the client.
 
 % ALLOC_ENGINE_V4_OFFER_NEW_LEASE %1: allocation engine will try to offer new lease to the client
 This message is issued when the allocation engine will try to
-offer new lease to the client. This is the case when the
+offer a new lease to the client. This is the case when the
 client doesn't have any existing lease, it has no reservation
 or the existing or reserved address is leased to another client.
-Also, the client didn't specify the hint, or the address in
+Also, the client didn't specify a hint, or the address in
 the hint is in use.
 
 % ALLOC_ENGINE_V4_OFFER_REQUESTED_LEASE %1: allocation engine will try to offer requested lease to the client
 This message is issued when the allocation engine will try to
-offer lease specified in the hint, because the client doesn't
+offer the lease specified in the hint, because the client doesn't
 have any reservations or the reserved or currently allocated
 address is leased to another client.
 
 % ALLOC_ENGINE_V4_REQUEST_ADDRESS_RESERVED %1: requested address %2 is reserved
 This message is issued when the allocation engine refused to
-allocate address requested by the client, because this
+allocate address requested by the client because this
 address is reserved for another client.
 
 % ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED %1: trying to allocate requested address %2
 This message is issued when the allocation engine is trying
-to allocate (or reuse expired) address which has been
+to allocate (or reuse an expired) address which has been
 requested by the client.
 
 % ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE %1: extending lifetime of the lease for address %2
 This message is issued when the allocation engine determines
-that the client already has a lease which lifetime can be
+that the client already has a lease whose lifetime can be
 extended, and which can be returned to the client.
 
 % ALLOC_ENGINE_V4_REQUEST_IN_USE %1: requested address %2 is in use
@@ -87,10 +87,10 @@ This message is issued when the client is requesting or has a
 reservation for an address which is in use.
 
 % ALLOC_ENGINE_V4_REQUEST_INVALID %1: client having a reservation for address %2 is requesting invalid address %3
-This message is logged when the client having a reservation for
+This message is logged when the client, having a reservation for
 one address, is requesting a different address. The client is
-only allowed to do it when the reserved address is in use by
-another client. However, the allocation engine has now
+only allowed to do this when the reserved address is in use by
+another client. However, the allocation engine has 
 determined that the reserved address is available and the
 client should request the reserved address.
 
@@ -101,20 +101,19 @@ which addresses are dynamically allocated. The client also
 doesn't have reservation for this address. This address
 could only be allocated if the client had reservation for it.
 
-% ALLOC_ENGINE_V4_REQUEST_PICK_ADDRESS %1: client hasn't requested any address - picking available address from the pool
-This message is logged when the client hasn't specified any address
-to be allocated. Client should always do it, but we want to be
-liberal. The allocation engine will try to pick an available
-address from the dynamic pool and allocate to the client.
+% ALLOC_ENGINE_V4_REQUEST_PICK_ADDRESS %1: client hasn't specified an address - picking available address from the pool
+This message is logged when the client hasn't specified any
+preferred address (the client should always do it, but Kea 
+tries to be forgiving). The allocation engine will try to pick an available
+address from the dynamic pool and allocate it to the client.
 
 % ALLOC_ENGINE_V4_REQUEST_REMOVE_LEASE %1: removing previous client's lease %2
 This message is logged when the allocation engine removes previous
-lease for the client, because the cliet has been allocated new
-lease.
+lease for the client because the cliet has been allocated new one.
 
 % ALLOC_ENGINE_V4_REQUEST_USE_HR %1: client hasn't requested specific address, using reserved address %2
 This message is issued when the client is not requesting any specific
-address and the allocation engine determines that there is a
+address but the allocation engine has determined that there is a
 reservation for this client. The allocation engine will try to
 allocate the reserved address.
 
@@ -151,7 +150,7 @@ for the client and the client can continue using it.
 % ALLOC_ENGINE_V6_ALLOC_LEASES_HR %1: leases and static reservations found for client
 This message is logged when the allocation engine is in the process of
 allocating leases for the client, it found existing leases and static
-reservations for the client. The allocation angine will verify if
+reservations for the client. The allocation engine will verify if
 existing leases match reservations. Those leases that are reserved for
 other clients and those that are not reserved for the client will
 be removed. All leases matching the reservations will be renewed
@@ -159,17 +158,16 @@ and returned.
 
 % ALLOC_ENGINE_V6_ALLOC_NO_LEASES_HR %1: no leases found but reservations exist for client
 This message is logged when the allocation engine is in the process of
-allocating leases for the client, it hasn't found any existing leases
+allocating leases for the client. It hasn't found any existing leases
 for this client, but the client appears to have static reservations.
 The allocation engine will try to allocate the reserved resources for
 the client.
 
 % ALLOC_ENGINE_V6_ALLOC_NO_V6_HR %1: unable to allocate reserved leases - no IPv6 reservations
 This message is logged when the allocation engine determines that the
-client has no IPv6 reservations and thus allocation engine will have
+client has no IPv6 reservations and thus the allocation engine will have
 to try to allocate allocating leases from the dynamic pool or stop
-the allocation process if none leases can be allocated from the
-dynamic pool.
+the allocation process if none can be allocated.
 
 % ALLOC_ENGINE_V6_ALLOC_LEASES_NO_HR %1: no reservations found but leases exist for client
 This message is logged when the allocation engine is in the process if
@@ -185,7 +183,7 @@ leases.
 
 % ALLOC_ENGINE_V6_EXTEND_ALLOC_UNRESERVED %1: allocate new (unreserved) leases for the renewing client
 This debug message is issued when the allocation engine is trying to
-allocate new leases for the renewing client, because it was unable to
+allocate new leases for the renewing client because it was unable to
 renew any of the existing client's leases, e.g. because leases are
 reserved for another client or for any other reason.
 
@@ -200,7 +198,7 @@ lifetime is being extended (renew or rebind).
 % ALLOC_ENGINE_V6_EXTEND_NEW_LEASE_DATA %1: new lease information for the lease being extended: %2
 This debug message prints updated information about the lease to be
 extended. If the lease update is successful, the information printed
-by this message will be stored in the database for this lease.
+by this message will be stored in the database.
 
 % ALLOC_ENGINE_V6_EXTEND_ERROR %1: allocation engine experienced error with attempting to extend lease lifetime: %2
 This error message indicates that an error was experienced during Renew
@@ -228,19 +226,19 @@ This informational message signals that the specified client was assigned the pr
 reserved for it.
 
 % ALLOC_ENGINE_V6_RENEW_HR %1: allocating leases reserved for the client as a result of Renew
-This debug message is issued when the allocation engine will try to
+This debug message is issued when the allocation engine tries to
 allocate reserved leases for the client sending a Renew message.
 The server will also remove any leases that the client is trying
-to renew, which are not reserved for the client.
+to renew that are not reserved for the client.
 
 % ALLOC_ENGINE_V6_RENEW_REMOVE_RESERVED %1: checking if existing client's leases are reseved for another client
 This message is logged when the allocation engine finds leases for
 the client and will check if these leases are reserved for another
 client. If they are, they will not be renewed for the client
-requsting their renewal.
+requesting their renewal.
 
 % ALLOC_ENGINE_V6_RENEW_REMOVE_UNRESERVED %1: dynamically allocating leases for the renewing client
-This debug message is issued when the allocation engine is trying
+This debug message is issued as the allocation engine is trying
 to dynamically allocate new leases for the renewing client. This
 is the case when the server couldn't renew any of the existing
 client's leases, e.g. because leased resources are reserved for