From: Peter van Dijk Date: Mon, 21 Oct 2013 12:23:31 +0000 (+0200) Subject: spelling, mostly thanks to codespell X-Git-Tag: rec-3.6.0-rc1~388 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1f6c983f426910570ac591cb042fdcb3f9c7de85;p=pdns spelling, mostly thanks to codespell --- diff --git a/modules/remotebackend/example.rb b/modules/remotebackend/example.rb index 031774a74..3b7f2b43e 100644 --- a/modules/remotebackend/example.rb +++ b/modules/remotebackend/example.rb @@ -130,7 +130,7 @@ Coefficient: 5lP9IFknvFgaXKCs8MproehHSFhFTWac4557HIn03KrnlGOKDcY6DC/vgu1e42bEZ4J ## AXFR support ## Do note that having AXFR here is somewhat stupid since ## we generate records above. But it is still included - ## for sake of having an example. Do not do ths in production. + ## for sake of having an example. Do not do this in production. def do_list(args) if args["zonename"] == "example.com" return [ diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml index f2ead5039..f09153e5b 100755 --- a/pdns/docs/pdns.xml +++ b/pdns/docs/pdns.xml @@ -10580,7 +10580,7 @@ name IN A 192.0.2.4 - Daniel Drown discovered that his PowerDNS 2.9.21.1 installation crashed on receiving a HINFO CH query. In his enthousiasm, he shared + Daniel Drown discovered that his PowerDNS 2.9.21.1 installation crashed on receiving a HINFO CH query. In his enthusiasm, he shared his discovery with the world, forcing a rapid over the weekend release cycle. @@ -13539,7 +13539,7 @@ sql> insert into domainmetadata (domain_id, kind, content) values (7,'ALLOW-AXFR Tell PowerDNS to forward to the master server if the zone is configured as slave. Masters are determined by the masters field in the domains table. The default behaviour is enabled (yes), which means that it will try to forward. In the processing of the update packet, the allow-2136-from and TSIG-2136-ALLOW are processed first, so those permissions apply before the forward-2136 is used. - It will try all masters that you have configured until one is succesful. + It will try all masters that you have configured until one is successful. @@ -13610,7 +13610,7 @@ sql> select id from domains where name='powerdnssec.org'; sql> insert into domainmetadata(domain_id, kind, content) values(5, ‘FORWARD-2136’,’’); - There is no content, the existance of the entry enables the forwarding. + There is no content, the existence of the entry enables the forwarding. This domain-specific setting is only useful when the configuration option forward-2136 is set to 'no', as that will disable it globally. Using the domainmetadata setting than allows you to enable it per domain. @@ -13645,7 +13645,7 @@ sql> select id from domains where name='powerdnssec.org'; 5 sql> insert into domainmetadata(domain_id, kind, content) values(5, ‘SOA-EDIT-2136’,’INCREASE’); - This will make the SOA Serial increase by one, for every succesful update. + This will make the SOA Serial increase by one, for every successful update. SOA-EDIT-2136 settings These are the settings available for SOA-EDIT-2136. @@ -13854,7 +13854,7 @@ sql> insert into domainmetadata (domain_id, kind, content) values (6, 'TSIG-ALLO If there are records updated and the SOA record was not modified, the SOA serial is updated. See . The cache for this record is purged. - The transaction with the backend is commited. If this fails, ServFail is returned. + The transaction with the backend is committed. If this fails, ServFail is returned. NoError is returned. @@ -14019,7 +14019,7 @@ sql> insert into domainmetadata (domain_id, kind, content) values (6, 'TSIG-ALLO Like allow-from, except reading from file. Overrides the 'allow-from' setting. - To use this feature, supply one netmask per line, with optional comments preceeded by a #. + To use this feature, supply one netmask per line, with optional comments preceded by a #. Available since version 3.1.5. diff --git a/pdns/docs/pdns_control.8 b/pdns/docs/pdns_control.8 index 35caff64e..dfa1269b2 100644 --- a/pdns/docs/pdns_control.8 +++ b/pdns/docs/pdns_control.8 @@ -64,7 +64,7 @@ specified the entire cache is purged. Instructs backends that new domains may have appeared in the database, or, in the case of the Bind backend, in named.conf. .TP .B retrieve \fI\fR -Retrieve a slave domain from its master. Done nearly immediatly. +Retrieve a slave domain from its master. Done nearly immediately. .TP .B set \fI \fR Set the configuration parameter \fI\fR to \fI\fR. Currently diff --git a/pdns/unix_utility.cc b/pdns/unix_utility.cc index 005284cb3..4dcf5b70a 100644 --- a/pdns/unix_utility.cc +++ b/pdns/unix_utility.cc @@ -256,7 +256,7 @@ time_t Utility::timegm(struct tm *const t) /* After 2100 we have to subtract 3 leap years for every 400 years This is not intuitive. Most mktime implementations do not support - dates after 2059, anyway, so we might leave this out for it's + dates after 2059, anyway, so we might leave this out for its bloat. */ if ((years -= 131) >= 0) { years /= 100; diff --git a/regression-tests/1dyndns-update-add-delete-mx/description b/regression-tests/1dyndns-update-add-delete-mx/description index 0e929fa03..8fa12abdf 100644 --- a/regression-tests/1dyndns-update-add-delete-mx/description +++ b/regression-tests/1dyndns-update-add-delete-mx/description @@ -1,3 +1,3 @@ A test to see if RFC2136 add and delete record works properly on an MX record, -this is interesting because the priority is stored seperately in powerdns and +this is interesting because the priority is stored separately in powerdns and it is part of the RDATA. diff --git a/regression-tests/1dyndns-update-delete-mx-prio/description b/regression-tests/1dyndns-update-delete-mx-prio/description index 4c5fd4367..db3d297b6 100644 --- a/regression-tests/1dyndns-update-delete-mx-prio/description +++ b/regression-tests/1dyndns-update-delete-mx-prio/description @@ -1,4 +1,4 @@ This test checks to see if deleting a MX record with a specific Priority works correctly. This is interesting because the gsql-backends store priority in a -seperate field, where other backends probably store it together with the content +separate field, where other backends probably store it together with the content (or RDATA). diff --git a/regression-tests/README b/regression-tests/README index 8126fbfe4..458048a1c 100644 --- a/regression-tests/README +++ b/regression-tests/README @@ -45,7 +45,7 @@ fails otherwise, for cosmetical reasons. Method of operation ------------------- -Each directory contains a command that, when executed, proces the 'cleandig' +Each directory contains a command that, when executed, process the 'cleandig' output for the answer the nameserver sent. This output is stored in the file 'real_result', and compared to 'expected_result' or one of its replacement files.