diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 509a22c8f..3a7df08db 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Vyznačuje se těmito vlastnostmi:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Přípustné hodnoty:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Vyznačuje se těmito vlastnostmi:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index e8e978caf..c08b73ce7 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ Pokud se tlačítko nezobrazí nebo se automatická aktualizace nezdařila, mů
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Rozbalte archiv AdGuard Home do dočasného adresáře. Pokud jste například stáhli archiv do adresáře `~/Downloads` a chcete jej rozbalit do adresáře `/tmp/`:
+5. Rozbalte archiv AdGuard Home do dočasného adresáře. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    V macOS zadejte něco jako:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Nahraďte starý spustitelný soubor AdGuard Home novým. Ve většině unixových systémů by měl příkaz vypadal takto:
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 5726d8885..f90b4c5d2 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-Chcete-li získat přístup k tomuto koncovému bodu, musíte nás kontaktovat na **devteam@adguard.com**. Popište prosím důvod a případy použití tohoto koncového bodu a uveďte URI přesměrování. Po schválení obdržíte jedinečný identifikátor klienta, který by měl být použit pro parametr **client_id**.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Popište prosím důvod a případy použití tohoto koncového bodu a uveďte URI přesměrování. Po schválení obdržíte jedinečný identifikátor klienta, který by měl být použit pro parametr **client_id**.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-Chcete-li získat přístup k tomuto koncovému bodu, musíte nás kontaktovat na **devteam@adguard.com**. Ve své zprávě prosím popište důvod a příklady použití tohoto koncového bodu a uveďte přesměrovací URI. Po schválení obdržíte jedinečný identifikátor klienta, který budete používat v parametru **client_id**.
+To access this endpoint, please contact us at **b2b@adguard.com**. Ve své zprávě prosím popište důvod a příklady použití tohoto koncového bodu a uveďte přesměrovací URI. Po schválení obdržíte jedinečný identifikátor klienta, který budete používat v parametru **client_id**.
 
 :::
 
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 89b122b6e..846bcb23e 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Odkaz
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 66a4aaf0f..c1ec3b18d 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -81,80 +81,80 @@ AdGuard Home er dybest set en DNS-proxy, der sender DNS-forespørgsler til upstr
 
 - `tcp://dns-unfiltered.adguard.com`: Almindelig DNS (over TCP, værtsnavn).
 
-- `tls://dns-unfiltered.adguard.com`: Encrypted [DNS-over-TLS].
+- `tls://dns-unfiltered.adguard.com`: Krypteret [DNS-over-TLS].
 
-- `https://dns-unfiltered.adguard.com/dns-query`: Encrypted [DNS-over-HTTPS].
+- `https://dns-unfiltered.adguard.com/dns-query`: Krypteret [DNS-over-HTTPS].
 
-- `h3://dns-unfiltered.adguard.com/dns-query`: Encrypted [DNS-over-HTTPS] with forced [HTTP/3] and no fallback to HTTP/2 and below.
+- `h3://dns-unfiltered.adguard.com/dns-query`: Krypteret [DNS-over-HTTPS] med tvungen [HTTP/3] og ingen HTTP/2-reserve eller lavere.
 
-- `quic://dns-unfiltered.adguard.com`: Encrypted [DNS-over-QUIC].
+- `quic://dns-unfiltered.adguard.com`: Krypteret [DNS-over-QUIC].
 
-- `sdns://...`: [DNS Stamps] for [DNSCrypt] or [DNS-over-HTTPS] resolvers.
+- `sdns://...`: \[DNS-stempler] til [DNSCrypt]- eller [DNS-over-HTTPS]-opløsere.
 
-- `[/example.local/]94.140.14.140`: DNS upstream for specific domains, see below.
+- `[/example.local/]94.140.14.140`: DNS-upstream for specifikke domæner, se nedenfor.
 
-- `[/*.example.local/]94.140.14.140`: DNS upstream for specific subdomains, see below.
+- `[/*.example.local/]94.140.14.140`: DNS-upstream for specifikke underdomains, se nedenfor.
 
-### Specifying upstreams for domains {#upstreams-for-domains}
+### Angivelse af upstreams for domæner {#upstreams-for-domains}
 
-You can specify upstreams that will be used for specific domains using the dnsmasq-like syntax (see the documentation for the option `--server` [here][dnsmasq-man]). This feature is intended for private nameservers which deal with intranet domains.
+Der kan angives upstreams til brug for specifikke domæner vha. den dnsmasq-lignende syntaks (se dokumentationen for indstillingen `--server` [her][dnsmasq-man]). Denne funktion er beregnet til private navneservere, som håndterer intranetdomæner.
 
 Syntaksen er:
 
 ```none
-[/domain1/domain2/domainN/]<upstreamString>
+[/domæne1/domæne2/domæneN/]<upstreamString>
 ```
 
-Where `upstreamString` is one or more upstreams separated by space (e.g. `1.1.1.1 2.2.2.2`).
+Hvor `upstreamString` er en eller flere upstreams adskilt af mellemrum (f.eks. `1.1.1.1 2.2.2.2`).
 
-If one or more domains are specified, that upstream (here `upstreamString`) is used only for those domains. Usually, it is used for private nameservers. For instance, if you have a nameserver on your network which deals with `xxx.internal.local` at address `192.168.0.1` then you can specify `[/internal.local/]192.168.0.1`, and AdGuard Home will send all `*.internal.local` queries to that nameserver. Everything else will be sent to the default upstreams, which should be specified as well.
+Er et eller flere domæner angivet, benyttes denne upstream (her `upstreamString`) kun til disse domæner. Normalt bruges den til private navneservere. Findes f.eks. en navneserver på netværket, der håndterer `xxx.internal.local` på adressen `192.168.0.1`, så kan der angives `[/internal.local/]192.168.0.1`, og AdGuard Home vil sende alle `*.internal.local`-forespørgsler til den navneserver. Alt andet vil blive sendt til standard-upstreams, som også skal angives.
 
-An empty domain specification, `//` has the special meaning of “unqualified names only”, i.e. names without any dots in them, like `myhost` or `router`. Those will only be used for resolving requests for unqualified domain names, but not their subdomains. So, a configuration like this:
+En tom domænespecifikation, `//` har den særlige betydning "kun ukvalificerede navne", dvs. navne uden nogen punktummer i dem, såsom `myhost` eller `router`. Disse vil kun blive brugt til at opløse forespørgsler for ukvalificerede domænenavne, men ikke deres underdomæner. Så en opsætning som denne:
 
 ```none
 5.6.7.8:53
 [//]4.3.2.1:53 [/com/]1.2.3.4:53
 ```
 
-sends requests for `com` (and its subdomains) to `1.2.3.4:53`, requests for other top-level domains to `4.3.2.1:53`, and all other requests to `5.6.7.8:53`.
+sender forespørgsler for `com` (og dets underdomæner) til `1.2.3.4:53`, forespørgsler for andre topdomæner til `4.3.2.1:53` og alle øvrige forespørgsler til `5.6.7.8:53`.
 
-More specific domains take precedence over less specific domains. So, a configuration like this:
+Mere specifikke domæner har forrang over mindre specifikke domæner. Så en opsætning som denne:
 
 ```none
 [/host.com/]1.2.3.4 [/www.host.com/]2.3.4.5
 ```
 
-sends queries for `*.host.com` to `1.2.3.4`, except for queries for `*.www.host.com`, which are sent to `2.3.4.5`.
+sender forespørgsler for `*.host.com` til `1.2.3.4`, undtagen forespørgsler for `*.www.host.com`, som sendes til `2.3.4.5`.
 
-The special server address `#` means “use the default servers”. So, a configuration like this:
+Den særlige serveradresse `#` betyder "brug standardserverne". Så en opsætning som denne:
 
 ```none
 6.7.8.9
 [/host.com/]1.2.3.4 [/www.host.com/]#
 ```
 
-sends queries for `*.host.com` to `1.2.3.4` except for queries for `*.www.host.com`, which are sent to `6.7.8.9`, which is the default upstream.
+sender forespørgsler for `*.host.com` til `1.2.3.4`, undtagen forespørgsler for `*.www.host.com`, som sendes til `6.7.8.9`, som er standard-upstream.
 
-Queries for the `DS` query type are following the assumption based on specification for records’ presence given in [RFC 4035, section 2.4](https://datatracker.ietf.org/doc/html/rfc4035#section-2.4):
+Forespørgsler for forespørgselstypen `DS` følger antagelsen baseret på specifikationen for posters tilstedeværelse angivet i [RFC 4035, afsnit 2.4](https://datatracker.ietf.org/doc/html/rfc4035#section-2.4):
 
-> A DS RRset SHOULD be present at a delegation point when the child zone is signed. \[…\] All DS RRsets in a zone MUST be signed, and DS RRsets MUST NOT appear at a zone’s apex.
+> Et DS RRset BØR være til stede ved et delegeringspunkt, når underzonen signeres. \[…\] Alle DS RRsets i en zone SKAL signeres, og DS RRsets MÅ IKKE vises ved et roddomæne.
 
-For example, the `DS` query for `domain.example.com` will be sent to the upstream specified for `example.com`, `com`, or the default one, even if there is a more specific upstream like `*.example.com`. Note that for two-label `DS` requests, the upstream specified for unqualified names, or the more specific one will be used, if any.
+En `DS`-forespørgsel for `domain.example.com` vil f.eks. blive sendt til den upstream, der er angivet for `example.com`, `com` eller standard-upstreamen, selvom der er en mere specifik upstream, såsom `*.example.com`. Bemærk, at for `DS`-forespørgsler med to navneelementer vil den upstream, der er angivet for ukvalificerede navne, eller den mere specifikke blive brugt, hvis nogen findes.
 
-Wildcard `*` has a special meaning of “any subdomain”, so `--upstream=[/*.host.com/]1.2.3.4` will send queries for `*.host.com` to `1.2.3.4`, but `host.com` will be forwarded to default upstreams.
+Jokertegnet `*` har en særlig betydning for "ethvert underdomæne", så `--upstream=[/*.host.com/]1.2.3.4` vil sende forespørgsler for `*.host.com` til `1.2.3.4`, men `host.com` videresendes til standard upstreams.
 
-**Examples:**
+**Eksempler:**
 
-- A configuration like:
+- En opsætning såsom:
 
     ```none
     8.8.8.8:53
     [/local/]192.168.0.1:53
     ```
 
-  sends queries for `*.local` domains to `192.168.0.1:53`. Other queries are sent to `8.8.8.8:53`.
+  sender forespørgsler for `*.local`-domæner til `192.168.0.1:53`. Øvrige forespørgsler sendes til `8.8.8.8:53`.
 
-- A configuration like:
+- En opsætning såsom:
 
     ```none
     8.8.8.8:53
@@ -162,9 +162,9 @@ Wildcard `*` has a special meaning of “any subdomain”, so `--upstream=[/*.ho
     [/maps.host.com/]#
     ```
 
-  sends queries for `*.host.com` to `1.1.1.1:53` except for `*.maps.host.com` which are sent to `8.8.8.8:53` along with all other queries.
+  sender forespørgsler for `*.host.com` til `1.1.1.1:53`, undtagen `*.maps.host.com`, der sendes til `8.8.8.8:53` sammen med alle øvrige forespørgsler.
 
-- A configuration like:
+- En opsætning såsom:
 
     ```none
     8.8.8.8:53
@@ -172,9 +172,9 @@ Wildcard `*` has a special meaning of “any subdomain”, so `--upstream=[/*.ho
     [/*.host.com/]2.2.2.2:53
     ```
 
-  sends queries for `*.host.com` to `2.2.2.2:53` except for `host.com` queries, those are sent to `1.1.1.1:53`, but all other queries are sent to `8.8.8.8:53`.
+  sender forespørgsler for `*.host.com` til `2.2.2.2:53`, undtagen `host.com`-forespørgsler, som sendes til `1.1.1.1:53`, men alle øvrige forespørgsler sendes til `8.8.8.8:53`.
 
-- A configuration like:
+- En opsætning såsom:
 
     ```none
     8.8.8.8:53
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Den har flg. egenskaber:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: Liste over upstream-DNS-servere.  Kommentarer (linjer startende med `#`) og tomme linjer ignoreres.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Kommentarer (linjer startende med `#`) og tomme linjer ignoreres.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Kommentarer (linjer startende med `#`) og tomme linjer ignoreres.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Kommentarer (linjer startende med `#`) og tomme linjer ignoreres.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Gyldige værdier:
 
@@ -436,7 +436,7 @@ The `dns` object configures the DNS server. Den har flg. egenskaber:
 
 - `disallowed_clients`: The list of CIDRs, IP addresses, or ClientIDs of disallowed DNS clients. If this list has entries, AdGuard Home will drop requests from these clients. Note that this field is ignored if there are entries in `allowed_clients`.
 
-  See also the note in the [Docker wiki page][docker-conf] about using this property within a container.
+  Se også noten på [Docker-wikisiden][docker-conf] om brug af denne egenskab i en container.
 
 - `blocked_hosts`: The list of domain names, wildcards or filtering rules to match requests that shouldn't be processed at all. These are ignored by statistics and query log as well.
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Den har flg. egenskaber:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index d67209fef..560c4713c 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ Hvis knappen ikke vises, eller en automatisk opdatering mislykkedes, kan opdater
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Udpak AdGuard Home-arkivet til en midlertidig mappe. Downloades arkivet til `~/Downloads`-mappen, så udpak det f.eks. til `/tmp/`:
+5. Udpak AdGuard Home-arkivet til en midlertidig mappe. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    På macOS, skriv noget i stil med:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Erstat den gamle AdGuard Home eksekverbare fil med den nye. På de fleste Unix-systemer vil kommandoen se således ud:
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index ac3d834fe..f00b048c9 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-For at tilgå dette endepunkt, kontakt os via **devteam@adguard.com**. Beskriv venligst årsagen til og brugstilfælde for dette endepunkt, samt angiv omdirigerings-URI'en. Efter godkendelse fremsendes en unik klientidentifikator til brug for parameteren **client_id**.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Beskriv venligst årsagen til og brugstilfælde for dette endepunkt, samt angiv omdirigerings-URI'en. Efter godkendelse fremsendes en unik klientidentifikator til brug for parameteren **client_id**.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-For at tilgå dette endepunkt, kontakt os venligst via **devteam@adguard.com**. Beskeden bedes beskrive årsagen til og anvendelsestilfældene for dette endepunkt samt angive omdirigerings-URI'en. Efter godkendelsen modtages en unik klientidentifikator til brug i parameteren **client_id**.
+To access this endpoint, please contact us at **b2b@adguard.com**. Beskeden bedes beskrive årsagen til og anvendelsestilfældene for dette endepunkt samt angive omdirigerings-URI'en. Efter godkendelsen modtages en unik klientidentifikator til brug i parameteren **client_id**.
 
 :::
 
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..2fafc6cc4 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/da/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -1,14 +1,15 @@
 ---
 title: Reference
 sidebar_position: 2
-description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+description: Autogenereret API-reference til AdGuard DNS' offentlige API, gengivet live fra OpenAPI-specifikationen.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
 
-This reference is generated automatically from the live
-[OpenAPI specification](https://adguard-dns.io/api/swagger/openapi.json).
-For authentication, see the [Overview](private-dns/api/overview.md); for changes,
-see the [Changelog](private-dns/api/changelog.md).
+Denne reference genereres automatisk fra den live
+[OpenAPI-specifikation](https://adguard-dns.io/api/swagger/openapi.json).
+For autentificering, se [Oversigt](private-dns/api/overview.md); for ændringer,
+se [Ændringslog](private-dns/api/changelog.md).
 
 <OpenApiReference />
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index d6cb8df5c..fd5e91b97 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -99,7 +99,7 @@ AdGuard Home is basically a DNS proxy that sends your DNS queries to upstream se
 
 You can specify upstreams that will be used for specific domains using the dnsmasq-like syntax (see the documentation for the option `--server` [here][dnsmasq-man]). This feature is intended for private nameservers which deal with intranet domains.
 
-The syntax is:
+Die Syntax lautet:
 
 ```none
 [/domain1/domain2/domainN/]<upstreamString>
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Es hat folgende Eigenschaften:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Mögliche Werte:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Es hat folgende Eigenschaften:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 8f7a71384..5412d9cc1 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ Wenn die Schaltfläche nicht angezeigt wird oder eine automatische Aktualisierun
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Entpacken Sie das AdGuard Home-Archiv in einen temporären Ordner. Wenn Sie zum Beispiel das Archiv in den Ordner `~/Downloads` heruntergeladen haben und es nach `/tmp/` entpacken wollen:
+5. Entpacken Sie das AdGuard Home-Archiv in einen temporären Ordner. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    Unter macOS geben Sie etwas ein wie:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Ersetzen Sie die alte ausführbare Datei von AdGuard Home durch die neue. Auf den meisten Unix-Systemen würde der Befehl etwa so aussehen:
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md b/i18n/de/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
index e2094e9d2..0460e92e6 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
@@ -19,13 +19,13 @@ Sie können die Syntax der AdGuard DNS-Filterregeln verwenden, um die Regeln fle
 
 Es gibt drei verschiedene Ansätze für die Erstellung von Hosts-Sperrlisten:
 
-- [Adblock-style syntax][]: the modern approach to writing filtering rules based on using a subset of the Adblock-style rule syntax. Auf diese Weise sind die Blocklisten mit den Werbeblockern der Browser kompatibel.
+- [Adblock-Syntax][]: der moderne Ansatz zum Schreiben von Filterregeln, der auf der Verwendung einer Untermenge der Adblock-Syntax basiert. Auf diese Weise sind die Blocklisten mit den Werbeblockern der Browser kompatibel.
 
 - [`/etc/hosts` syntax](#etc-hosts-syntax): Der alte, bewährte Ansatz, der die gleiche Syntax verwendet, die auch die Betriebssysteme für ihre hosts-Dateien verwenden.
 
 - [Domains-only-Syntax](#domains-only-syntax): eine einfache Liste von Domainnamen.
 
-If you are creating a blocklist, we recommend using the [Adblock-style syntax][]. Sie hat eine Reihe wichtiger Vorteile gegenüber der alten Syntax:
+Wenn Sie eine Blockliste erstellen, empfehlen wir die Verwendung der [Adblock-Stil-Syntax][]. Sie hat eine Reihe wichtiger Vorteile gegenüber der alten Syntax:
 
 - **Größe der Sperrlisten.** Durch die Verwendung des Musterabgleichs können Sie eine einzige Regel anstelle von Hunderten von `/etc/hosts` Einträgen verwenden.
 
@@ -33,7 +33,7 @@ If you are creating a blocklist, we recommend using the [Adblock-style syntax][]
 
 - **Erweiterbarkeit.** In den letzten zehn Jahren hat sich die Adblock-Syntax stark weiterentwickelt, und wir sehen keinen Grund, sie nicht noch weiter zu erweitern und zusätzliche Funktionen für Blocker auf Netzwerkebene anzubieten.
 
-If you’re maintaining either a `/etc/hosts`-style blocklist or multiple filtering lists (regardless of type), we provide a tool for blocklist compilation. We named it [Hostlist compiler][] and we use it ourselves to create [AdGuard DNS filter][].
+Wenn Sie entweder eine Blockliste im Stil von `/etc/hosts` oder mehrere Filterlisten (unabhängig vom Typ) verwalten, bieten wir ein Werkzeug zur Zusammenstellung von Blocklisten. Wir haben es [Hostlist compiler][] genannt und wir verwenden es selbst, um den [AdGuard DNS filter][] zu erstellen.
 
 ## Allgemeine Beispiele {#basic-examples}
 
@@ -60,7 +60,7 @@ If you’re maintaining either a `/etc/hosts`-style blocklist or multiple filter
 
 ## Syntax im Adblock-Stil {#adblock-style-syntax}
 
-This is a subset of the [traditional Adblock-style syntax][] which is used by browser ad blockers.
+Dies ist eine Teilmenge der [traditionellen Adblock-Syntax][], die von den Werbeblockern der Browser verwendet wird.
 
 ```none
      Regel = ["@@"] pattern [ "$" modifiers ]
@@ -79,13 +79,13 @@ Modifikator = [modifier0, modifier1[, ...[, modifierN]]]
 
 - `||`: stimmt mit dem Anfang eines Hostnamens überein, einschließlich aller Subdomains. Zum Beispiel stimmt `||example.org` mit `example.org` und `test.example.org` überein, aber nicht mit `testexample.org`.
 
-- `^`: das Trennzeichen. Unlike browser ad blocking, there’s nothing to separate in a hostname, so the only purpose of this character is to mark the end of the hostname.
+- `^`: das Trennzeichen. Anders als bei der Werbeblockierung in Browsern gibt es in einem Hostnamen nichts zu trennen, so dass der einzige Zweck dieses Zeichens darin besteht, das Ende des Hostnamens zu markieren.
 
 - `|`: ein Zeiger auf den Anfang oder das Ende des Hostnamens. Der Wert hängt von der Platzierung des Zeichens in der Maske ab. Die Regel `ample.org|` entspricht zum Beispiel `example.org`, aber nicht `example.org.com`. `|example` entspricht `example.org` aber nicht `test.example`.
 
 ### Reguläre Ausdrücke {#regular-expressions}
 
-If you want even more flexibility in making rules, you can use [regular expressions][regexp] instead of the default simplified matching syntax. Wenn Sie einen regulären Ausdruck verwenden wollen, muss das Muster wie folgt aussehen:
+Wenn Sie bei der Erstellung von Regeln noch flexibler sein wollen, können Sie [reguläre Ausdrücke][regexp] anstelle der standardmäßigen vereinfachten Syntax verwenden. Wenn Sie einen regulären Ausdruck verwenden wollen, muss das Muster wie folgt aussehen:
 
 ```none
 pattern = "/" regexp "/"
@@ -125,11 +125,11 @@ Sie können das Verhalten einer Regel ändern, indem Sie Modifikatoren hinzufüg
   ||example.org^$client=127.0.0.1,dnstype=A
   ```
 
-  `||example.org^` ist das passende Muster. `$` ist das Trennzeichen, das signalisiert, dass der Rest der Regel Modifikatoren sind. `client=127.0.0.1` is the [`client`][] modifier with its value, `127.0.0.1`. `,` (Komma) ist das Trennzeichen zwischen den Modifikatoren. And finally, `dnstype=A` is the [`dnstype`][] modifier with its value, `A`.
+  `||example.org^` ist das passende Muster. `$` ist das Trennzeichen, das signalisiert, dass der Rest der Regel Modifikatoren sind. `client=127.0.0.1` ist der [client</code>-][]Modifikator mit seinem Wert `127.0.0.1`. `,` (Komma) ist das Trennzeichen zwischen den Modifikatoren. Und schließlich ist `dnstype=A` der [`dnstype`][]-Modifikator mit seinem Wert, `A`.
 
 :::note
 
-If a rule contains a modifier not listed in this document, the whole rule **must be ignored**. This way we avoid false-positives when people are trying to use unmodified browser ad blockers’ filter lists like EasyList or EasyPrivacy.
+Wenn eine Regel einen Modifikator enthält, der nicht in diesem Dokument aufgeführt ist, wird die gesamte Regel **nicht berücksichtigt**. Auf diese Weise werden Fehlalarme vermieden, wenn Nutzer versuchen, unveränderte Filterlisten von Browser-Werbeblockern wie EasyList oder EasyPrivacy zu verwenden.
 
 :::
 
@@ -137,11 +137,11 @@ If a rule contains a modifier not listed in this document, the whole rule **must
 
 :::note
 
-The `client` modifier can only be used in AdGuard Home and AdGuard DNS.
+Der Modifikator `client` kann nur in AdGuard Home und AdGuard DNS verwendet werden.
 
 :::
 
-The `client` modifier allows specifying clients this rule is applied to. There are two main ways to identify a client:
+Der Modifikator `client` ermöglicht die Angabe von Clients, auf die diese Regel angewendet werden soll. Es gibt zwei Hauptmethoden, um einen Client zu identifizieren:
 
 - Durch ihre IP-Adresse oder ihr CIDR-Präfix. Dies funktioniert für alle Arten von Clients.
 
@@ -149,27 +149,27 @@ The `client` modifier allows specifying clients this rule is applied to. There a
 
   :::note
 
-  In AdGuard Home, ClientIDs are not currently supported, only names are. If you have added a client with the name “My Client” and ClientID `my-client` spell your modifier as `$client='My Client'` as opposed to `$client=my-client`.
+  In AdGuard Home werden derzeit keine Client-IDs unterstützt, sondern nur Namen. Wenn Sie einen Client mit dem Namen „Mein Client” und der „ClientID” `mein-client` hinzugefügt haben, benennen Sie ihren Modifikator mit „`$client='Mein Client'`” anstelle von „`$client=mein-client`”.
 
   :::
 
-The syntax is:
+Die Syntax lautet:
 
 ```none
 $client=value1|value2|...
 ```
 
-You can also exclude clients by adding a `~` character before the value. In this case, the rule is not be applied to this client’s DNS requests.
+Sie können auch Clients ausschließen, indem Sie `~` vor dem Wert einfügen. In diesem Fall wird die Regel nicht auf die DNS-Anfragen dieses Clients angewendet.
 
 ```none
 $client=~value1
 ```
 
-Client names usually contain spaces or other special characters, which is why you should enclose the name in quotes. Both single and double ASCII quotes are supported. Use the backslash (`\`) to escape quotes (`"` and `'`), commas (`,`), and pipes (`|`).
+Client-Namen enthalten in der Regel Leerzeichen oder andere Sonderzeichen, weshalb Sie den Namen in Anführungszeichen setzen sollten. Sowohl einfache als auch doppelte ASCII-Anführungszeichen werden unterstützt. Verwenden Sie den Backslash (`\`), um Anführungszeichen (`"` und `'`), Kommata (`,`) und Pipes (`|`) zu vermeiden.
 
 :::note
 
-When excluding a client, you **must** place `~` outside the quotes.
+Wenn Sie einen Client ausschließen, **müssen** Sie `~` außerhalb der Anführungszeichen platzieren.
 
 :::
 
@@ -187,15 +187,15 @@ When excluding a client, you **must** place `~` outside the quotes.
 
 #### `denyallow` {#denyallow-modifier}
 
-You can use the `denyallow` modifier to exclude domains from the blocking rule. To add multiple domains to one rule, use the `|` character as a separator.
+Sie können den `denyallow`-Modifikator verwenden, um Domänen von der Blockierungsregel auszuschließen. Um mehrere Domains zu einer Regel hinzuzufügen, verwenden Sie das Pipe-Zeichen `|` als Trennzeichen.
 
-The syntax is:
+Die Syntax lautet:
 
 ```none
 $denyallow=domain1|domain2|...
 ```
 
-This modifier allows avoiding creating unnecessary exception rules when our blocking rule covers too many domains. You may want to block everything except for a couple of TLD domains. You could use the standard approach, i.e. rules like this:
+Dieser Modifikator ermöglicht es, unnötige Ausnahmeregeln zu vermeiden, wenn unsere Blockierungsregel zu viele Domains abdeckt. Möglicherweise möchten Sie alles außer einigen TLD-Domains blockieren. Sie könnten den Standardansatz verwenden, d. h. Regeln wie diese:
 
 ```none
 ! Alles blockieren.
@@ -206,7 +206,7 @@ This modifier allows avoiding creating unnecessary exception rules when our bloc
 @@||net^
 ```
 
-The problem with this approach is that this way you will also unblock tracking domains that are located on those TLDs (i.e. `google-analytics.com`). Here’s how to solve this with `denyallow`:
+Das Problem bei diesem Ansatz ist, dass Sie auf diese Weise auch Tracking-Domains freigeben, die sich auf diesen TLDs befinden (z. B. `google-analytics.com`). So lösen Sie dieses Problem mit `denyallow`:
 
 ```none
 *$denyallow=com|net
@@ -218,28 +218,28 @@ The problem with this approach is that this way you will also unblock tracking d
 
 - `@@*$denyallow=com|net`: entsperrt alles außer `*.com` und `*.net`.
 
-- `||example.org^$denyallow=sub.example.org`: block `example.org` and `*.example.org`, but not `sub.example.org`.
+- `||example.org^$denyallow=sub.example.org`: blockiert `example.org` und `*.example.org`, aber nicht `sub.example.org`.
 
 #### `dnstype` {#dnstype-modifier}
 
-The `dnstype` modifier allows specifying DNS request or response type on which this rule will be triggered.
+Mit dem Modifikator `dnstype` kann der Typ der DNS-Anfrage oder -Antwort angegeben werden, bei dem diese Regel ausgelöst wird.
 
-The syntax is:
+Die Syntax lautet:
 
 ```none
 $dnstype=value1|value2|...
 $dnstype=~value1|~value2|~...
 ```
 
-The names of the types are case-insensitive, but are validated against a set of actual DNS resource record (RR) types.
+Die Namen der Typen sind unabhängig von Groß- und Kleinschreibung, werden jedoch anhand einer Menge tatsächlicher DNS-Resource-Record-(RR)-Typen validiert.
 
-Do not combine exclusion rules with inclusion ones. This:
+Kombinieren Sie keine Ausschlussregeln mit Einschlussregeln. Dies:
 
 ```none
 $dnstype=~value1|value2
 ```
 
-is equivalent to this:
+ist gleichbedeutend mit diesem:
 
 ```none
 $dnstype=value2
@@ -253,7 +253,7 @@ $dnstype=value2
 
 :::note
 
-Before version **v0.108.0,** AdGuard Home would use the type of the request to filter the response records, as opposed to the type of the response record itself.  That caused issues, since that meant that you could not write rules that would allow certain `CNAME` records in responses in `A` and `AAAA` requests. In **v0.108.0** that behaviour was changed, so now this:
+Vor Version **v0.108.0** verwendete AdGuard Home den Typ der Anfrage, um die Antwortdatensätze zu filtern, im Gegensatz zum Typ des Antwortdatensatzes selbst.  Das führte zu Problemen, da dies bedeutete, dass man keine Regeln schreiben konnte, die bestimmte `CNAME`-Datensätze in Antworten auf `A`- und `AAAA`-Anfragen zuließen. In **v0.108.0** wurde dieses Verhalten geändert, so dass jetzt dieses:
 
 :::
 
@@ -261,7 +261,7 @@ Before version **v0.108.0,** AdGuard Home would use the type of the request to f
 ||canon.example.com^$dnstype=~CNAME
 ```
 
-allows you to avoid filtering of the following response:
+erlaubt es, die Filterung der folgenden Antwort zu vermeiden:
 
 ```none
 ANSWERS:
@@ -275,17 +275,17 @@ ANSWERS:
 
 #### `dnsrewrite` {#dnsrewrite-modifier}
 
-The `dnsrewrite` response modifier allows replacing the content of the response to the DNS request for the matching hosts. Note that this modifier in AdGuard Home works in all rules, but in Private AdGuard DNS — only in custom ones.
+Der `dnsrewrite`-Antwortmodifikator erlaubt es, den Inhalt der Antwort auf die DNS-Anfrage für die entsprechenden Hosts zu ersetzen. Beachten Sie, dass dieser Modifikator in AdGuard Home in allen Regeln funktioniert, in Private AdGuard DNS jedoch nur in benutzerdefinierten Regeln.
 
 :::note
 
-Rules with the `dnsrewrite` response modifier have higher priority than other rules in AdGuard Home and AdGuard DNS.
+Regeln mit dem Antwortmodifikator `dnsrewrite` haben eine höhere Priorität als andere Regeln in AdGuard Home.
 
 :::
 
-Responses to all requests for a host matching a `dnsrewrite` rule will be replaced. The answer section of the replacement response will only contain RRs that match the request’s query type and, possibly, CNAME RRs. Note that this means that responses to some requests may become empty (`NODATA`) if the host matches a `dnsrewrite` rule.
+Die Antworten auf alle Anfragen nach einem Host, der einer `dnsrewrite`-Regel entspricht, werden ersetzt. Der Antwortabschnitt der Ersatzantwort enthält nur RRs, die dem Abfragetyp der Anfrage entsprechen, und möglicherweise CNAME-RRs. Beachten Sie, dass dies bedeutet, dass Antworten auf einige Anfragen leer sein können (`NODATA`), wenn der Host einer `dnsrewrite`-Regel entspricht.
 
-The shorthand syntax is:
+Die Kurzsyntax lautet:
 
 ```none
 $dnsrewrite=1.2.3.4
@@ -294,9 +294,9 @@ $dnsrewrite=example.net
 $dnsrewrite=REFUSED
 ```
 
-The keywords MUST be in all caps (e.g. `NOERROR`). Keyword rewrites take precedence over the other and will result in an empty response with an appropriate response code.
+Die Schlüsselwörter MÜSSEN in Großbuchstaben geschrieben werden (z.B. `NOERROR`). Keyword-Rewrites haben Vorrang vor anderen und führen zu einer leeren Antwort mit einem entsprechenden Antwortcode.
 
-The full syntax is of the form `RCODE;RRTYPE;VALUE`:
+Die vollständige Syntax hat die Form `RCODE;RRTYPE;VALUE`:
 
 ```none
 $dnsrewrite=NOERROR;A;1.2.3.4
@@ -305,9 +305,9 @@ $dnsrewrite=NOERROR;CNAME;example.net
 $dnsrewrite=REFUSED;;
 ```
 
-The `$dnsrewrite` modifier with the `NOERROR` response code may also has empty `RRTYPE` and `VALUE` fields.
+Die `$dnsrewrite` Modifikator mit dem `NOERROR` Der Antwortcode kann ebenfalls leer sein `RRTYPE` und `WERT` Felder.
 
-The `CNAME` one is special because AdGuard Home will resolve the host and add its info to the response. That is, if `example.net` has IP `1.2.3.4`, and the user has this in their filter rules:
+Der `CNAME` ist besonders, weil AdGuard Home den Host auflöst und seine Informationen in die Antwort einfügt. Das heißt, wenn `example.net` die IP `1.2.3.4`hat, und der Benutzer dies in seinen Filterregeln hat:
 
 ```none
 ||example.com^$dnsrewrite=example.net
@@ -315,7 +315,7 @@ The `CNAME` one is special because AdGuard Home will resolve the host and add it
 ||example.com^$dnsrewrite=NOERROR;CNAME;example.net
 ```
 
-then the response will be something like:
+dann lautet die Antwort etwa so:
 
 ```sh
 nslookup example.com my.adguard.local
@@ -331,22 +331,22 @@ Name: example.net
 Adresse: 1.2.3.4
 ```
 
-Next, the `CNAME` rewrite. After that, all other records’ values are summed as one response, so this:
+Als nächstes wird der `CNAME` umgeschrieben. Danach werden alle Werte der anderen Datensätze zu einer Antwort zusammengefasst, also so:
 
 ```none
 ||example.com^$dnsrewrite=NOERROR;A;1.2.3.4
 ||example.com^$dnsrewrite=NOERROR;A;1.2.3.5
 ```
 
-will result in a response with two `A` records.
+führt zu einer Antwort mit zwei `A`-Datensätzen.
 
-Currently supported RR types with examples:
+Derzeit unterstützte RR-Typen mit Beispielen:
 
 - `||4.3.2.1.in-addr.arpa^$dnsrewrite=NOERROR;PTR;example.net.` fügt einen `PTR`-Eintrag für Reverse DNS hinzu. Reverse-DNS-Anfragen für `1.2.3.4` an den DNS-Server ergeben `example.net`.
 
   :::note
 
-  The IP MUST be in reverse order. See [RFC 1035][rfc1035].
+  Die IP-Adresse MUSS in umgekehrter Reihenfolge angegeben werden. Siehe [RFC 1035][rfc1035].
 
   :::
 
@@ -379,7 +379,7 @@ Currently supported RR types with examples:
 
 - `$dnstype=AAAA,denyallow=example.org,dnsrewrite=NOERROR;;` antwortet mit einem leeren `NOERROR` antwortet auf alle `AAAA` Anfragen außer denen für `example.org`.
 
-Exception rules unblock one or all rules:
+Ausschlussregeln heben die Sperre einer oder aller Regeln auf:
 
 - `@@||example.com^$dnsrewrite` hebt das Sperren aller DNS-Rewrite-Regeln auf.
 
@@ -387,13 +387,13 @@ Exception rules unblock one or all rules:
 
 :::info
 
-If you are maintaining a blocklist that is included in AdGuard DNS and AdGuard Home (i.e. included into [HostlistsRegistry][hostlistsregistry]), `$dnsrewrite` rules will be automatically filtered out. If these rules are required for your blocklist, please request permission by opening a new issue in the [HostlistsRegistry][hostlistsregistry] repo.
+Wenn Sie eine Blockliste pflegen, die in AdGuard DNS und AdGuard Home enthalten ist (d. h. enthalten in [HostlistsRegistry][hostlistsregistry]), `$dnsrewrite` Die Regeln werden automatisch herausgefiltert. Falls diese Regeln für Ihre Blockliste erforderlich sind, beantragen Sie bitte die Genehmigung, indem Sie ein neues Issue im Repository [„HostlistsRegistry“][hostlistsregistry] eröffnen.
 
 :::
 
 #### `important` {#important-modifier}
 
-The `important` modifier applied to a rule increases its priority over any other rule without the modifier. Even over basic exception rules.
+Der `important` Modifikator, der auf eine Regel angewendet wird, erhöht ihre Priorität gegenüber allen anderen Regeln ohne den Modifikator. Sogar über grundlegende Ausnahmeregeln.
 
 **Beispiele:**
 
@@ -417,7 +417,7 @@ The `important` modifier applied to a rule increases its priority over any other
 
 #### `badfilter` {#badfilter-modifier}
 
-The rules with the `badfilter` modifier disable other basic rules to which they refer. It means that the text of the disabled rule should match the text of the `badfilter` rule (without the `badfilter` modifier).
+Die Regeln mit dem Modifikator `badfilter` deaktivieren andere Grundregeln, auf die sie sich beziehen. Dies bedeutet, dass der Text der deaktivierten Regel dem Text der Regel `badfilter` (ohne den Modifikator `badfilter`) entsprechen sollte.
 
 **Beispiele:**
 
@@ -427,7 +427,7 @@ The rules with the `badfilter` modifier disable other basic rules to which they
 
   :::note
 
-  The `badfilter` modifier currently doesn’t work with `/etc/hosts`-style rules. `127.0.0.1 example.org$badfilter` will **not** disable the original `127.0.0.1 example.org` rule.
+  Der Modifikator `badfilter` funktioniert derzeit nicht mit Regeln im Stil von `/etc/hosts`. `127.0.0.1 example.org$badfilter` wird **nicht** die ursprüngliche Regel `127.0.0.1 example.org` deaktivieren.
 
   :::
 
@@ -435,25 +435,25 @@ The rules with the `badfilter` modifier disable other basic rules to which they
 
 :::note
 
-The `ctag` modifier can only be used in AdGuard Home.
+Der Modifikator `ctag` kann nur in AdGuard Home verwendet werden.
 
 :::
 
-It allows to block domains only for specific types of DNS client tags. You can assign tags to clients in the AdGuard Home UI. In the future, we plan to assign tags automatically by analyzing the behavior of each client.
+Es ermöglicht, Domains nur für bestimmte Arten von DNS-Client-Tags zu blockieren. Sie können Tags den Clients im AdGuard Home UI zuweisen. Zukünftig planen wir, Tags automatisch zu vergeben, indem wir das Verhalten jedes einzelnen Clients analysieren.
 
-The syntax is:
+Die Syntax lautet:
 
 ```none
 $ctag=value1|value2|...
 ```
 
-If one of client’s tags matches the `ctag` values, this rule applies to the client. The syntax for exclusion is:
+Wenn eines der Schlagwörter (Tags) des Clients mit den Werten von `ctag` übereinstimmt, gilt diese Regel für den Client. Die Syntax für den Ausschluss lautet:
 
 ```none
 $ctag=~value1|~value2|...
 ```
 
-If one of client’s tags matches the exclusion `ctag` values, this rule doesn’t apply to the client.
+Wenn eines der Schlagwörter (Tags) des Clients mit den Ausschlusswerten `ctag` übereinstimmt, gilt diese Regel nicht für den Client.
 
 **Beispiele:**
 
@@ -461,7 +461,7 @@ If one of client’s tags matches the exclusion `ctag` values, this rule doesn
 
 - `||example.org^$ctag=~device_phone`: sperrt `example.org` für alle Clients außer denen, die als `device_phone` gekennzeichnet sind.
 
-The list of allowed tags:
+Die Liste der zulässigen Tags:
 
 - Nach Gerätetyp:
 
@@ -497,25 +497,25 @@ The list of allowed tags:
 
 :::note
 
-The `respgeo` modifier can only be used in AdGuard DNS.
+Der Modifikator `respgeo` kann ausschließlich in AdGuard DNS verwendet werden.
 
 :::
 
-The `respgeo` modifier allows you to apply rules based on the country or ASN of the IP address returned in the DNS response. It checks the **destination** IP address — the IP address the domain resolves to. It does **not** check the IP address, country, or ASN of the user, device, or DNS client.
+Mit dem Modifikator `respgeo` können Regeln angewendet werden, die auf dem Land oder der ASN der in der DNS-Antwort zurückgegebenen IP-Adresse basieren. Er überprüft die **Ziel**-IP-Adresse — also die IP-Adresse, auf die die Domain aufgelöst wird. Er **überprüft nicht** die IP-Adresse, das Land oder die ASN des Benutzers, des Geräts oder des DNS-Clients.
 
-##### Blocking by response country
+##### Blockierung nach antwortendem Land
 
-The value of the modifier must be a two-letter country code in ISO 3166-1 alpha-2 format. You can also use `--` to match responses where the country could not be determined.
+Der Wert des Modifikators muss dem zweistelligen Ländercode im ISO 3166-1-Alpha-2-Format entsprechen. Sie können auch `--` verwenden, um Antworten abzugleichen, bei denen das Land nicht ermittelt werden konnte.
 
 **Beispiele:**
 
-- `||*^$respgeo=US`: block domains if the IP address in the DNS response is associated with the United States.
-- `||*^$respgeo=FR|DE`: block domains if the IP address in the DNS response is associated with France or Germany.
-- `||*^$respgeo=--`: block domains if the country of the IP address in the DNS response is unknown.
-- `||*^$respgeo=~--`: block domains if the country of the IP address in the DNS response is known.
-- `@@||whitehouse.gov^`: allow `whitehouse.gov`, even if it is blocked by a wildcard rule with the `respgeo` modifier.
-- `@@||example.org^$respgeo=US`: allow `example.org` if the IP address in the DNS response is associated with the United States.
-- `||whitehouse.gov^$respgeo=US`: blocks `whitehouse.gov` only if the IP address in the DNS response is associated with the United States.
+- `||*^$respgeo=US`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort den Vereinigten Staaten zugeordnet ist.
+- `||*^$respgeo=FR|DE`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort mit Frankreich oder Deutschland in Verbindung steht.
+- `||*^$respgeo=--`: Domains blockieren, wenn das Land der IP-Adresse in der DNS-Antwort unbekannt ist.
+- `||*^$respgeo=~--`: Domains blockieren, wenn das Land der IP-Adresse in der DNS-Antwort bekannt ist.
+- `@@||whitehouse.gov^`: `whitehouse.gov` zulassen, auch wenn die Domain durch eine Platzhalterregel mit dem Modifikator `respgeo` blockiert ist.
+- `@@||example.org^$respgeo=US`: `example.org` zulassen, wenn die IP-Adresse in der DNS-Antwort den Vereinigten Staaten zugeordnet ist.
+- `||whitehouse.gov^$respgeo=US`: blockiert `whitehouse.gov` nur dann, wenn die IP-Adresse in der DNS-Antwort mit den Vereinigten Staaten verknüpft ist.
 - In diesem Beispiel:
 
   ```none
@@ -523,40 +523,40 @@ The value of the modifier must be a two-letter country code in ISO 3166-1 alpha-
   @@||whitehouse.gov^$respgeo=US
   ```
 
-  `@@||whitehouse.gov^$respgeo=US` will **not** allow `whitehouse.gov`, because the first rule blocks the query by inspecting request data, while the second tries to allow it by inspecting the response.
+  `@@||whitehouse.gov^$respgeo=US` wird **nicht** `whitehouse.gov` zulassen, da die erste Regel die Anfrage durch Prüfung der Anfragedaten blockiert, während die zweite versucht, sie durch Prüfung der Antwort zuzulassen.
 
-You can use `~` to invert the condition:
+Sie können `~` verwenden, um die Bedingung zu invertieren:
 
-- `||*^$respgeo=~DE`: block domains if the IP address in the DNS response is **not** associated with Germany.
+- `||*^$respgeo=~DE`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort **nicht** Deutschland zugeordnet ist.
 
-**Limitations**
+**Einschränkungen**
 
-The `respgeo` modifier uses a single calculated IP address and country according to the current *Query log* logic. If a domain resolves to multiple IP addresses or countries, AdGuard DNS does not analyze all returned IP addresses.
+Der `respgeo`-Modifikator verwendet eine einzelne berechnete IP-Adresse und ein Land gemäß der aktuellen *Anfragenprotokoll*-Logik. Wenn eine Domain zu mehreren IP-Adressen oder Ländern aufgelöst wird, analysiert AdGuard DNS nicht alle zurückgegebenen IP-Adressen.
 
-Because many domains use CDNs, load balancing, or geographically distributed infrastructure, the detected country may change over time.
+Da viele Domains CDNs, Lastenausgleich oder geografisch verteilte Infrastruktur verwenden, kann sich das erkannte Land im Laufe der Zeit ändern.
 
-If the country cannot be determined, the GeoIP condition will not match. Use `respgeo=--` to match responses with an unknown country.
+Wenn das Land nicht ermittelt werden kann, trifft die GeoIP-Bedingung nicht zu. Verwenden Sie `respgeo=--`, um Antworten mit einem unbekannten Land abzugleichen.
 
-Rules with the `respgeo` modifier are displayed in the *Query log* as regular rules.
+Regeln mit dem Modifikator `respgeo` werden im *Anfragenprotokoll* als reguläre Regeln angezeigt.
 
-##### Blocking by ASN
+##### Blockierung nach ASN
 
-The `respgeo` modifier can also be used to apply rules based on the ASN of the IP address returned in the DNS response.
+Der `respgeo`-Modifikator kann auch verwendet werden, um Regeln basierend auf der ASN der IP-Adresse anzuwenden, die in der DNS-Antwort zurückgegeben wird.
 
-ASN stands for **Autonomous System Number**. It identifies an autonomous system — a network operated by an ISP, hosting provider, cloud provider, company, or other organization.
+ASN steht für **Autonomous System Number**. Es identifiziert ein autonomes System — ein Netzwerk, das von einem ISP, Hosting-Anbieter, Cloud-Anbieter, Unternehmen oder einer anderen Organisation betrieben wird.
 
-This modifier checks the **destination ASN** — the ASN associated with the IP address the domain resolves to. It does **not** check the ASN of the user, device, or DNS client.
+Dieser Modifikator überprüft die <strong x-id=\"1\">Ziel-ASN</strong> — die ASN, die der IP-Adresse zugeordnet ist, zu der die Domain auflöst. Er überprüft **nicht** die ASN des Benutzers, Geräts oder DNS-Clients.
 
-The value of the modifier must be an ASN in the `AS<number>` format, for example `AS15169`.
+Der Wert des Modifikators muss eine ASN im Format `AS<number>` sein, zum Beispiel `AS15169`.
 
 **Beispiele:**
 
-- `||*^$respgeo=AS15169`: block domains if the IP address in the DNS response belongs to ASN AS15169.
-- `||*^$respgeo=AS15169|AS8075`: block domains if the IP address in the DNS response belongs to ASN AS15169 or AS8075.
-- `||*^$respgeo=AS--`: block domains if the ASN of the IP address in the DNS response is unknown.
-- `||*^$respgeo=~AS--`: block domains if the ASN of the IP address in the DNS response is known.
-- `@@||google.com^$respgeo=AS15169`: allow `google.com` if the IP address in the DNS response belongs to ASN AS15169.
-- `||google.com^$respgeo=AS15169`: block `google.com` only if the IP address in the DNS response belongs to ASN AS15169.
+- `||*^$respgeo=AS15169`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort zu ASN AS15169 gehört.
+- `||*^$respgeo=AS15169|AS8075`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort zum ASN AS15169 oder AS8075 gehört.
+- `||*^$respgeo=AS--`: Domains blockieren, wenn die ASN der IP-Adresse in der DNS-Antwort unbekannt ist.
+- `||*^$respgeo=~AS--`: Domains blockieren, wenn die ASN der IP-Adresse in der DNS-Antwort bekannt ist.
+- `@@||google.com^$respgeo=AS15169`: `google.com` zulassen, wenn die IP-Adresse in der DNS-Antwort zum ASN AS15169 gehört.
+- `||google.com^$respgeo=AS15169`: `google.com` nur dann blockieren, wenn die IP-Adresse in der DNS-Antwort zum ASN AS15169 gehört.
 - In diesem Beispiel:
 
   ```none
@@ -564,35 +564,35 @@ The value of the modifier must be an ASN in the `AS<number>` format, for example
   @@||google.com^$respgeo=AS15169
   ```
 
-  `@@||google.com^$respgeo=AS15169` will **not** allow `google.com`, because the first rule blocks the query by inspecting request data, while the second tries to allow it by inspecting the response.
+  `@@||google.com^$respgeo=AS15169` wird **nicht** `google.com` zulassen, weil die erste Regel die Anfrage durch Auswertung der Anfragedaten blockiert, während die zweite versucht, sie durch Auswertung der Antwort zuzulassen.
 
-You can use `~` to invert the condition:
+Sie können `~` verwenden, um die Bedingung zu invertieren:
 
-- `||*^$respgeo=~AS15169`: block domains if the IP address in the DNS response does **not** belong to ASN AS15169.
+- `||*^$respgeo=~AS15169`: Domains blockieren, wenn die IP-Adresse in der DNS-Antwort **nicht** zu ASN AS15169 gehört.
 
-**Limitations**
+**Einschränkungen**
 
-The `respgeo` modifier uses a single calculated IP address and ASN according to the current *Query log* logic. If a domain resolves to multiple IP addresses or ASNs, AdGuard DNS does not analyze all returned ASNs.
+Der `respgeo`-Modifikator verwendet eine einzelne berechnete IP-Adresse und ASN gemäß der aktuellen *Anfragenprotokoll*-Logik. Wenn eine Domain zu mehreren IP-Adressen oder ASNs aufgelöst wird, analysiert AdGuard DNS nicht alle zurückgegebenen ASNs.
 
-Large CDN, cloud, or hosting ASNs may contain many unrelated websites. Blocking an ASN may therefore affect more domains than expected.
+Große CDN-, Cloud- oder Hosting-ASNs können viele nicht miteinander verbundene Websites enthalten. Die Sperrung einer ASN kann daher mehr Domains betreffen als erwartet.
 
-If the ASN cannot be determined, the ASN condition will not match. Use `respgeo=AS--` to match responses with an unknown ASN.
+Wenn die ASN nicht ermittelt werden kann, stimmt die ASN-Bedingung nicht überein. Verwenden Sie `respgeo=AS--`, um Antworten mit einem unbekannten ASN abzugleichen.
 
-ASN does not always correspond to a specific company, product, or service. It only identifies the network associated with the resolved IP address.
+Eine ASN entspricht nicht immer einem bestimmten Unternehmen, Produkt oder Dienst. Es identifiziert nur das Netzwerk, das mit der aufgelösten IP-Adresse verbunden ist.
 
-Rules with the `respgeo` modifier are displayed in the *Query log* as regular rules.
+Regeln mit dem Modifikator `respgeo` werden im *Anfragenprotokoll* als reguläre Regeln angezeigt.
 
 ## `/etc/hosts`-Style-Syntax {#etc-hosts-syntax}
 
-For each host a single line should be present with the following information:
+Für jeden Host sollte eine einzelne Zeile mit den folgenden Informationen vorhanden sein:
 
 ```none
 IP_Adresse canonical_hostname [aliases...]
 ```
 
-Fields of the entries are separated by any number of space or tab characters. Text from the `#` character until the end of the line is a comment and is ignored.
+Die Felder der Einträge werden durch eine beliebige Anzahl von Leer- oder Tabulatorzeichen getrennt. Der Text ab dem Zeichen `#` bis zum Ende der Zeile ist ein Kommentar und wird ignoriert.
 
-Hostnames may contain only alphanumeric characters, hyphen-minus signs (`-`), and periods (`.`). They must begin with an alphabetic character and end with an alphanumeric character. Optional aliases provide for name changes, alternate spellings, shorter hostnames, or generic hostnames (for example, `localhost`).
+Hostnamen dürfen nur alphanumerische Zeichen, Bindestrich-Minuszeichen (`-`) und Punkte (`.`) enthalten. Sie müssen mit einem Buchstaben beginnen und mit einem alphanumerischen Zeichen enden. Optionale Aliase ermöglichen Namensänderungen, alternative Schreibweisen, kürzere Hostnamen oder generische Hostnamen (z. B. `localhost`).
 
 **Beispiel:**
 
@@ -603,11 +603,11 @@ Hostnames may contain only alphanumeric characters, hyphen-minus signs (`-`), an
 127.0.0.1 example.net # Dies ist auch ein Kommentar
 ```
 
-In AdGuard Home, the IP addresses are used to respond to DNS queries for these domains. In Private AdGuard DNS, these addresses are simply blocked.
+In AdGuard Home werden die IP-Adressen verwendet, um DNS-Anfragen für diese Domains zu beantworten. Im Private AdGuard DNS werden diese Adressen einfach blockiert.
 
 ## Nur-Domain-Syntax {#domains-only-syntax}
 
-A simple list of domain names, one name per line.
+Eine einfache Liste von Domainnamen, ein Name pro Zeile.
 
 **Beispiel:**
 
@@ -618,17 +618,17 @@ example.org
 example.net # dies ist auch ein Kommentar
 ```
 
-If a string is not a valid domain (e.g. `*.example.org`), AdGuard Home will consider it to be an [Adblock-style syntax][] rule.
+Wenn eine Zeichenkette keine gültige Domain ist (z.B. `*.example.org`), wird AdGuard Home sie als [Adblock-Syntax][]-Regel betrachten.
 
 ## Hostlists Compiler {#hostlist-compiler}
 
-If you are maintaining a blocklist and use different sources in it, [Hostlist compiler][] may be useful to you. It is a simple tool that makes it easier to compile a hosts blocklist compatible with AdGuard Home, Private AdGuard DNS or any other AdGuard product with DNS filtering.
+Wenn Sie eine Blockliste pflegen und darin verschiedene Quellen verwenden, kann der [Hostlist-Compiler][] für Sie nützlich sein. Es ist ein einfaches Hilfsmittel, das die Zusammenstellung einer Sperrliste für Hosts erleichtert, die mit AdGuard Home, Private AdGuard DNS oder jedem anderen AdGuard-Produkt mit DNS-Filterung kompatibel ist.
 
-What it’s capable of:
+Was es kann:
 
 1. Zusammenstellung einer einzigen Blockliste aus mehreren Quellen.
 
-2. Exclude the rules you don’t need.
+2. Streicht die Regeln, die nicht benötigt werden.
 
 3. Bereinigt die resultierende Liste: entfernt Dubletten, entfernt ungültige Regeln und komprimiert die Liste.
 
@@ -638,14 +638,19 @@ What it’s capable of:
 
 <!-- external links -->
 
+[Adblock-Syntax]: #adblock-style-syntax
+
+[hostlistsregistry]: https://github.com/AdguardTeam/HostlistsRegistry
+
 [hostlistsregistry]: https://github.com/AdguardTeam/HostlistsRegistry
 
-[Adblock-style syntax]: #adblock-style-syntax
-[`client`]: #client-modifier
+[Adblock-Stil-Syntax]: #adblock-style-syntax
+[client</code>-]: #client-modifier
 [`dnstype`]: #dnstype-modifier
 
 [AdGuard DNS filter]: https://github.com/AdguardTeam/AdGuardSDNSFilter
 [Hostlist compiler]: https://github.com/AdguardTeam/HostlistCompiler
+[Hostlist-Compiler]: https://github.com/AdguardTeam/HostlistCompiler
 [regexp]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions
+[traditionellen Adblock-Syntax]: https://adguard.com/kb/general/ad-filtering/create-own-filters/
 [rfc1035]: https://tools.ietf.org/html/rfc1035#section-3.5
-[traditional Adblock-style syntax]: https://adguard.com/kb/general/ad-filtering/create-own-filters/
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index d302ecf63..4f9236763 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3d766a229..d32af4874 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/de/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Referenz
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 1f9ea5f6c..b9987f181 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Tiene las siguientes propiedades:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Valores posibles:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Tiene las siguientes propiedades:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 049d4568c..339ecfdf9 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 447a179be..84f40a2a8 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 2f457d5f3..e60358809 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/es/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Referencia
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 322b14725..2236aa29f 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 0c1fa2482..764538781 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 4fead3a2a..8252bb50e 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Il a les propriétés suivantes :
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Valeurs possibles :
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Il a les propriétés suivantes :
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index d4d461d5b..dd848ec8c 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Remplacez l'ancien fichier exécutable AdGuard Home par le nouveau. On most Unix systems the command would look something like this:
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
index 707babbdc..8eb3db076 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/dns-filtering-syntax.md
@@ -509,13 +509,13 @@ La valeur du modificateur doit être un code pays à deux lettres au format ISO
 
 **Exemples :**
 
-- `||*^$respgeo=US`: block domains if the IP address in the DNS response is associated with the United States.
-- `||*^$respgeo=FR|DE`: block domains if the IP address in the DNS response is associated with France or Germany.
-- `||*^$respgeo=--`: block domains if the country of the IP address in the DNS response is unknown.
-- `||*^$respgeo=~--`: block domains if the country of the IP address in the DNS response is known.
-- `@@||whitehouse.gov^`: allow `whitehouse.gov`, even if it is blocked by a wildcard rule with the `respgeo` modifier.
-- `@@||example.org^$respgeo=US`: allow `example.org` if the IP address in the DNS response is associated with the United States.
-- `||whitehouse.gov^$respgeo=US`: blocks `whitehouse.gov` only if the IP address in the DNS response is associated with the United States.
+- `||*^$respgeo=US` : bloquer les domaines si l’adresse IP dans la réponse DNS est associée aux États-Unis.
+- `||*^$respgeo=FR|DE` : bloquer les domaines si l'adresse IP dans la réponse DNS est associée à la France ou à l'Allemagne.
+- `||*^$respgeo=--` : bloquer les domaines si le pays de l'adresse IP dans la réponse DNS est inconnu.
+- `||*^$respgeo=~--` : bloquer les domaines si le pays de l'adresse IP dans la réponse DNS est connu.
+- `@@||whitehouse.gov^` : autoriser `whitehouse.gov`, même s'il est bloqué par une règle générique avec le modificateur `respgeo`.
+- `@@||example.org^$respgeo=US` : autoriser `example.org` si l'adresse IP dans la réponse DNS est associée aux États-Unis.
+- `||whitehouse.gov^$respgeo=US` : bloque `whitehouse.gov` uniquement si l’adresse IP dans la réponse DNS est associée aux États-Unis.
 - Dans cet exemple :
 
   ```none
@@ -523,11 +523,11 @@ La valeur du modificateur doit être un code pays à deux lettres au format ISO
   @@||whitehouse.gov^$respgeo=US
   ```
 
-  `@@||whitehouse.gov^$respgeo=US` will **not** allow `whitehouse.gov`, because the first rule blocks the query by inspecting request data, while the second tries to allow it by inspecting the response.
+  `@@||whitehouse.gov^$respgeo=US` n'autorisera **pas** `whitehouse.gov`, car la première règle bloque la requête en inspectant les données de requête, tandis que la seconde tente de l'autoriser en inspectant la réponse.
 
-You can use `~` to invert the condition:
+Vous pouvez utiliser `~` pour inverser la condition :
 
-- `||*^$respgeo=~DE`: block domains if the IP address in the DNS response is **not** associated with Germany.
+- `||*^$respgeo=~DE` : bloque les domaines si l'adresse IP dans la réponse DNS n'est **pas** associée à l'Allemagne.
 
 **Limitations**
 
@@ -566,7 +566,7 @@ The value of the modifier must be an ASN in the `AS<number>` format, for example
 
   `@@||google.com^$respgeo=AS15169` will **not** allow `google.com`, because the first rule blocks the query by inspecting request data, while the second tries to allow it by inspecting the response.
 
-You can use `~` to invert the condition:
+Vous pouvez utiliser `~` pour inverser la condition :
 
 - `||*^$respgeo=~AS15169`: block domains if the IP address in the DNS response does **not** belong to ASN AS15169.
 
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 58984b84b..37bc15ce8 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::avertissement
 
-Pour accéder à ce point de terminaison, vous devez nous contacter à **devteam@adguard.com**. Veuillez décrire la raison et les cas d'utilisation de ce point de terminaison, et fournir l'URL de redirection. Une fois l’approbation obtenue, vous recevrez un identificateur de client unique, qui doit être utilisé pour le paramètre **client_id**.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Veuillez décrire la raison et les cas d'utilisation de ce point de terminaison, et fournir l'URL de redirection. Une fois l’approbation obtenue, vous recevrez un identificateur de client unique, qui doit être utilisé pour le paramètre **client_id**.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::avertissement
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index a9f2671b3..0fd722882 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Référence
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 3afd51952..15d47989a 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 0c1fa2482..764538781 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 86843e633..112451e7a 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Ha le seguenti proprietà:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Valori possibili:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Ha le seguenti proprietà:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index ad32ba6f5..409da3052 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Sostituisci il vecchio file eseguibile di AdGuard Home con quello nuovo. On most Unix systems the command would look something like this:
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index ce22ddcea..ce3886398 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-Per accedere a questo endpoint, è necessario contattarci a **devteam@adguard.com**. Si prega di descrivere il motivo e gli casi d'uso per questo endpoint, nonché di fornire l'URI di reindirizzamento. Una volta approvato, riceverai un identificatore cliente unico, che dovrà essere utilizzato per il parametro **client_id**.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Si prega di descrivere il motivo e gli casi d'uso per questo endpoint, nonché di fornire l'URI di reindirizzamento. Una volta approvato, riceverai un identificatore cliente unico, che dovrà essere utilizzato per il parametro **client_id**.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index f09f63d03..a1f3cc806 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/it/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Riferimento
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 78bafd2e6..967f6e94d 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 5b2b65dc3..cd33bb86a 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 6c3d6bf3d..37516de86 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 3919371ce..763286895 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 60a7f1270..194652879 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: API에 대한 도움말
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..5704fdd39 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: lijst van upstream DNS-servers.  Opmerkingen (regels die beginnen met `#`) en lege regels worden genegeerd.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Opmerkingen (regels die beginnen met `#`) en lege regels worden genegeerd.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Opmerkingen (regels die beginnen met `#`) en lege regels worden genegeerd.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Opmerkingen (regels die beginnen met `#`) en lege regels worden genegeerd.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -422,7 +422,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   - `enabled`: Specifies, if AdGuard Home should track simultaneous identical requests and perform a single lookup for them. By default, the value is `true`.
 
-- `edns_client_subnet`: Controls EDNS Client Subnet behavior. It has the following properties:
+- `edns_client_subnet`: Controls EDNS Client Subnet behavior. Het heeft de volgende eigenschappen:
 
   - `enabled`: Add the ECS option to upstream requests.
 
@@ -436,7 +436,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `disallowed_clients`: The list of CIDRs, IP addresses, or ClientIDs of disallowed DNS clients. If this list has entries, AdGuard Home will drop requests from these clients. Note that this field is ignored if there are entries in `allowed_clients`.
 
-  See also the note in the [Docker wiki page][docker-conf] about using this property within a container.
+  Zie ook de opmerking op de [Docker-wikipagina][docker-conf] over het gebruik van deze eigenschap binnen een container.
 
 - `blocked_hosts`: The list of domain names, wildcards or filtering rules to match requests that shouldn't be processed at all. These are ignored by statistics and query log as well.
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -670,7 +670,7 @@ Built-in DHCP server configuration. See also the [DHCP][DHCPv4] article. It has
 
 - `interface_name`: Network interface name (`eth0`, `en0`, and so on).
 
-- `dhcpv4`: DHCPv4 settings. It has the following properties:
+- `dhcpv4`: DHCPv4 settings. Het heeft de volgende eigenschappen:
 
   - `gateway_ip`: Gateway IP address.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index a8f39cf58..02ef7466d 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index d6936e9b0..48e76eec3 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::waarschuwing
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::waarschuwing
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3e9c184c5..724cdd490 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Referentie
 sidebar_position: 2
 description: Automatisch gegenereerde API-referentie voor de openbare AdGuard DNS-API, live weergegeven vanuit de OpenAPI-specificatie.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 7d9d0ef64..7b000b084 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Ele tem as seguintes propriedades:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Valores possíveis:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Ele tem as seguintes propriedades:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index c82ca6934..ee232399c 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 3f2626f98..6a1d4bef1 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 50adb9ecd..1f8f041b2 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Referência
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index efc9ec678..0356d76a6 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Он обладает следующ
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Возможные значения:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Он обладает следующ
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 99b3dc7ba..9bb18c668 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ curl -s -S -L 'https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Распакуйте архив AdGuard Home во временную директорию. Например, если вы скачали архив в директорию `~/Downloads` и хотите извлечь его в `/tmp/`:
+5. Распакуйте архив AdGuard Home во временную директорию. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    На macOS введите что-то вроде:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Замените старый исполняемый файл AdGuard Home на новый. В большинстве Unix-систем команда будет выглядеть примерно так:
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index d06aecf57..b18e317b1 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 4c25fbb1b..0b8555052 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Руководство по API
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 266dd560b..078153332 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 0c1fa2482..764538781 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 266dd560b..078153332 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 0c1fa2482..764538781 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 49a4e1459..97a98b75e 100644
--- a/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/sr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index fca345dd8..67e793b08 100644
--- a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/sr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index 3d9e6e234..e8a47586e 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. Aşağıdaki özelliklere sahiptir:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Olası değerler:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. Aşağıdaki özelliklere sahiptir:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 3cc8d774b..90ad08b1a 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ Düğme görüntülenmiyorsa veya otomatik güncelleme başarısız olduysa, ell
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. AdGuard Home arşivini geçici bir dizine çıkarın. Örneğin, arşivi `~/Downloads` dizininize indirdiyseniz ve `/tmp/` dizinine çıkarmak istiyorsanız:
+5. AdGuard Home arşivini geçici bir dizine çıkarın. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    macOS'ta aşağıdaki gibi bir şey yazın:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Eski AdGuard Home yürütülebilir dosyasını yenisiyle değiştirin. Çoğu Unix sisteminde komut aşağıdaki gibi görünecektir:
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 2149852a3..0fbe833db 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index aedc5a88d..ea07b652d 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Referans
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index 266dd560b..078153332 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index b7039b831..2e97b205d 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index debad557e..9bd6e69c2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. 它包含以下属性：
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. 可能的选项值如下：
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. 它包含以下属性：
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index b22d1bdb8..647e94125 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ curl -s -S -L 'https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. 将 AdGuard Home 压缩包解压到临时目录。 例如，如果您将压缩包下载到 `~/Downloads` 目录，并希望将其解压缩到 `/tmp/`：
+5. 将 AdGuard Home 压缩包解压到临时目录。 For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    在 macOS 上，键入如下内容：
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. 将旧的 AdGuard Home 可执行文件替换为新的可执行文件。 在大多数 Unix 系统上，该命令如下所示：
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 4de132fbc..17c17841f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index d9cd90e71..236b346be 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: 参考资料
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/configuration.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
index a33e548a9..c16dc4667 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/configuration.md
@@ -386,21 +386,21 @@ The `dns` object configures the DNS server. It has the following properties:
 
 - `refuse_any`: Another DDoS protection mechanism. Requests of type `ANY` are rarely needed, so refusing to serve them mitigates against attackers trying to use your DNS as a reflection. Safe to disable if DNS server is not available from internet.
 
-- `upstream_dns`: List of upstream DNS servers.
+- `upstream_dns`: List of upstream DNS servers.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_dns_file`: Path to a file with the list of upstream DNS servers. If it is configured, the value of `upstream_dns` is ignored.
 
-- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.
+- `bootstrap_dns`: List of DNS servers used for initial hostname resolution in case an upstream server name is a hostname.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `bootstrap_prefer_ipv6`: If `true`, instructs the bootstrapper to prefer IPv6 addresses to IPv4 ones when resolving DoH, DoQ, and DoT hostnames.
 
-- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.
+- `fallback_dns`: List of fallback DNS servers used when upstream DNS servers are not responding.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `private_networks`: List of networks used to check if an IP address belongs to a locally-served address registry. If empty, AdGuard Home will use the set defined by [RFC 6303][private-ip].
 
 - `use_private_ptr_resolvers`: If AdGuard Home should use private reverse DNS servers.
 
-- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.
+- `local_ptr_upstreams`: List of upstream DNS servers to resolve PTR requests for addresses inside locally-served networks. If empty, AdGuard Home will automatically try to get local resolvers from the OS. Domain-specific upstreams are validated for being a valid ARPA domain pointing to a locally-served network.  Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_mode`: The mode describes the logic through which the upstreams will be used. Possible values:
 
@@ -485,7 +485,7 @@ The `dns` object configures the DNS server. It has the following properties:
 
   This setting is supported on Linux OSs only. This feature is similar to `--ipset` in dnsmasq.
 
-- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) are supported.
+- `ipset_file`: Same as `ipset`, but the rules are read from a file. If this property is set, property `ipset` is ignored. Comments (lines starting with `#`) and empty lines are ignored.
 
 - `upstream_timeout`: The timeout for querying upstream servers. Zero value will be rewritten with default one which is `10s`.
 
@@ -905,5 +905,6 @@ For a list of supported profiles go to `http://localhost:6060/debug/pprof/`.
 Alternatively, you may want to simply download the file and analyze it later:
 
 ```sh
-wget http://localhost:6060/debug/pprof/heap go tool --http=':8080' heap
+wget http://localhost:6060/debug/pprof/heap
+go tool --http=':8080' heap
 ```
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/faq.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/faq.md
index a91b2649f..5438195ad 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/faq.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-home/faq.md
@@ -396,16 +396,16 @@ If the button isn’t displayed or an automatic update has failed, you can updat
    cp -r ./AdGuardHome.yaml ./data ~/my-agh-backup/
    ```
 
-5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `~/Downloads` directory and want to extract it to `/tmp/`:
+5. Extract the AdGuard Home archive to a temporary directory. For example, if you downloaded the archive to your `/tmp/` directory:
 
    ```sh
-   tar -C /tmp/ -f ~/Downloads/AdGuardHome_linux_amd64.tar.gz -x -v -z
+   tar -C /tmp/ -f /tmp/AdGuardHome_linux_amd64.tar.gz -x -v -z
    ```
 
    On macOS, type something like:
 
    ```sh
-   unzip -d /tmp/ ~/Downloads/AdGuardHome_darwin_amd64.zip
+   unzip -d /tmp/ /tmp/AdGuardHome_darwin_amd64.zip
    ```
 
 6. Replace the old AdGuard Home executable file with the new one. On most Unix systems the command would look something like this:
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/overview.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
index 0c1fa2482..764538781 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/overview.md
@@ -135,7 +135,7 @@ $ curl 'https://api.adguard-dns.io/oapi/v1/revoke_token' -i -X POST \
 
 :::warning
 
-To access this endpoint, you need to contact us at **devteam@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
+To access this endpoint, you need to contact us at **b2b@adguard.com**. Please describe the reason and use cases for this endpoint, as well as provide the redirect URI. Upon approval, you will receive a unique client identifier, which should be used for the **client_id** parameter.
 
 :::
 
@@ -176,7 +176,7 @@ Location: REDIRECT_URI#access_token=...&token_type=Bearer&expires_in=3600&state=
 
 :::warning
 
-To access this endpoint, please contact us at **devteam@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
+To access this endpoint, please contact us at **b2b@adguard.com**. In your message, please describe the reason for and use cases of this endpoint, and provide the redirect URI. Once approved, you will receive a unique client identifier to use for the **client_id** parameter.
 
 :::
 
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
index 3929a1a14..8a143cf2e 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/private-dns/api/reference.mdx
@@ -2,6 +2,7 @@
 title: Reference
 sidebar_position: 2
 description: Auto-generated API reference for the AdGuard DNS public API, rendered live from the OpenAPI specification.
+custom_edit_url: null
 ---
 
 import OpenApiReference from '@site/src/components/OpenApiReference';