Bug 21525: AudioDestinationNode does not always talk to audio hardware
authorcrogers
Mon, 08 Apr 2013 15:23:47 -0700
changeset 292 d76c9043e607
parent 291 9769f4b94d63
child 293 f4b0a9d88309
Bug 21525: AudioDestinationNode does not always talk to audio hardware
webaudio/specification.html
--- a/webaudio/specification.html	Mon Apr 08 15:12:49 2013 -0700
+++ b/webaudio/specification.html	Mon Apr 08 15:23:47 2013 -0700
@@ -884,8 +884,9 @@
   <dt id="dfn-destination"><code>destination</code></dt>
     <dd><p>An <a
       href="#AudioDestinationNode-section"><code>AudioDestinationNode</code></a>
-      with a single input representing the final destination for all audio (to
-      be rendered to the audio hardware). All AudioNodes actively rendering
+      with a single input representing the final destination for all audio.
+      Usually this will represent the actual audio hardware.
+      All AudioNodes actively rendering
       audio will directly or indirectly connect to <code>destination</code>.</p>
     </dd>
 </dl>
@@ -1503,7 +1504,7 @@
 
 <p>This is an <a href="#AudioNode-section"><code>AudioNode</code></a>
 representing the final audio destination and is what the user will ultimately
-hear. It can be considered as an audio output device which is connected to
+hear. It can often be considered as an audio output device which is connected to
 speakers. All rendered audio to be heard will be routed to this node, a
 "terminal" node in the AudioContext's routing graph. There is only a single
 AudioDestinationNode per AudioContext, provided through the