--- a/webaudio/specification.html	Tue Oct 02 12:28:55 2012 -0700
+++ b/webaudio/specification.html	Tue Oct 02 12:33:36 2012 -0700
@@ -1633,7 +1633,7 @@
 
 interface <dfn id="dfn-AudioGainNode">AudioGainNode</dfn> : AudioNode {
 
-    AudioGain gain;
+    AudioParam gain;
 
 };
 </code></pre>
@@ -1644,7 +1644,7 @@
 <h3 id="attributes-AudioGainNode">4.7.1. Attributes</h3>
 <dl>
   <dt id="dfn-gain"><code>gain</code></dt>
-    <dd><p>An AudioGain object representing the amount of gain to apply. Its
+    <dd><p>Represents the amount of gain to apply. Its
       default <code>value</code> is 1 (no gain change). The nominal <code>minValue</code> is 0, but may be
       set negative for phase inversion.  The nominal <code>maxValue</code> is 1, but higher values are allowed (no
       exception thrown).This parameter is <em>a-rate</em> </p>
@@ -2122,8 +2122,8 @@
     attribute float coneOuterGain;
 
     <span class="comment">// Dynamically calculated gain values </span>
-    readonly attribute AudioGain coneGain;
-    readonly attribute AudioGain distanceGain;
+    readonly attribute AudioParam coneGain;
+    readonly attribute AudioParam distanceGain;
 
 };
 </code></pre>
@@ -3397,7 +3397,7 @@
     <span class="comment">// We now have explicit control over all the volumes g1_1, g2_1, ..., s1, s2 </span>
     g2_1.gain.value = 0.2; <span class="comment"> // For example, set source1 reverb gain </span>
 
-    <span class="comment"> // Because g2_1.gain is of type "AudioGain" which is an "AudioParam", </span>
+    <span class="comment"> // Because g2_1.gain is an "AudioParam", </span>
     <span class="comment"> // an automation curve could also be attached to it. </span>
     <span class="comment"> // A "mixing board" UI could be created in canvas or WebGL controlling these gains. </span>
 }