More README updates

Signed-off-by: Alexey Cluster <cluster@cluster.wtf>

Author: ClusterM

README.md

@@ -23,7 +23,7 @@ What started as a quick-and-dirty solution just for personal use has grown into
 * **Cross-Platform and Lightweight**  
   Available as binaries for Linux, Windows, and Mac, as well as tiny multi-arch Docker images (amd64, arm64, arm/v7, arm/v6, 386, ppc64le, s390x). The images are extremely small and suitable even for embedded routers like MikroTik.
 * **Cross-compile ready**  
-  Easily portable and compilable on Linux, macOS, and Windows (MSYS2/MinGW, with automatic fallback to poll()).
+  Easily portable and compilable on Linux, macOS, and Windows (MSYS2/MinGW, with automatic fallback to `poll()`).
 * **Very low dependency footprint**  
   No huge libraries or frameworks.
 * **Android Client Coming Soon?**  
@@ -304,6 +304,8 @@ This allows the remote obfuscator to recognize which static mapping (and which l
 * Peer A’s obfuscator sees a packet coming from `5.6.7.8:8888`.
 * It checks its static bindings (`127.0.0.1:5555:7777`) and knows to deliver the packet to the local WireGuard instance on port `5555`.
 
+Packets sent from Peer B to Peer A follow the exact same steps, but in the reverse order.
+
 #### Summary
 
 With static bindings, each obfuscator knows in advance how to forward packets between the server and local WireGuard, regardless of which peer initiates the connection. This enables fully bidirectional, peer-to-peer WireGuard tunnels—*even if both sides can initiate connections at any time.*