Changes again

docs/adguard-for-android/solving-problems/compatibility-issues.md

@@ -11,18 +11,28 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote
 
 ## VPN apps
 
-Other VPN apps are incompatible with AdGuard running in the Local VPN filtering mode since you cannot have two active VPNs at the same time. To solve this problem we suggest you: 
+Other VPN apps are incompatible with AdGuard running in the Local VPN filtering mode since you cannot have two active VPNs at the same time. To solve this problem we suggest you:
 
 * use [AdGuard VPN](https://adguard-vpn.com/welcome.html) — it has Integrated mode that allows two apps to operate seamlessly
 * use AdGuard in Local HTTP Proxy mode
-> Please note that 'manual' HTTP Proxy mode is not supported on devices since Android 10
-* configure your VPN app to to act as an outbound proxy and set up a local outbound proxy using the parameters from the third-party application. To do this, a third-party VPN application must support SOCKS4/SOCKS5 mode. For example, AdGuard can be automatically configured with 'Orbot: Proxy with Tor'.
+
+:::caution
+
+Please note that on Android 10 and later devices, the 'manual' HTTP proxy mode is no longer supported.
+
+:::
+
+* configure your VPN app to to act as an outbound proxy and set up a local outbound proxy using the parameters from the third-party app. To do this, a third-party VPN app must support SOCKS4/SOCKS5 mode. For example, AdGuard can be automatically configured with 'Orbot: Proxy with Tor'.
 
 ## Private DNS
 
 The Private DNS feature was introduced in Android Pie. Before version Q, Private DNS didn't break AdGuard DNS filtering logic and the DNS forwarding through AdGuard worked normally. But starting from version Q, the presence of Private DNS forces apps to redirect traffic through the system resolver instead of AdGuard. See Android [devs blog](https://android-developers.googleblog.com/2018/04/dns-over-tls-support-in-android-p.html) for more details.
 
-* To solve the problem with Private DNS, use the `$network` rule
+:::tip
+
+To solve the problem with Private DNS, use the `$network` rule
+
+:::
 
 Some device manufacturers keep Private DNS settings hidden and set 'Automatic' mode as a default one. Thus, disabling Private DNS is impossible but we can make the system think that the upstream is not valid by blocking it with a `$network` rule. For instance, if the system uses Google DNS by default, we can add rules `|8.8.4.4^$network` and `|8.8.8.8^$network` to block Google DNS.
 
@@ -32,15 +42,27 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m
 
 To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there.
 
-* To solve this problem, move the certificate to the system certificate store
+:::tip
 
-> Requires root access. 
+To solve this problem, move the certificate to the system certificate store
+
+:::
+
+:::caution
+
+Requires root access.
+
+:::
 
 ### Dolphin Browser: Dolphin Browser, Dolphin Browser Express
 
 AdGuard cannot filter its traffic when operating in **Manual proxy mode** because this browser ignores system proxy settings.
 
-* Use the **Local VPN** filtering mode to solve this problem
+:::tip
+
+Use the **Local VPN** filtering mode to solve this problem
+
+:::
 
 ### Opera mini: Opera mini, Opera mini with Yandex