From 6e67b21dd85320faafe01e8927ff4f1d170e9d15 Mon Sep 17 00:00:00 2001
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 9 May 2024 13:54:24 -0700
Subject: [PATCH] Clarify language

---
 index.html | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/index.html b/index.html
index 4d8d2ca..30671e6 100644
--- a/index.html
+++ b/index.html
@@ -312,13 +312,14 @@ <h2>Negotiation issues</h2>
             the application will negotiate codecs to be sent and received with
             the conferencing server. However, since scalability modes are not
             negotiated in Offer/Answer, the application needs to determine
-            which scalability modes are available by other means.
+            which scalability modes the conference server supports by other
+            means.
           </p>
           <p>  
-            One way in which this can be achieved is for the SFM to provide
-            information on the codecs and scalability modes it can decode in
-            the form of receiver capabilities. After exchanging capabilities,
-            the application can compute the intersection of codecs and
+            One way to handle this is for the SFM to indicate the codecs
+            and scalability modes it can decode in the form of receiver
+            capabilities. After exchanging capabilities, the application
+            can compute the intersection of codecs and
             {{RTCRtpEncodingParameters/scalabilityMode}} values supported
             by the browser's {{RTCRtpSender}} and the
             <a title="Selective Forwarding Middlebox">SFM</a>'s receiver. This