Adding the interrupted state

Author: gabrielsanbrito

index.bs

@@ -718,7 +718,8 @@ for="BaseAudioContext">[[control thread state]]</dfn> that take values from
 enum AudioContextState {
     "suspended",
     "running",
-    "closed"
+    "closed",
+    "interrupted"
 };
 </pre>
 
@@ -746,6 +747,12 @@ enum AudioContextState {
             <td>
                 This context has been released, and can no longer be used to
                 process audio. All system audio resources have been released.
+        <tr>
+            <td>
+                "<dfn>interrupted</dfn>"
+            <td>
+                This context is currently interrupted and cannot process audio
+                until the interruption ends.
 </table>
 </div>
 
@@ -11534,7 +11541,7 @@ and a <a>rendering thread</a>.
 
 The <dfn>control thread</dfn> is the thread from which the
 {{AudioContext}} is instantiated, and from which authors
-manipulate the audio graph, that is, from where the operation on a
+manipulate the audio graph, that is, from where the operations on a
 {{BaseAudioContext}} are invoked. The <dfn>rendering thread</dfn>
 is the thread on which the actual audio output is computed, in
 reaction to the calls from the <a>control thread</a>. It can be a
@@ -11641,7 +11648,7 @@ The algorithm for rendering a block of audio from a {{BaseAudioContext}}
 in the algorithm of <a href="#rendering-a-graph">rendering a graph</a>.
 
 The {{AudioContext}} <a>rendering thread</a> is driven by a
-<dfn>system-level audio callback</dfn>, that is periodically 
+<dfn>system-level audio callback</dfn>, that is periodically called
 at regular intevals. Each call has a <dfn>system-level audio callback buffer
 size</dfn>, which is a varying number of sample-frames that needs to be
 computed on time before the next <a>system-level audio callback</a> arrives.