Issue70 m line profile names

I think this would be clearer if worded as

For media m= sections, JSEP endpoints MUST support receiving either the "UDP/TLS/RTP/SAVPF" or
"TCP/TLS/RTP/SAVPF" profiles; because ICE can select either TCP or UDP transport depending
 on network conditions, an advertisement for either transport is actually an advertisement for both.
To simplify backwards compatibility, JSEP endpoints must also tolerate receiving any profile containing the string 
 "RTP/", but interpret that as indicating support for both "UDP/TLS/RTP/SAVPF"
 or "TCP/TLS/RTP/SAVPF".  For example, even if "RTP/AVP" is indicated, the endpoint MUST
 assume that the peer is offering SRTP with feedback.

 For data m= sections, JSEP endpoints MUST support receiving the "UDP/TLS/SCTP", "TCP/TLS/SCTP", or
 "DTLS/SCTP" (for backwards compatibility) profiles.