vendor/ldns/1.8.3

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/API.xml b/doc/API.xml
index 554420d11c29..3d873d88f49a 100644
--- a/doc/API.xml
+++ b/doc/API.xml
@@ -68,7 +68,7 @@ A small abstract will come here, TBD.
 <section title="Introduction">
 <t>
 LibDNS (or lDNS) is modelled after the Net::DNS perl library. It has
-been shown that Net::DNS  can be used vefficiently for
+been shown that Net::DNS  can be used efficiently for
 programming DNS aware applications. We want to bring the same
 level of efficiency to C programmers.
 </t>
@@ -97,9 +97,9 @@ Further more it is to be expected that lDNS will depend on OpenSSL for
 its cryptography.
 </t>
 <t>
-As said, lDNS is modelled after Net::DNS, therefor its application API
+As said, lDNS is modelled after Net::DNS, therefore its application API
 looks very much like the one used for Net::DNS. Some modification are made
-ofcourse, because not all functionality of Perl can be caught in C.
+of course, because not all functionality of Perl can be caught in C.
 </t>
 
 <t>
@@ -336,7 +336,7 @@ Returns a pointer to a ldns_rr_list of representing the additional
 section of the packet.
 	
 </t>
-<t hangText=" void ldsn_pkt_print(ldns_pkt *pkt):">
+<t hangText=" void ldns_pkt_print(ldns_pkt *pkt):">
 Prints the packet data on the standard output in an ASCII format similar
 to that used in DNS zone files. See RFC1035.
       
@@ -400,7 +400,7 @@ insert your long list here.
 <section title="Examples">
 <t>
 A small example, which queries a nameserver on localhost
-to diplay the MX records for miek.nl.
+to display the MX records for miek.nl.
 </t>
 
 <t>