Update the spec to refer to the new activation mechanism in HTML

This is intentionaly vague to not restrict implementors: it's plausible
that an implementation chooses to be transient or sticky here.

This fixes #2107.

Address comments from Marcos

Don't use explicit link, and follow the guideline in https://github.com/whatwg/html/issues/5129\#issuecomment-562210730

index.bs

@@ -1324,9 +1324,10 @@ interface AudioContext : BaseAudioContext {
 </xmp>
 
 An {{AudioContext}} is said to be <dfn>allowed to start</dfn> if the user agent
-allows the context state to transition from "{{AudioContextState/suspended}}" to "{{AudioContextState/running}}". A user
-agent may require the actual audio production from an {{AudioContext}} to be
-<a>triggered by user activation</a> (as described in [[HTML]]).
+allows the context state to transition from "{{AudioContextState/suspended}}" to
+"{{AudioContextState/running}}". A user agent may delay this initial transition,
+to allow it only when the {{AudioContext}}'s [=relevant global object=] has
+[=sticky activation=] or [=transient activation=].
 
 {{AudioContext}} has an internal slot: