BIND 10 trac2765, updated. 1a1447425c6acc5601ea59d18c3638a0e65f0aed [2765] Fixed typo in the libdhcp++ developer's guide.

[BIND 10 source code commits]

The branch, trac2765 has been updated
       via  1a1447425c6acc5601ea59d18c3638a0e65f0aed (commit)
      from  68aae7c97b56de73918721193ec1ee29bee638e6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 1a1447425c6acc5601ea59d18c3638a0e65f0aed
Author: Marcin Siodelski <marcin at isc.org>
Date:   Wed Dec 4 16:13:55 2013 +0100

    [2765] Fixed typo in the libdhcp++ developer's guide.

-----------------------------------------------------------------------

Summary of changes:
 src/lib/dhcp/libdhcp++.dox |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-----------------------------------------------------------------------
diff --git a/src/lib/dhcp/libdhcp++.dox b/src/lib/dhcp/libdhcp++.dox
index 34993af..6397a4b 100644
--- a/src/lib/dhcp/libdhcp++.dox
+++ b/src/lib/dhcp/libdhcp++.dox
@@ -148,7 +148,7 @@ response will be received and processed by all clients in the particular
 network. Therefore, the preferred approach is that the server unicasts its
 response to a new address being assigned for the client. This client will
 identify itself as a target of this message by checking chaddr and/or
-Client Identifier value. In the same time, the other clients in the network
+Client Identifier value. At the same time, the other clients in the network
 will not receive the unicast message. The major problem that arises with this
 approach is that the client without an IP address doesn't respond to ARP
 messages. As a result, server's response will not be sent over IP/UDP