Removing references to legacy packaged apps across extension docs.

chrome/common/extensions/docs/server2/templates/intros/ttsEngine.html

 <p id="classSummary">
 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

[Mihai Parparita -not on Chrome, 2012/09/16 04:55:02]

Platform apps can use the tts module, this reference can stay.

-app uses the
+an utterance to be spoken and other parameters when any extension uses the
 <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>
 
 
 <h2 id="overview">Overview</h2>
 
 <p>An extension can register itself as a speech engine. By doing so, it
@@ skipping 126 matching lines @@
 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>