Section 3.2.2: Clarify Use Case

Fix for #103

index.html

@@ -303,12 +303,11 @@ <h4>Game streaming</h4>
 transported using RTP or RTCDataChannel.</p>
 </section> 
 <section id="auction">
-   <h4>Low latency Broadcast with Fanout</h4>
-   <p>There are streaming applications that require large scale as well as low latency.
-   Examples include sporting events, church services, webinars and company 'Town Hall' meetings.
-   Live audio, video and data is sent to thousands (or even millions) of recipients.
-   Limited interactivity may be supported, such as allowing authorized participants to ask
-   questions at a company meeting. Both the media sender and receivers may be behind a NAT.
+   <h4>Ultra Low latency Broadcast with Fanout</h4>
+   <p>There are streaming applications that require large scale as well as ultra low latency.
+   Examples include sporting events, auctions and financial news. Live audio, video and data is sent to
+   thousands (or even millions) of recipients. Limited interactivity may be supported, such as
+   capturing video or audio from auction bidders. Both the media sender and receivers may be behind a NAT.
    P2P relays may be used to improve scalability, potentially using different transport than
    the original stream.</p>
    <p class="note">This use case has completed a Call for Consensus (CfC) [[?CFC-Low-Latency]] but has unresolved issues.</p>
@@ -336,7 +335,7 @@ <h4>Low latency Broadcast with Fanout</h4>
         </tr>
     </tbody>
 </table>
-<p>Experience: |pipe|, Peer5 and Dolby are examples of this use case, with media
+<p>Experience: |pipe| and Dolby are examples of this use case, with media
 transported via RTP or RTCDataChannel.</p>
 </section>
 </section>