Harmonize capitalization and hyphenization

close #2585

webrtc.html

@@ -4,7 +4,7 @@
     <meta charset="utf-8">
     <link href="webrtc.css" rel="stylesheet">
     <title>
-      WebRTC 1.0: Real-time Communication Between Browsers
+      WebRTC 1.0: Real-Time Communication Between Browsers
     </title>
     <script class="remove" src="respec-w3c-common.js" type="text/javascript">
     // // keep this comment //
@@ -17417,7 +17417,7 @@ <h2>
         </h2>
         <p>
           This document extends the Web platform with the ability to set up
-          real time, direct communication between browsers and other devices,
+          real-time, direct communication between browsers and other devices,
           including other browsers.
         </p>
         <p>
@@ -17592,15 +17592,15 @@ <h2>
       <p>
         The Telecommunications Device for the Deaf (TDD/TTY) enables
         individuals who are hearing or speech impaired (among others) to
-        communicate over telephone lines. Real-time Text, defined in
+        communicate over telephone lines. Real-Time Text, defined in
         [[RFC4103]], utilizes T.140 encapsulated in RTP to enable the
         transition from TDD/TTY devices to IP-based communications, including
         emergency communication with <a href=
         "https://www.ecfr.gov/cgi-bin/text-idx?SID=ada7cebd65433a9e05c35426a2bc76b8&amp;mc=true&amp;node=pt47.3.67&amp;rgn=div5">
         Public Safety Access Points (PSAP)</a>.
       </p>
       <p>
-        Since Real-time Text requires the ability to send and receive data in
+        Since Real-Time Text requires the ability to send and receive data in
         near real time, it can be best supported via the WebRTC 1.0 data
         channel API. As defined by the IETF, the data channel protocol utilizes
         the SCTP/DTLS/UDP protocol stack, which supports both reliable and
@@ -17612,7 +17612,7 @@ <h2>
         Since the IETF chose a different approach than the RTP data channel as
         part of the WebRTC suite of protocols, as of the time of this
         publication there is no standardized way for the WebRTC APIs to
-        directly support Real-time Text as defined at IETF and implemented in
+        directly support Real-Time Text as defined at IETF and implemented in
         U.S. (FCC) regulations. The WebRTC working Group will evaluate whether
         the developing IETF protocols in this space warrant direct exposure in
         the browser APIs and is looking for input from the relevant user
@@ -17624,7 +17624,7 @@ <h2>
         "https://tools.ietf.org/html/draft-holmberg-mmusic-t140-usage-data-channel">
         Real-time text to be sent over the WebRTC data channel</a>, allowing
         gateways to be deployed to translate between the SCTP data channel
-        protocol and RFC 4103 Real-time text. This work, once completed, is
+        protocol and RFC 4103 Real-Time Text. This work, once completed, is
         expected to enable a unified and interoperable approach for integrating
         real-time text in WebRTC user-agents (including browsers) - through a
         gateway or otherwise.
@@ -17634,7 +17634,7 @@ <h2>
         support in WebRTC clients can be developed e.g. through a custom WebRTC
         data channel. This is deemed sufficient until such time as future
         standardized gateways are enabled via IETF protocols such as the SCTP
-        data channel protocol and RFC 4103 Real-time text. This will need to be
+        data channel protocol and RFC 4103 Real-Time Text. This will need to be
         defined at IETF in conjunction with related work at W3C groups to
         effectively and consistently standardise RTT support internationally.
       </p>