Remove mention of special automatic tunnel protocol logic on Windows,

and other vestiges

1 files changed, 3 insertions, 9 deletions

diff --git a/docs/relay-selector.md b/docs/relay-selector.md
index 4db6700f1d..a4c4b8a249 100644
--- a/docs/relay-selector.md
+++ b/docs/relay-selector.md
@@ -49,15 +49,9 @@ Endpoints may be filtered by:
 Whilst all user selected constraints are always honored, when the user hasn't selected any specific
 constraints, following default ones will take effect:
 
-- If no tunnel protocol is specified for tunnel endpoints, then the behavior is different on Windows
-  and other platforms.
-  - On MacOS and Linux, first two connection attempts will use WireGuard, over a random port at
-    first and then port 53. From the third attempt onwards, OpenVPN will be used, alternating
-    between UDP on any port and TCP on port 443.
-  - On Windows, a migration to WireGuard is ongoing and a percentage value provided by the API tells
-    clients to randomly decide if they will use WireGuard as a default or OpenVPN as a default.
-    The client's decision will persist over time.
-    If the client decides to use WireGuard it will have the same behavior as MacOS and Linux.
+- If no tunnel protocol is specified, the first two connection attempts will use WireGuard, over a
+  random port at first and then port 53. From the third attempt onwards, OpenVPN will be used,
+  alternating between UDP on any port and TCP on port 443.
 
 - If the tunnel protocol is specified as WireGuard and obfuscation mode is set to _Auto_:
   - First two attempts will be used without _udp2tcp_, using a random port on first attempt, and