Merge pull request #537 from AdguardTeam/update-translations

Update translations

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md

@@ -27,7 +27,27 @@ Alternatively, instead of unchecking **Auto-deny apps from auto starting** entir
 
 Xiaomi (and especially MIUI) devices are among the most troublesome ones when it comes to background work. They are known to limit background processes and have non-standard permissions with a lack of proper documentation to top it off. Sometimes apps just don't work right on Xiaomi phones and there's little that can be done about that. Below are some actions you might attempt to perform if you run into any trouble regarding AdGuard's background work on various Xiaomi devices.
 
-### MIUI 12.0.8+
+### MIUI 13+ and HyperOS
+
+Depending on the MIUI and HyperOS versions, there are two ways to change the battery optimization settings on your phone and block ads more efficiently.
+
+Option 1
+
+1. Go to **Settings** → **Apps** → **Permissions** → **Background autostart** and allow AdGuard to run in the background
+
+1. Return to **Settings** → **Apps** → **Manage apps** → **AdGuard** and uncheck **Pause app activity if unused**
+
+1. Go to **Battery saver** and tap **No restrictions**
+
+Option 2
+
+1. Go to **Settings** → **Apps** → **Manage apps** → **AdGuard** and enable **Autostart**
+
+1. Go to **Battery saver** and tap **No restrictions**
+
+Done! You have successfully set up AdGuard to work in the background.
+
+### MIUI 12.0.8
 
 To let your AdGuard app run successfully in the background, do the following:
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md

@@ -89,17 +89,25 @@ In this article we give examples of how to set up some of the most popular proxi
 
 ### How to use AdGuard with NordVPN
 
-1. Open AdGuard and go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server**.
+1. Log in to your NordVPN account.
 
-1. Tap the **Add proxy server** button and enter the following data:
+1. Go to **Services** → **NordVPN** → **Manual setup** and set up your service credentials manually.
+
+1. You will receive a verification code on the email address you use for NordVPN. Use it on your NordVPN account as requested, then tap *Apply* and *OK* to save the changes.
+
+![Manual setup](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/outbound-proxy/nordvpn-manual-setup.png)
+
+1. Open the AdGuard app, go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server** → **Add proxy server**.
+
+1. Enter the following data:
 
-    | Field      | Value                                                                                                                           |
-    | ---------- | ------------------------------------------------------------------------------------------------------------------------------- |
-    | Proxy type | *SOCKS5*                                                                                                                        |
-    | Proxy host | *any server from [this list](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent)* |
-    | Proxy port | *1080*                                                                                                                          |
+    | Field      | Value                                                                                                                         |
+    | ---------- | ----------------------------------------------------------------------------------------------------------------------------- |
+    | Proxy type | *SOCKS5*                                                                                                                      |
+    | Proxy host | Any server from [this list](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent) |
+    | Proxy port | *1080*                                                                                                                        |
 
-1. For **Username** and **Password** fields, enter your NordVPN Username and Password.
+1. Enter your NordVPN credentials in the **Username** and **Password** fields.
 
 1. Tap **Save and select**.
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md

@@ -13,15 +13,15 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects
 
 ### iPhone
 
-Requires iOS 11.2 or later.
+Requires iOS 13 or later.
 
 ### iPad
 
-Requires iPadOS 11.2 or later.
+Requires iPadOS 13 or later.
 
 ### iPod touch
 
-Requires iOS 11.2 or later.
+Requires iOS 13 or later.
 
 ## AdGuard for iOS installation
 

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md

@@ -21,160 +21,168 @@ To find *Advanced Settings*, open AdGuard, click the gear icon, select *Advanced
 
 ## Advanced Settings
 
-`network.extension.exclude.domains`
+### Network settings
+
+#### `network.extension.exclude.domains`
 
 The listed domains will be excluded from filtering in the *Network Extension* mode. Use a comma or line break to separate values.
 
-`network.extension.exclude.ports`
+#### `network.extension.exclude.ports`
 
 The listed ports will be excluded from filtering in the *Network Extension* mode. Use a comma or line break to separate values.
 
-`network.extension.route.exclude`
+#### `network.extension.route.exclude`
 
 The listed routes will be excluded from filtering in the *Network Extension* mode. Set routes using an IP address or destination CIDR. Separate values with commas or line breaks.
 
-`network.extension.http.downgrade.bundleids`
+#### `network.extension.http.downgrade.bundleids`
 
 Here you can specify a list of applications for which the HTTP/2 protocol will be downgraded to HTTP/1.1 in the *Network Extension* filtering mode. The bundle ID should be separated by a comma or a line break.
 
-`network.extension.monterey.force.split.tunnel`
+#### `network.extension.monterey.force.split.tunnel`
 
 Here you can prohibit AdGuard from using the "default route" which is enabled by default in the *Network Extension* mode on macOS Monterey. AdGuard uses "default route" to disable iCloud Private Relay and Protect Mail Activity, as it cannot operate in unison with them.
 
 You will find more information about the problem [in this article](../icloud-private-relay).
 
-`network.extension.dns.redirect.exclude.bundleids`
+#### `network.extension.dns.redirect.exclude.bundleids`
 
 Here you can specify a list of applications that make DNS queries directly not via system DNS resolver (for example, some VPN clients or DNS filtering applications). DNS filtering will be disabled for them in the *Network Extension mode*. The bundle IDs should be separated by a comma or line break.
 
-`network.dns.filter.secure.request`
+#### `network.dns.filter.secure.request`
 
 Redirects secure DNS requests to a local DNS proxy, if there is one available.
 
-`network.https.ocsp.check`
+#### `network.https.ocsp.check`
 
 By setting `true`, you enable HTTPS certificate revocation checking.
 
-`network.tcp.keepalive.enabled`
+#### `network.tcp.keepalive.enabled`
 
 Periodically sends TCP packets over an idle connection to ensure that it remains active and to renew NAT timeouts.
 
-`network.tcp.keepalive.interval.seconds`
+#### `network.tcp.keepalive.interval.seconds`
 
 Idle time, in seconds, before sending a keepalive probe. If 0 is specified, the system will use the default value.
 
-`network.tcp.keepalive.timeout.seconds`
+#### `network.tcp.keepalive.timeout.seconds`
 
 Time, in seconds, before sending another keepalive probe to an unresponsive peer. If 0 is specified, the value selected by the system will be used.
 
-`network.https.ech.enabled`
+#### `network.https.ech.enabled`
 
 Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos.
 
-`network.https.enforce.certificate.transparency`
+#### `network.https.enforce.certificate.transparency`
 
 Verifies the authenticity of all certificates for the domain based on Chrome Certificate Transparency Policy.
 
-`network.https.filter.http3.enabled`
+#### `network.https.filter.http3.enabled`
 
 By setting `true`, you allow AdGuard to filter traffic sent over HTTP/3, the latest version of the HTTP protocol based on QUIC.
 
-`network.filtering.localnetwork`
+#### `network.filtering.localnetwork`
 
 By setting `true`, you enable local network filtering.
 
-`network.filtering.localhost`
+#### `network.filtering.localhost`
 
 By setting `true`, you enable LoopBack filtering.
 
-`dns.proxy.bootstrap.ips`
+### DNS settings
+
+#### `dns.proxy.bootstrap.ips`
 
 Here you can enter the IP addresses of the DNS servers that will be used to determine the address of the encrypted DNS server.
 
-`dns.proxy.fallback.ips`
+#### `dns.proxy.fallback.ips`
 
 Here you can specify a list of IP addresses of DNS servers that will be used as backups in case the encrypted DNS server fails to respond.
 
-`dns.proxy.fallback.on.upstreams.failure.enabled`
+#### `dns.proxy.fallback.on.upstreams.failure.enabled`
 
 Normal queries will be redirected to a fallback upstream if all normal upstreams fail.
 
-`dns.proxy.detect.search.domains`
+#### `dns.proxy.detect.search.domains`
 
 This option enables automatic detection of the local network domain, which will be automatically redirected to the fallback DNS server instead of the main DNS server.
 
-`dns.proxy.fallback.domains`
+#### `dns.proxy.fallback.domains`
 
 Here you can list domains for which the fallback DNS server will be used instead of the main DNS server.
 
-`dns.proxy.adblockrules.blocking.mode`
+#### `dns.proxy.adblockrules.blocking.mode`
 
 Here you can specify the type of DNS server response to blocked requests, corresponding to ad-blocker-style rules.
 
 - 0 — respond with REFUSED
 - 1 — respond with NXDOMAIN
 - 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address`
 
-`dns.proxy.hostrules.blocking.mode`
+#### `dns.proxy.hostrules.blocking.mode`
 
 Here you can specify the type of DNS server response to blocked requests, corresponding to hosts rules:
 
 - 0 — respond with REFUSED
 - 1 — respond with NXDOMAIN
 - 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address`
 
-`dns.proxy.blocking.response.IPv4.address`
+#### `dns.proxy.blocking.response.IPv4.address`
 
 Here you can specify the IPv4 address that will be returned in response to blocked "A" requests when `dns.proxy.adblockrules.blocking.mode` or `dns.proxy.hostrules.blocking.mode` is set to the response type "ADDRESS".
 
-`dns.proxy.blocking.response.IPv6.address`
+#### `dns.proxy.blocking.response.IPv6.address`
 
 Here you can specify the IPv6 address that will be returned in response to blocked "AAAA" requests when `dns.proxy.adblockrules.blocking.mode` or `dns.proxy.hostrules.blocking.mode` is set to the response type "ADDRESS".
 
-`dns.proxy.block.AAAA.requests`
+#### `dns.proxy.block.AAAA.requests`
 
 Here you can enable IPv6 DNS query blocking.
 
-`dns.proxy.blocked.response.TTL.in.seconds`
+#### `dns.proxy.blocked.response.TTL.in.seconds`
 
 Here you can specify the TTL (time to live) value that will be returned in response to a blocked request.
 
-`dns.proxy.parallel.upstream.queries.enabled`
+#### `dns.proxy.parallel.upstream.queries.enabled`
 
 All upstreams are queried simultaneously. The first response is returned.
 
-`dns.proxy.servfail.on.upstreams.failure.enabled`
+#### `dns.proxy.servfail.on.upstreams.failure.enabled`
 
 Responds to upstream failure with a SERVFAIL packet.
 
-`dns.proxy.http3.enabled`
+#### `dns.proxy.http3.enabled`
 
 Enables HTTP/3 for DNS-over-HTTPS upstreams to accelerate connection.
 
-`dns.proxy.block.encrypted.client.hello.response`
+#### `dns.proxy.block.encrypted.client.hello.response`
 
 Removes the Encrypted Client Hello parameters from responses.
 
-`stealth.antidpi.http.split.fragment.size`
+### Stealth Mode settings
+
+#### `stealth.antidpi.http.split.fragment.size`
 
 Adjusts the size of the HTTP request fragmentation. Valid values: 1–1500. If an invalid size is specified, the system will use the default value.
 
-`stealth.antidpi.clienthello.split.fragment.size`
+#### `stealth.antidpi.clienthello.split.fragment.size`
 
 This option specifies the size of TCP packet fragmentation, which helps avoid deep packet inspection. Valid values: 1–1500. If an invalid size is specified, the system will use the default value.
 
-`stealth.antidpi.http.space.juggling`
+#### `stealth.antidpi.http.space.juggling`
 
 Adds extra space between the HTTP method and the URL and removes space after the "Host:" field.
 
-`stealth.antidpi.split.delay.millisecond`
+#### `stealth.antidpi.split.delay.millisecond`
 
 Here you can specify the delay, in milliseconds, after sending the first fragment, if fragmentation is performed.
 
-`subscription.link.interception.userscript`
+### Subscription link interception settings (userscripts and filters)
+
+#### `subscription.link.interception.userscript`
 
 Activate this feature if you want AdGuard to automatically intercept the URLs of userscripts and open the installation window.
 
-`subscription.link.interception.filter`
+#### `subscription.link.interception.filter`
 
 Activate this feature if you want AdGuard to automatically intercept subscription URLs (for example, abp:subscribe, etc.) and open the custom filter setup window.