Francis Dupont 10 years ago
parent
commit
2de38cb988
1 changed files with 2 additions and 2 deletions
  1. 2 2
      src/bin/dhcp4/dhcp4.dox

+ 2 - 2
src/bin/dhcp4/dhcp4.dox

@@ -21,7 +21,7 @@ isc::dhcp::Dhcpv4Srv class. It uses \ref libdhcp extensively,
 especially isc::dhcp::Pkt4, isc::dhcp::Option and
 isc::dhcp::IfaceMgr classes. Currently this code offers skeleton
 functionality, i.e. it is able to receive and process incoming
-requests and trasmit responses. However, it does not have database
+requests and transmit responses. However, it does not have database
 management, so it returns only one, hardcoded lease to whoever asks
 for it.
 
@@ -174,7 +174,7 @@ be interpreted as a class name.
 In principle any given packet can belong to zero or more classes. As the current
 classifier is very modest, there's only one way to assign a class (based on vendor class
 option), the ability to assign more than one class to a packet is not yet exercised.
-Neverthless, there is such a possibility and it will be used in a near future. To
+Nevertheless, there is such a possibility and it will be used in a near future. To
 check whether a packet belongs to given class, isc::dhcp::Pkt4::inClass method should
 be used.