Confusingly redundant prose in § 4.3.1 Life-cycle and Media Flow

[jan-ivar]

The section § 4.3.1 Life-cycle and Media Flow has two subsections:

• § 4.3.1.1 Life-cycle, which one might expect to cover readyState and the ended event
• § 4.3.1.2 Media Flow, which one might expect to cover the muted and enabled states and events

Unfortunately, § 4.3.1.1 Life-cycle jumps the gun, describing fundamental aspects of muted and enabled, like "A muted or disabled MediaStreamTrack renders either silence (audio), black frames (video), or a zero-information-content equivalent." ahead of the section that defines it.

As one measure, there are 20 hits for "muted" in § 4.3.1.1 Life-cycle vs 17 hits in § 4.3.1.2 Media Flow.

To be fair, there's one camera and microphone-specific lifecycle-aspect to muted/disabled, which is that UAs MAY temporarily relinquish devices (Firefox does this on some platforms). This is probably how the muted/disabled concept snuck into the lifecycle section. But this was meant to be an implementation optimization not meant to disturb the API model, so it may be better to discuss it in 4.3.1.2.

This might be good to clean up.