spelling: cannot

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

diff --git a/docs/backends/ldap.rst b/docs/backends/ldap.rst
index 4a5b29735c4a8e620d80863ec29afd4d1efe8758..9779f32491a35b3efe39623e31aa18aa15db0a3f 100644 (file)
--- a/docs/backends/ldap.rst
+++ b/docs/backends/ldap.rst
@@ -431,7 +431,7 @@ Tree mode requires each component to be a dc element of its own:
 To use this kind of record, add the dnsdomain2 schema to the
 configuration of the LDAP server.
 
-**CAUTION:** ``ldap-method=strict`` can not be used if zone transfers
+**CAUTION:** ``ldap-method=strict`` cannot be used if zone transfers
 (AXFR) are needed to other name servers. Distributing zones can only be
 done directly via LDAP replication in this case, because for a full zone
 transfer the reverse records are missing.

diff --git a/docs/common/secpoll.rst b/docs/common/secpoll.rst
index 051b7ffa3edcf7ffd550472330af9f103f63dcd8..d181f1ffaf09a48b641e7810b7a5866032a56190 100644 (file)
--- a/docs/common/secpoll.rst
+++ b/docs/common/secpoll.rst
@@ -46,7 +46,7 @@ It could be lowered however if we discover the security status is less urgent th
 If resolution fails, and the previous security-status was 1, the new security-status becomes 0 ('no data').
 If the security-status was higher than 1, it will remain that way, and not get set to 0.
 
-In this way, security-status of 0 really means 'no data', and can not mask a known problem.
+In this way, security-status of 0 really means 'no data', and cannot mask a known problem.
 
 Distributions
 ~~~~~~~~~~~~~

diff --git a/docs/domainmetadata.rst b/docs/domainmetadata.rst
index 16ca81d9f9a726f4dc0792a0ff7d1a0180a65814..5f399037822bc53591e1101d1ae61c0951fcf32d 100644 (file)
--- a/docs/domainmetadata.rst
+++ b/docs/domainmetadata.rst
@@ -27,7 +27,7 @@ The following options can only be read (not written to) via the HTTP API metadat
 * PRESIGNED
 * TSIG-ALLOW-AXFR
 
-The option SOA-EDIT-API can not be written or read via the HTTP API metadata endpoint.
+The option SOA-EDIT-API cannot be written or read via the HTTP API metadata endpoint.
 
 .. _metadata-allow-axfr-from:
 

diff --git a/docs/guides/recursion.rst b/docs/guides/recursion.rst
index a1756ed976cd8cbb981bc83b053c94e1f05fbeaf..a12fc958f174ba8c4d1506018bf2adfb0c621ac6 100644 (file)
--- a/docs/guides/recursion.rst
+++ b/docs/guides/recursion.rst
@@ -61,7 +61,7 @@ and port 5300 change the following in ``pdns.conf``:
 This is most likely an ``apt-get`` or ``yum install`` away, see the
 `Recursor documentation <https://doc.powerdns.com/recursor/getting-started.html#installation>`__ for more information.
 
-It might be possible that the Recursor can not start as the listen
+It might be possible that the Recursor cannot start as the listen
 address is in use by the Authoritative Server, this is fine for now.
 
 Now configure the listen addresses and ACL for the Recursor to be the
@@ -144,7 +144,7 @@ This is most likely an ``apt-get`` or ``yum install`` away, see the
 `Recursor's Install Guide <https://doc.powerdns.com/recursor/getting-started.html#installation>`__ for more
 information.
 
-It might be possible that the Recursor can not start as the listen
+It might be possible that the Recursor cannot start as the listen
 address is in use by the Authoritative Server, this is fine for now.
 
 Configure the recursor to listen on the local loopback interface on a

diff --git a/docs/guides/svcb.rst b/docs/guides/svcb.rst
index 8c5c2d4a23667e8c8839bac144ce4c813a521a05..b0ca7e0da067ace663bc45eed154d3f2c9f106ca 100644 (file)
--- a/docs/guides/svcb.rst
+++ b/docs/guides/svcb.rst
@@ -66,7 +66,7 @@ Consider the following zone content::
   no-ipv6.example.org  IN HTTPS 1 . ipv4hint=auto ipv6hint=auto
   no-ipv6.example.org  IN A     192.0.2.2
 
-Here, no AAAA record exists for www.example.org, so PowerDNS can not put any data in the ipv6hint.
+Here, no AAAA record exists for www.example.org, so PowerDNS cannot put any data in the ipv6hint.
 In this case, the ipv6hint parameter is dropped when answering the query (and on AXFR)::
 
   ;; QUESTION SECTION:

diff --git a/docs/lua-records/index.rst b/docs/lua-records/index.rst
index 66d0b82876cafb03f0ec90d1d25db82e9882cc3c..109954ac61240cc463ba9ca1f2a166c7b7ea7892 100644 (file)
--- a/docs/lua-records/index.rst
+++ b/docs/lua-records/index.rst
@@ -198,7 +198,7 @@ Details & Security
 LUA records are synthesized on query. They can also be transferred via AXFR
 to other PowerDNS servers.
 
-LUA records themselves can not be queried however, as this would allow third parties to see load balancing internals
+LUA records themselves cannot be queried however, as this would allow third parties to see load balancing internals
 they do not need to see.
 
 A non-supporting DNS server will also serve a zone with LUA records, but

diff --git a/docs/modes-of-operation.rst b/docs/modes-of-operation.rst
index 3ba094f9b0d91ed24997afc3b50e82c0ca932f35..2406a0b90b9318ab9db4d5fa2de6787492ffd15b 100644 (file)
--- a/docs/modes-of-operation.rst
+++ b/docs/modes-of-operation.rst
@@ -200,7 +200,7 @@ Finally, IXFR updates that "plug" Empty Non-Terminals do not yet remove
 ENT records. A 'pdnsutil rectify-zone' may be required.
 
 PowerDNS itself is currently only able to retrieve updates via IXFR. It
-can not serve IXFR updates.
+cannot serve IXFR updates.
 
 .. _supermaster-operation:
 .. _autoprimary-operation:

diff --git a/docs/settings.rst b/docs/settings.rst
index d8bed0d47ce18a97cc100dd6b1a8bcc7299653f2..ef487677f2d40196c657561b2563e7d242d6bf68 100644 (file)
--- a/docs/settings.rst
+++ b/docs/settings.rst
@@ -1304,7 +1304,7 @@ If this is disabled (the default), ALIAS records are sent verbatim
 during outgoing AXFR. Note that if your slaves do not support ALIAS,
 they will return NODATA for A/AAAA queries for such names.
 
-If the ALIAS target can not be resolved during AXFR the AXFR will fail.
+If the ALIAS target cannot be resolved during AXFR the AXFR will fail.
 To allow outgoing AXFR also if the ALIAS targets are broken set this
 setting to `ignore-errors`.
 Be warned, this will lead to inconsistent zones between Primary and

diff --git a/pdns/recursordist/docs/changelog/4.1.rst b/pdns/recursordist/docs/changelog/4.1.rst
index 92d1b6a6f70651dbc703eafeebf7b39ee2eb1ce8..86e61c0145ac1f490543dce86723421bb21d3474 100644 (file)
--- a/pdns/recursordist/docs/changelog/4.1.rst
+++ b/pdns/recursordist/docs/changelog/4.1.rst
@@ -1341,7 +1341,7 @@ See :doc:`EOL Statements <../appendices/EOL>`.
     :tags: Bug Fixes
     :pullreq: 5209
 
-    Ensure locks can not be copied.
+    Ensure locks cannot be copied.
 
   .. change::
     :tags: Improvements, RPZ

diff --git a/pdns/recursordist/settings/table.py b/pdns/recursordist/settings/table.py
index e833fb6564065d3b3ea2472b20f5e98d9fd78e01..99b7e39ba6b1238dc4b39ba4af9b51556497bd42 100644 (file)
--- a/pdns/recursordist/settings/table.py
+++ b/pdns/recursordist/settings/table.py
@@ -502,7 +502,7 @@ In this case, ``dont-throttle-netmasks`` could be set to ``192.0.2.1``.
         'default' : 'false',
         'help' : 'Disable packetcache',
         'doc' : '''
-Turn off the packet cache. Useful when running with Lua scripts that can not be cached, though individual query caching can be controlled from Lua as well.
+Turn off the packet cache. Useful when running with Lua scripts that cannot be cached, though individual query caching can be controlled from Lua as well.
  ''',
     },
     {