Merge pull request #698 from AdguardTeam/agm-2450-update-icloud-private-relay-md

[AGM-2450] Update AG for Mac's icloud-private-relay.md

Author: vyanovsky

docs/adguard-for-mac/solving-problems/icloud-private-relay.md

@@ -26,17 +26,17 @@ On Big Sur, AdGuard developed "split-tunnel" rules to avoid creating the "defaul
 
 On Monterey, iCloud Private Relay got introduced. Privacy features of the Mail app also use Private Relay servers.
 
-As a consequence, AdGuard can't work together with iCloud Private Relay and the Mail app privacy features:
+As a consequence, AdGuard can’t work together with iCloud Private Relay and the Mail app privacy features:
 
 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates.
-2. iCloud Private Relay uses QUIC, which AdGuard can't filter in filtered apps because HTTP/3 filtering is not yet available.
-3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic — otherwise, ad blocking is impossible.
-4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari.
-5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically.
+2. iCloud Private Relay is implemented with HTTP/3 CONNECT proxies.
+3. Since AdGuard does not filter CONNECT HTTP/3 requests yet, it attempts to downgrade HTTP/3 proxy connections to HTTP/1.1, which results in blocking iCloud Private Relay traffic.
+4. When you use iCloud Private Relay and switch AdGuard into the Split-Tunnel mode, you can’t open websites in Safari.
+5. To work around this issue for Monterey, we apply the “default route” rule. When Private Relay sees that rule, it disables itself automatically.
 So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled.
 
-`network.extension.monterey.force.split.tunnel` restores the "Big Sur" behavior, but this option may break access to websites due to (3) and (4).
-We keep searching for a solution to this issue. One of the options is implementing HTTP/3 filtering.
+The `network.extension.monterey.force.split.tunnel` option restores the “Big Sur” behavior, but this option may break access to websites due to (3) and (4).
+We keep searching for a solution to this issue. One of the options is implementing HTTP/3 proxy filtering.
 
 ## Recommended solution