Amend TODOs

Signed-off-by: Šimon Brandner <simon.bra.ag@gmail.com>

proposals/3898-sfu.md

@@ -16,10 +16,8 @@ which other SFUs to connect.
 
 ## Proposal
 
-**TODO: spell out how this works with active speaker detection & associated
-signalling** **TODO: spell out how the DC traffic interacts with
-application-layer traffic** **TODO: how do we prove to the SFU that we have the
-right to subscribe to track?**
+- **TODO: spell out how this works with active speaker detection & associated
+signalling**
 
 ### Diagrams
 
@@ -78,7 +76,7 @@ this field from the state event or leave the list empty.
 
 #### Discovering foci
 
-**TODO: How does a client discover foci? We could use well-known or a custom endpoint**
+- **TODO: How does a client discover foci? We could use well-known or a custom endpoint**
 
 Foci are identified by a tuple of `user_id` and `device_id`.
 
@@ -155,9 +153,12 @@ The client uses the established data channel connection to the SFU to perform
 low-latency signalling to rapidly (un)subscribe/(un)publish streams, send
 keep-alive messages, metadata, cascade and perform re-negotiation.
 
-**TODO: It feels like these ought to be `m.` namespaced** **TODO: Why `op`
-instead of `type`?** **TODO: It feels like these ought to have `content` rather
-than being on the same layer**
+- **TODO: It feels like these ought to be `m.` namespaced**
+- **TODO: Why `op` instead of `type`?**
+- **TODO: It feels like these ought to have `content` rather than being on the
+  same layer**
+- **TODO: Spell out how the DC traffic interacts with application-layer
+traffic**
 
 #### SDP Stream Metadata extension
 
@@ -204,6 +205,9 @@ If the user for example switches from "spotlight" (one large tile) to "grid"
 (multiple small tiles) view, it should also send this request to let the SFU
 know of the resolution change.
 
+- **TODO: how do we prove to the SFU that we have the right to subscribe to
+track?**
+
 ```json
 {
     "op": "subscribe",