From: Jeremy C. Reed Date: Fri, 15 Aug 2014 15:35:31 +0000 (-0500) Subject: fix typos or misspellings X-Git-Tag: v9.11.0a1~1397 X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=821350367e2c7313c02eb275e8e05d5193b47cfd;p=thirdparty%2Fbind9.git fix typos or misspellings --- diff --git a/README b/README index 09b0178e446..8298ae1f889 100644 --- a/README +++ b/README @@ -141,7 +141,7 @@ BIND 9.10.0 browsers. - The statistics channel can now provide data in JSON format as well as XML. - - New stats counters track TCP and UDP queries recieved + - New stats counters track TCP and UDP queries received per zone, and EDNS options received in total. - The internal and export versions of the BIND libraries (libisc, libdns, etc) have been unified so that external diff --git a/bin/dig/dig.docbook b/bin/dig/dig.docbook index 6b2b7850a8d..ace24ac91b2 100644 --- a/bin/dig/dig.docbook +++ b/bin/dig/dig.docbook @@ -560,7 +560,7 @@ Set the DSCP code point to be used when sending the query. Valid DSCP code points are in the range - [0..63]. By default no code point is explictly set. + [0..63]. By default no code point is explicitly set. @@ -856,7 +856,7 @@ - Send an EDNS Client Subnet option with the speciifed + Send an EDNS Client Subnet option with the specified IP address or network prefix. diff --git a/bin/python/dnssec-coverage.docbook b/bin/python/dnssec-coverage.docbook index 50997339baf..7f335f32473 100644 --- a/bin/python/dnssec-coverage.docbook +++ b/bin/python/dnssec-coverage.docbook @@ -150,7 +150,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.) @@ -179,7 +179,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/bin/tests/system/geoip/data/README b/bin/tests/system/geoip/data/README index 672959af0e3..11f51e9a8ef 100644 --- a/bin/tests/system/geoip/data/README +++ b/bin/tests/system/geoip/data/README @@ -3,7 +3,7 @@ See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. The data data files in this directory are sample GeoIP databases, generated from the corresponding CSV files. Thanks to MaxMind, Inc. -for assitance with producing these files. +for assistance with producing these files. Unless otherwise noted, the databases only support IPv4: @@ -18,7 +18,7 @@ GeoIPDoain.dat: Domain Name GeoIPASNum.dat: AS Number GeoIPNetSpeed.dat: Net Speed -GeoIP.dat can also be egenerated using the open source 'geoip-csv-to-dat' +GeoIP.dat can also be generated using the open source 'geoip-csv-to-dat' utility: $ geoip-csv-to-dat -i "BIND9 geoip test data v1" -o GeoIP.dat << EOF diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index c37dfc2ff44..c2cd9db416f 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2905,7 +2905,7 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. 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 expalantions of particular parameters + See the explanations of particular parameters that use size_spec for details on how they interpret its use. @@ -5770,7 +5770,7 @@ options { restarted (NTA's do not persist across restarts). - For convienience, TTL-style time unit suffixes can be + For convenience, TTL-style time unit suffixes can be used to specify the NTA lifetime in seconds, minutes or hours. defaults to one hour. It cannot exceed one day. @@ -5798,13 +5798,13 @@ options { the negative trust anchor is allowed to expire early. - Validity checks can be disabled for an indivdiual + Validity checks can be disabled for an individual NTA by using rndc nta -f, or for all NTA's by setting to zero. - For convienience, TTL-style time unit suffixes can be + For convenience, TTL-style time unit suffixes can be used to specify the NTA recheck interval in seconds, minutes or hours. The default is five minutes. @@ -7421,7 +7421,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 @@ -7429,12 +7429,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, @@ -10229,7 +10229,7 @@ rate-limit { is over 1000 and the ratio is over 10), the one that appears last in the configuration file is the one chosen. To eliminate any ambiguity, it is recommended - that under normal circumstnaces, rate limiting bands should + that under normal circumstances, rate limiting bands should be configured using either size or ratio parameters, but not both. @@ -14124,8 +14124,7 @@ view external { 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/dlz.xml b/doc/arm/dlz.xml index 22ec2e4bd7a..74a9f2a5004 100644 --- a/doc/arm/dlz.xml +++ b/doc/arm/dlz.xml @@ -20,7 +20,7 @@ DLZ (Dynamically Loadable Zones) - DLZ (Dynamically Loadable Zones) is an extention to BIND 9 that allows + DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows zone data to be retrieved directly from an external database. There is no required format or schema. DLZ drivers exist for several different database backends including PostgreSQL, MySQL, and LDAP and can be diff --git a/doc/arm/libdns.xml b/doc/arm/libdns.xml index 6134ff6521f..cf7b94350e9 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 f1d011d15d3..9a4c2f4c6c3 100644 --- a/doc/arm/pkcs11.xml +++ b/doc/arm/pkcs11.xml @@ -131,7 +131,7 @@ $ ./configure --enable-native-pkcs11 \ The modified OpenSSL code is included in the BIND 9 release, - in the form of a context diff against the latest verions of + 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 diff --git a/lib/lwres/man/lwres.docbook b/lib/lwres/man/lwres.docbook index a6722075a50..26723e5f0ca 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 62c71446a61..8743696c123 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 8cd763958ba..8f40990b478 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 5c6bc08d953..0a0c4704aa2 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.