spelling, mostly thanks to codespell

diff --git a/modules/remotebackend/example.rb b/modules/remotebackend/example.rb
index 031774a7441c7c04f5425365fb07ae9334839a16..3b7f2b43ee2e4956a44f9d6746bb47a5785f2373 100644 (file)
--- 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 f2ead50390c449ec800bd5edeb073b0b519488a8..f09153e5b7647a38d39c3186208011a3e5315841 100755 (executable)
--- a/pdns/docs/pdns.xml
+++ b/pdns/docs/pdns.xml
@@ -10580,7 +10580,7 @@ name         IN            A        192.0.2.4
        </table>
       </para>
       <para>
-       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.
       </para>
       <para>
@@ -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 <command>allow-2136-from</command> and
               <command>TSIG-2136-ALLOW</command> are processed first, so those permissions apply before the <command>forward-2136</command> 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.
             </para>
           </listitem>
         </varlistentry>
@@ -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’,’’);
               </programlisting>
 
-              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 <command>forward-2136</command> is set to 'no', as that will disable it globally.
               Using the domainmetadata setting than allows you to enable it per domain.
             </para>
@@ -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’);
         </programlisting>
-        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.
       </para>
       <sect2 id="rfc2136-soa-edit-settings"><title>SOA-EDIT-2136 settings</title>
         <para>These are the settings available for <command>SOA-EDIT-2136</command>.</para>
@@ -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 <xref linkend="rfc2136-soa-edit"/>.
             The cache for this record is purged.
           </para></listitem>
-          <listitem><para>The transaction with the backend is commited. If this fails, ServFail is returned.</para></listitem>
+          <listitem><para>The transaction with the backend is committed. If this fails, ServFail is returned.</para></listitem>
           <listitem><para>NoError is returned.</para></listitem>
         </orderedlist>
       </para>
@@ -14019,7 +14019,7 @@ sql> insert into domainmetadata (domain_id, kind, content) values (6, 'TSIG-ALLO
            <listitem>
              <para>
                Like <command>allow-from</command>, 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.
              </para>
            </listitem>

diff --git a/pdns/docs/pdns_control.8 b/pdns/docs/pdns_control.8
index 35caff64e155f6d6bb0b70f71cb83334d3195a79..dfa1269b231cb47977e6ef36a7a7587da4647e8f 100644 (file)
--- 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<domain>\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<variable> <value>\fR
 Set the configuration parameter \fI<variable>\fR to \fI<value>\fR. Currently

diff --git a/pdns/unix_utility.cc b/pdns/unix_utility.cc
index 005284cb3d8fe7691612f333b0993d795e564b24..4dcf5b70aa53159adc78eef8c13f0a1384f600fa 100644 (file)
--- 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 0e929fa03c0834a8591e6fe4ec623fa7011f20eb..8fa12abdf50eb3cacb36faee8173e11418e77f50 100644 (file)
--- 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 4c5fd43671e2049d3b1cf9ab0b2ff3013ebb6b13..db3d297b6d63b5d18ce856203e7614dde44d433d 100644 (file)
--- 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 8126fbfe419167bdff929704c07e7dc13d710f04..458048a1c764adcdc20d2ad310e95d9462d48251 100644 (file)
--- 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.