Fix some spellings, ignore others.

Signed-off-by: Adam Warner <me@adamwarner.co.uk>

.codespellignore

@@ -0,0 +1,6 @@
+doubleclick
+Thur
+neet
+BRE
+WAN
+keep-alives

.github/workflows/codespell.yml

@@ -16,3 +16,4 @@ jobs:
       uses: codespell-project/actions-codespell@master
       with:
         ignore_words_file: .codespellignore
+        skip: ./docs/routers/fritzbox-de.md,./mkdocs.yml

docs/database/gravity/recovery.md

@@ -1,4 +1,4 @@
-If the `gravity.db` database has been damaged, Pi-hole offers two build-in attemps to repair the database.
+If the `gravity.db` database has been damaged, Pi-hole offers two built-in methods to repair the database.
 
 ## Recover
 

docs/ftldns/configfile.md

@@ -208,7 +208,7 @@ This setting can be used to disable ARP cache processing. When disabled, client
 
 #### `CHECK_LOAD=true|false` (PR [#1249](https://github.com/pi-hole/FTL/pull/1249)) {#check_load data-toc-label='Check system load'}
 
-Pi-hole is very lightweight on resources. Nevertheless, this does not mean that you should run Pi-hole on a server that is otherwise extremely busy as queuing on the system can lead to unecessary delays in DNS operation as the system becomes less and less usable as the system load increases because all resources are permanently in use. To account for this, FTL regularly checks the system load. To bring this to your attention, FTL warns about excessive load when the 15 minute system load average exceeds the number of cores.
+Pi-hole is very lightweight on resources. Nevertheless, this does not mean that you should run Pi-hole on a server that is otherwise extremely busy as queuing on the system can lead to unnecessary delays in DNS operation as the system becomes less and less usable as the system load increases because all resources are permanently in use. To account for this, FTL regularly checks the system load. To bring this to your attention, FTL warns about excessive load when the 15 minute system load average exceeds the number of cores.
 
 This check can be disabled with this setting.
 
@@ -222,7 +222,7 @@ By default, FTL warns if the shared-memory usage exceeds 90%. You can set any in
 
 FTL stores its long-term history in a database file on disk (see [here](../database/index.md)). Furthermore, FTL stores log files (see, e.g., [here](#file_LOGFILE)).
 
-By default, FTL warns if usage of the disk holding any crutial file exceeds 90%. You can set any integer limit between `0` to `100` (interpreted as percentages) where `0` means that checking of disk usage is disabled.
+By default, FTL warns if usage of the disk holding any crucial file exceeds 90%. You can set any integer limit between `0` to `100` (interpreted as percentages) where `0` means that checking of disk usage is disabled.
 
 ---
 

docs/ftldns/dnsmasq_warn.md

@@ -139,7 +139,7 @@ Warnings commonly seen in `dnsmasq`'s log file (`/var/log/pihole.log`) and the P
 
     `dnsmasq` can be configured to only accept queries from at-most-one-hop-away addresses using the option `local-service`. Other queries are discarded in this case.
 
-    This is ment to be a safe default to keep otherwise unconfigured installations safe. Note that `local-service` is ignored if *any* access-control config is in place (`interface`, `except-interface`, `listen-address` or `auth-server`).
+    This is meant to be a safe default to keep otherwise unconfigured installations safe. Note that `local-service` is ignored if *any* access-control config is in place (`interface`, `except-interface`, `listen-address` or `auth-server`).
 
 !!! warning "Maximum number of concurrent DNS queries reached (max: `NUMBER`)"
 
@@ -167,7 +167,7 @@ Warnings commonly seen in `dnsmasq`'s log file (`/var/log/pihole.log`) and the P
 
 !!! warning "overflow: `NUMBER` log entries lost"
 
-    When using asynchroneous logging and the disk is too slow, we can loose log lines during busy times. This can be avoided by decreasing the system load or switching to synchroneous logging. Note that synchroneous logging has the disadvantage of blocking DNS resolution when waiting for the log to be written to disk.
+    When using asynchronous logging and the disk is too slow, we can loose log lines during busy times. This can be avoided by decreasing the system load or switching to synchronous logging. Note that synchronous logging has the disadvantage of blocking DNS resolution when waiting for the log to be written to disk.
 
 !!! warning "failed to create listening socket for `ADDRESS`: `MSG`"
 

docs/guides/vpn/openvpn/client.ovpn

@@ -39,7 +39,7 @@ nobind
 persist-key
 persist-tun
 
-# SSL/TLS parms.
+# SSL/TLS params.
 # See the server config file for more
 # description.  It's best to use
 # a separate .crt/.key file pair

docs/main/faq.md

@@ -14,7 +14,7 @@ nskywzjbpj
 
 **Solution:**
 
-This happens when using Chrome-based browsers. Chrome tries to find out if someone is messing up with the DNS (i.e. wildcard DNS servers to catch all domains). Chrome does this by issuing DNS requests to randomly generated domain names with bewteen 7 and 15 characters
+This happens when using Chrome-based browsers. Chrome tries to find out if someone is messing up with the DNS (i.e. wildcard DNS servers to catch all domains). Chrome does this by issuing DNS requests to randomly generated domain names with between 7 and 15 characters
 
 In a normal setup this results in a “No such name” response from your DNS server. If the DNS server you use has a wildcard setup, each of these requests will result in a response (which is normally even the same) so Chrome knows that there is someone messing around with DNS responses.
 
@@ -79,7 +79,7 @@ The amount of memory needed depends on many factors:
 - other processes running on your device,
 - the amount of data you want to process.
 
-One aproach would be to increase the limit by 128M and check if it was enough to retrieve the data.
+One approach would be to increase the limit by 128M and check if it was enough to retrieve the data.
 If not, add another 128M, check again. If not, add another 128M, check again, until you find the best value.
 
 _Note:_

docs/main/prerequisites.md

@@ -40,7 +40,7 @@ The following operating systems are **officially** supported:
     [✗] Unsupported OS detected: Debian 16
       If you are seeing this message and you do have a supported OS, please contact support.
 
-      https://docs.pi-hole.net/main/prerequesites/#supported-operating-systems
+      https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems
 
       If you wish to attempt to continue anyway, you can try one of the following commands to skip this check:
 

docs/routers/fritzbox.md

@@ -26,7 +26,7 @@ The Fritz!Box can be Pi-hole's upstream DNS server, as long Pi-hole itself is no
 To set it up, enter Pi-hole's IP as "Local DNS server" in
 
 ```bash
-Home Network/Network/Network Settings/IP Adresses/IPv4 Configuration/Home Network
+Home Network/Network/Network Settings/IP Addresses/IPv4 Configuration/Home Network
 ```
 
 ![Screenshot of Fritz!Box DHCP Settings](../images/fritzbox-dhcp.png)
@@ -63,7 +63,7 @@ If only this configuration is used, you won't see individual clients in Pi-hole'
 There is no option to set the DNS server for the guest network in
 
 ```bash
-Home Network/Network/Network Settings/IP Adresses/IPv4 Configuration/Guest Network
+Home Network/Network/Network Settings/IP Addresses/IPv4 Configuration/Guest Network
 ```
 
 The Fritz!Box always sets its own IP as DNS server for the guest network. To filter its traffic, you have to setup Pi-hole as upstream DNS server for your Fritz!Box. As there is no other option, all DNS requests from your guest network will appear as coming from your Fritz!Box. Individual filtering per client within the guest network is therefore not possible.