Fix RTSP docs and add a missing release note

* Add release note for `RtspMediaSource.Factory.setTimeoutMs()`
* Remove mention of what we don't support (any such list is necessarily non-exhaustive)
* Remove markdown quote character ('>')

PiperOrigin-RevId: 385143574

RELEASENOTES.md

@@ -160,6 +160,8 @@
         ([#9014](https://github.com/google/ExoPlayer/issues/9014)).
         ([#9014](https://github.com/google/ExoPlayer/issues/9014)).
     *   Allow using absolute URI in the control attribute in a media description
     *   Allow using absolute URI in the control attribute in a media description
         ([#9183](https://github.com/google/ExoPlayer/issues/9183)).
         ([#9183](https://github.com/google/ExoPlayer/issues/9183)).
+    *   Allow the timeout to be customised via
+        `RtspMediaSource.Factory.setTimeoutMs`.
 *   Metadata:
 *   Metadata:
     *   Fix handling of emsg messages with an unset duration
     *   Fix handling of emsg messages with an unset duration
         ([#9123](https://github.com/google/ExoPlayer/issues/9123)).
         ([#9123](https://github.com/google/ExoPlayer/issues/9123)).

docs/_page_fragments/supported-formats-rtsp.md

@@ -10,5 +10,3 @@ types are listed below.
 **Supported network types**
 **Supported network types**
 * RTP over UDP unicast (multicast is not supported).
 * RTP over UDP unicast (multicast is not supported).
 * Interleaved RTSP, RTP over RTSP using TCP.
 * Interleaved RTSP, RTP over RTSP using TCP.
-
-> Playback of RTP streams is not supported.

docs/rtsp.md

@@ -68,10 +68,10 @@ The timeout for retrying with TCP can be customized by calling the method
 four seconds, the player will retry with TCP after four seconds of UDP
 four seconds, the player will retry with TCP after four seconds of UDP
 inactivity.
 inactivity.
 
 
-> Setting the timeout also affects the end-of-stream detection logic. That is,
+Setting the timeout also affects the end-of-stream detection logic. That is,
 ExoPlayer will report the playback has ended if nothing is received for the
 ExoPlayer will report the playback has ended if nothing is received for the
-duration of the set timeout. Setting this value too small may lead to pre-mature
-stream ending under poor network conditions.
+duration of the set timeout. Setting this value too small may lead to an early
+end-of-stream signal under poor network conditions.
 
 
 ### Force using RTP/TCP ###
 ### Force using RTP/TCP ###
 ExoPlayer can also be configured to play with RTP/TCP by default. To do so,
 ExoPlayer can also be configured to play with RTP/TCP by default. To do so,