diff --git a/README.md b/README.md
index 133f002..94c18a8 100644
--- a/README.md
+++ b/README.md
@@ -254,13 +254,12 @@ we transparently direct traffic to the target host!
 - We consider this a breakthrough aspect, which has no stable analogues today
 - Based on this: if `telemt` configured correctly, **TLS mode is completely identical to real-life handshake + communication** with a specified host
 - Here is our evidence:
-  - 212.220.88.77 - "dummy" host, running `telemt`
-  - `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275`
-  - client WITH secret-key accesses the MTProxy resource:
+    - 212.220.88.77 - "dummy" host, running `telemt`
+    - `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275`
+  1) client WITH secret-key accesses the MTProxy resource:
   <img width="360" height="439" alt="telemt" src="https://github.com/user-attachments/assets/39352afb-4a11-4ecc-9d91-9e8cfb20607d" />
-
   
-  - client WITHOUT secret-key gets transparent access to the specified resource:
+  2) client WITHOUT secret-key gets transparent access to the specified resource:
     - with trusted certificate
     - with original handshake
     - with full request-response way