From 0ee71a59a021dcf2bbf5fd1e454db772a8b1b650 Mon Sep 17 00:00:00 2001
From: Alexey <247128645+axkurcom@users.noreply.github.com>
Date: Wed, 31 Dec 2025 05:44:48 +0300
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0f633f0..37f9bd3 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ WantedBy=multi-user.target
 ### Telegram Calls via MTProxy
 - Telegram architecture does **NOT allow calls via MTProxy**, but only via SOCKS5, which cannot be obfuscated
 ### How does DPI see MTProxy TLS?
-- DPI sees MTProxy in Fake TLS mode as TLS
+- DPI sees MTProxy in Fake TLS (ee) mode as TLS 1.3
 - the SNI you specify sends both the client and the server;
 - ALPN is similar to HTTP 1.1/2;
 - high entropy, which is normal for AES-encrypted traffic;