Update 0004_ws2p_v1.md

rfc/0004_ws2p_v1.md

@@ -26,7 +26,9 @@ WS2P WS2P is exclusively based on websocket.
 
 ### Endpoint format
 
-`WS2P uuid host port path`
+In the peer card : `WS2P uuid host port path`  
+Resolved in* : `ws://host:port/path`  
+*If the port is `443`, the `wss://` protocol will be used.
 
 uuid := Random sequence of 8 hexadecimal characters. (This uuid makes it possible to identify a Duniter node in a unique way.)  
 host := domain name or ipv4 or ipv6 (it is not possible to declare both an ipv4 and an ipv6, for this it is necessary to use a domain name.)  
@@ -36,7 +38,7 @@ path := Optional access path
 Example of a valid endpoint : `WS2P c1c39a0a g1-monit.librelois.fr 443 ws2p`  
 This endpoint is resolved as follows: `wss://g1-monit.librelois.fr:443/ws2p`
 
-other valid endpoint : `WS2P a0a45ed2 88.174.120.187 20901`  
+Other valid endpoint : `WS2P a0a45ed2 88.174.120.187 20901`  
 This endpoint is resolved as follows: `ws://88.174.120.187:20901`
 
 Any ws2p endpoint  must match this regexp : `/^WS2P (?:[1-9][0-9]* )?([a-f0-9]{8}) ([a-z_][a-z0-9-_.]*|[0-9.]+|[0-9a-f:]+) ([0-9]+)(?: (.+))?$/`