diff --git a/bin/pkcs11/pkcs11-destroy.docbook b/bin/pkcs11/pkcs11-destroy.docbook index be9539bf76..3ccd6b9d68 100644 --- a/bin/pkcs11/pkcs11-destroy.docbook +++ b/bin/pkcs11/pkcs11-destroy.docbook @@ -126,10 +126,10 @@ SEE ALSO - pkcs11-list3 + pkcs11-keygen8 , - pkcs11-keygen3 + pkcs11-list8 diff --git a/bin/pkcs11/pkcs11-list.docbook b/bin/pkcs11/pkcs11-list.docbook index 9b1279299e..3949364024 100644 --- a/bin/pkcs11/pkcs11-list.docbook +++ b/bin/pkcs11/pkcs11-list.docbook @@ -130,10 +130,10 @@ SEE ALSO - pkcs11-keygen3 + pkcs11-destroy8 , - pkcs11-destroy3 + pkcs11-keygen8 diff --git a/bin/python/dnssec-coverage.docbook b/bin/python/dnssec-coverage.docbook index 571eae473b..f6b2666cf6 100644 --- a/bin/python/dnssec-coverage.docbook +++ b/bin/python/dnssec-coverage.docbook @@ -130,7 +130,7 @@ This option is mandatory unless the has been used to specify a zone file. (If has - been specified, this option may still be used; it will overrde + been specified, this option may still be used; it will override the value found in the file.) @@ -159,7 +159,7 @@ been used to specify a zone file, or a default key TTL was set with the to dnssec-keygen. (If either of those is true, - this option may still be used; it will overrde the value found + this option may still be used; it will override the value found in the zone or key file.) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index 0815ef3683..155723117f 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2871,12 +2871,14 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. Integers may take values 0 <= value <= 18446744073709551615, though - certain parameters may use a more limited range - within these extremes. In most cases, setting a - value to 0 does not literally mean zero; it means - "undefined" or "as big as psosible", depending on - the context. See the expalantions of particular - parameters that use size_spec + certain parameters + (such as max-journal-size) may + use a more limited range within these extremes. + In most cases, setting a value to 0 does not + literally mean zero; it means "undefined" or + "as big as possible", depending on the context. + See the explanations of particular parameters + that use size_spec for details on how they interpret its use. @@ -7102,7 +7104,7 @@ options { than matching the case of the records entered in the zone file. This allows responses to exactly match the query, which is required by some clients - due to incorrect use of case-sensitive comparisions. + due to incorrect use of case-sensitive comparisons. Case-insensitive compression is always @@ -7110,12 +7112,12 @@ options { the client matches this ACL. - There are circusmstances in which named + There are circumstances in which named will not preserve the case of owner names of records: if a zone file defines records of different types with the same name, but the capitalization of the name is different (e.g., "www.example.com/A" and - "WWW.EXAMPLE.COM/AAAA"), then all resposnes for that + "WWW.EXAMPLE.COM/AAAA"), then all responses for that name will use the first version of the name that was used in the zone file. This limitation may be addressed in a future release. However, @@ -13305,8 +13307,7 @@ example.com. NS ns2.example.net. Each RR can have a TTL as the second field in the RR, which will control how long other - servers can cache - the it. + servers can cache it. diff --git a/doc/arm/libdns.xml b/doc/arm/libdns.xml index 6134ff6521..cf7b94350e 100644 --- a/doc/arm/libdns.xml +++ b/doc/arm/libdns.xml @@ -270,7 +270,7 @@ $ make consists of a single domain name. Example: www.example.com - mx.examle.net + mx.example.net ns.xxx.example diff --git a/doc/arm/pkcs11.xml b/doc/arm/pkcs11.xml index b4e22bb351..050bce8508 100644 --- a/doc/arm/pkcs11.xml +++ b/doc/arm/pkcs11.xml @@ -68,12 +68,13 @@ is an example of such a device. - The modified OpenSSL code is included in the BIND 9 release, - in the form of a context diff against the latest verions of - OpenSSL. OpenSSL 0.9.8, 1.0.0 and 1.0.1 are supported; there are - separate diffs for each version. In the examples to follow, - we use OpenSSL 0.9.8, but the same methods work with OpenSSL 1.0.0 - and 1.0.1. + + The modified OpenSSL code is included in the BIND 9 release, + in the form of a context diff against the latest versions of + OpenSSL. OpenSSL 0.9.8, 1.0.0, and 1.0.1 are supported; there are + separate diffs for each version. In the examples to follow, + we use OpenSSL 0.9.8, but the same methods work with OpenSSL + 1.0.0 and 1.0.1. The latest OpenSSL versions at the time of the BIND release diff --git a/lib/lwres/man/lwres.docbook b/lib/lwres/man/lwres.docbook index a6722075a5..26723e5f0c 100644 --- a/lib/lwres/man/lwres.docbook +++ b/lib/lwres/man/lwres.docbook @@ -63,7 +63,7 @@ and address-to-hostname lookup services to applications by transmitting lookup requests to a resolver daemon lwresd - running on the local host. The resover daemon performs the + running on the local host. The resolver daemon performs the lookup using the DNS or possibly other name service protocols, and returns the results to the application through the library. The library and resolver daemon communicate using a simple diff --git a/lib/lwres/man/lwres_gabn.docbook b/lib/lwres/man/lwres_gabn.docbook index 62c71446a6..8743696c12 100644 --- a/lib/lwres/man/lwres_gabn.docbook +++ b/lib/lwres/man/lwres_gabn.docbook @@ -120,7 +120,7 @@ void There are four main functions for the getaddrbyname opcode. One render function converts a getaddrbyname request structure — lwres_gabnrequest_t — - to the lighweight resolver's canonical format. + to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a getaddrbyname request structure. Another render function converts the getaddrbyname response structure diff --git a/lib/lwres/man/lwres_noop.docbook b/lib/lwres/man/lwres_noop.docbook index 8cd763958b..8f40990b47 100644 --- a/lib/lwres/man/lwres_noop.docbook +++ b/lib/lwres/man/lwres_noop.docbook @@ -127,7 +127,7 @@ void There are four main functions for the no-op opcode. One render function converts a no-op request structure — lwres_nooprequest_t — - to the lighweight resolver's canonical format. + to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a no-op request structure. Another render function converts the no-op response structure — diff --git a/lib/lwres/man/lwres_resutil.docbook b/lib/lwres/man/lwres_resutil.docbook index 5c6bc08d95..0a0c4704aa 100644 --- a/lib/lwres/man/lwres_resutil.docbook +++ b/lib/lwres/man/lwres_resutil.docbook @@ -153,7 +153,7 @@ typedef struct { The lightweight resolver uses lwres_getaddrsbyname() to perform - foward lookups. + forward lookups. Hostname name is looked up using the resolver context ctx for memory allocation.