Move the tts and ttsEngine APIs out of experimental, and give

chrome/common/extensions/docs/static/ttsEngine.html

 <p id="classSummary">
-Use the <code>chrome.experimental.ttsEngine</code> module to
+Use the <code>chrome.ttsEngine</code> module to
 implement a text-to-speech (TTS) engine using an extension. If your
 extension registers using this API, it will receive events containing
 an utterance to be spoken and other parameters when any extension or packaged
 app uses the
-<a href="experimental.tts.html">experimental.tts</a>
+<a href="tts.html">tts</a>
 module to generate speech. Your extension can then use any available
 web technology to synthesize and output the speech, and send events back
 to the calling function to report the status.
 </p>
 
 <p class="note"><b>Give us feedback:</b> If you have suggestions,
 especially changes that should be made before stabilizing the first
 version of this API, please send your ideas to the
 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions">chromium-extensions</a>
 group.</p>
 
 <h2 id="overview">Overview</h2>
 
-<p>To enable this experimental API, visit
-<b>chrome://flags</b> and enable <b>Experimental Extension APIs</b>.
-
 <p>An extension can register itself as a speech engine. By doing so, it
 can intercept some or all calls to functions such as
-<a href="experimental.tts.html#method-speak"><code>speak()</code></a> and
-<a href="experimental.tts.html#method-stop"><code>stop()</code></a>
+<a href="tts.html#method-speak"><code>speak()</code></a> and
+<a href="tts.html#method-stop"><code>stop()</code></a>
 and provide an alternate implementation.
 Extensions are free to use any available web technology
 to provide speech, including streaming audio from a server, HTML5 audio,
 Native Client, or Flash. An extension could even do something different
 with the utterances, like display closed captions in a pop-up window or
 send them as log messages to a remote server.</p>
 
 <h2 id="manifest">Manifest</h2>
 
-<p>To implement a TTS engine, an extension must first declare all voices
+<p>To implement a TTS engine, an extension must
+declare the "ttsEngine" permission and then declare all voices
 it provides in the extension manifest, like this:</p>
 
 <pre>{
   "name": "My TTS Engine",
   "version": "1.0",
-  <b>"permissions": ["experimental"],
+  <b>"permissions": ["ttsEngine"],
   "tts_engine": {
     "voices": [
       {
         "voice_name": "Alice",
         "lang": "en-US",
         "gender": "female",
         "event_types": ["start", "marker", "end"]
       },
       {
         "voice_name": "Pat",
@@ skipping 60 matching lines @@
   <li><code>'error'</code>: An engine-specific error occurred and
           this utterance cannot be spoken.
           Pass more information in <code>event.errorMessage</code>.
 </ul>
 
 <p>The <code>'interrupted'</code> and <code>'cancelled'</code> events are
 not sent by the speech engine; they are generated automatically by Chrome.</p>
 
 <p>Text-to-speech clients can get the voice information from your
 extension's manifest by calling
-<a href="experimental.tts.html#method-getVoices">getVoices()</a>,
+<a href="tts.html#method-getVoices">getVoices()</a>,
 assuming you've registered speech event listeners as described below.</p>
 
 <h2 id="handling_speech_events">Handling speech events</h2>
 
 <p>To generate speech at the request of clients, your extension must
 register listeners for both <code>onSpeak</code> and <code>onStop</code>,
 like this:</p>
 
 <pre>var speakListener = function(utterance, options, sendTtsEvent) {
   sendTtsEvent({'event_type': 'start', 'charIndex': 0})
 
   // (start speaking)
 
   sendTtsEvent({'event_type': 'end', 'charIndex': utterance.length})
 };
 
 var stopListener = function() {
   // (stop all speech)
 };
 
-chrome.experimental.ttsEngine.onSpeak.addListener(speakListener);
-chrome.experimental.ttsEngine.onStop.addListener(stopListener);</pre>
+chrome.ttsEngine.onSpeak.addListener(speakListener);
+chrome.ttsEngine.onStop.addListener(stopListener);</pre>
 
 <p class="warning">
 <b>Important:</b>
 If your extension does not register listeners for both
 <code>onSpeak</code> and <code>onStop</code>, it will not intercept any
 speech calls, regardless of what is in the manifest.</p>
 
 <p>The decision of whether or not to send a given speech request to an
 extension is based solely on whether the extension supports the given voice
 parameters in its manifest and has registered listeners
 for <code>onSpeak</code> and <code>onStop</code>. In other words,
 there's no way for an extension to receive a speech request and
 dynamically decide whether to handle it.</p>