Update README.md

README.md

@@ -87,8 +87,7 @@ the past, to can begin one new experiment/showcase... and then:
 
    Note: we can avoid this heavy part of manual handshake-procedure from our webrtc-chat app using the automation of this process to can "automatically" store in back-end(maybe php-based for e.g.)the content of messeges(the SDPs) in some servers(for eg.  
    db-server based like "MySQL"+"PhP" or maybe one service like "Firebase") and in this-case need/must in backend one external web-[micro]service(which implement protocols like GraphQL/REST, gRPC, SOAP with XML/JSON messenging, eTransport, Websocket, Pub/Sub,... 
-   or UDP/TCP/raw-socket or other/any protocol service with one 
-   exception: webrtc... :) to transport the information exchanged(with or no encryption) between both ends.
+   or UDP/TCP/raw-socket or other/any protocol service,certainly with one exception: webrtc ... :) ... because the implementation of webrtc cannot be based on itself)to transport the information exchanged(with or no encryption) between both ends.
    In this last case(automatic solution), to can comunicate one with other, the ends use the service/server which implement the transport protocol as "shared-memory" implemented as third/broker/intermediate part(as ICE-servers: STUN-like or TURN-like).
    This own complicated task of implementing of third-parts can be done by you or can use(for free or no, with installemnt or no) ready-made solutions( in this case, for free, the ghithub-repositories can be the most good CDN-friend for you :)