Clarified association when reconnect WS connection

TS-0020-WebSocket_Protocol_Binding.md

@@ -375,7 +375,7 @@ The WebSocket server needs to associate a connection with an originator in order
 
 Except in case of the AE registration procedure the client must include the additional `X-M2M-Origin` header field with the *from* request attribute (the request's originator). The registrar must then associate the connection with the provided originator. 
 
-For each originator only one associated WebSocket connection must be kept open by the registrar. If the registrar receives a new WebSocket handshake with an originator in the `X-M2M-Origin` header field for which an already existing established WebSocket connection exists, then the registrar must close the previous existing WebSocket connection. 
+For each originator only one associated WebSocket connection must be kept open by the registrar. If the registrar receives a new WebSocket handshake with an originator in the `X-M2M-Origin` header field for which an already existing established WebSocket connection exists, then the registrar must close the previous existing WebSocket connection and associate the new WebSocket connection with the provided originator. 
 
 If, after the WebSocket connection without a provided `X-M2M-Orgin` header is established, the registrar receives a request over this WebSocket connection and the request is not an AE registration request, then the registrar must return a response with the response status code **ORIGINATOR HAS NO PRIVILEGE**.