Removing references to legacy packaged apps across extension docs.

chrome/common/extensions/docs/server2/templates/articles/overview.html

 <h1>Overview</h1>
 
-
 <p>
 Once you've finished this page
 and the
 <a href="getstarted.html">Getting Started</a> tutorial,
-you'll be all set to start writing extensions and packaged apps.
-</p>
-
-<p class="caution">
-<strong>Note:</strong>
-<em>Packaged apps</em> are implemented as extensions,
-so unless otherwise stated,
-everything in this page applies to packaged apps.
+you'll be all set to start writing extensions.
 </p>
 
 <h2 id="what">The basics</h2>
 
 <p>
 An extension is a zipped bundle of files&mdash;HTML,
 CSS, JavaScript, images, and anything else you need&mdash;that
 adds functionality to the Google Chrome browser.
 Extensions are essentially web pages,
 and they can use all the
 <a href="api_other.html">APIs that the browser provides to web pages</a>,
 from XMLHttpRequest to JSON to HTML5.
 </p>
 
 <p>
 Extensions can interact with web pages or servers using
 <a href="content_scripts.html">content scripts</a> or
 <a href="xhr.html">cross-origin XMLHttpRequests</a>.
 Extensions can also interact programmatically
 with browser features such as
 <a href="bookmarks.html">bookmarks</a>
 and <a href="tabs.html">tabs</a>.
 </p>
 
 <h3 id="extension-ui">Extension UIs</h3>
 
 <p>
-Many extensions&mdash;but not packaged apps&mdash;add
-UI to Google Chrome in the form of
+Many extensions add UI to Google Chrome in the form of
 <a href="browserAction.html">browser actions</a>
 or <a href="pageAction.html">page actions</a>.
 Each extension can have at most one browser action or page action.
 Choose a <b>browser action</b> when the extension is relevant to most pages.
 Choose a <b>page action</b> when the extension's icon
 should appear or disappear,
 depending on the page.
 </p>
 
 <table class="columns">
@@ skipping 31 matching lines @@
   <td>
     This <a href="samples.html#news">news extension</a>
     features a browser action that,
     when clicked,
     shows a <em>popup</em>.
   </td>
 </tr>
 </table>
 
 <p>
-Extensions (and packaged apps) can also present a UI in other ways,
+Extensions can also present a UI in other ways,
 such as adding to the Chrome context menu,
 providing an options page,
 or using a content script that changes how pages look.
 See the <a href="devguide.html">Developer's Guide</a>
 for a complete list of extension features,
 with links to implementation details
 for each one.
 </p>
 
-
-<h3 id="packagedapp-ui">Packaged app UIs</h3>
-
-<p>
-A packaged app usually presents its main functionality using
-an HTML page that's bundled into the app.
-For example, the following packaged app
-displays a Flash file within an HTML page.
-</p>
-
-<img src="{{static}}/images/overview/flash-app.png"

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

Delete this image file if it's no longer referenced anywhere.

-  width="372" height="300"
-  alt="screenshot" />
-
-<p>
-For more information,
-see <a href="apps.html">Packaged Apps</a>.
-</p>
-
 <h2 id="files">Files</h2>
 <p>
 Each extension has the following files:
 
 </p>
 
 <ul>
   <li>A <b>manifest file</b></li>
   <li>One or more <b>HTML files</b> (unless the extension is a theme)</li>
   <li><em>Optional:</em> One or more <b>JavaScript files</b></li>
@@ skipping 147 matching lines @@
 There are two types of background pages:
 <a href="background_pages.html">persistent background pages</a>,
 and <a href="event_pages.html">event pages</a>. Persistent
 background pages, as the name suggests, are always open.
 Event pages are opened and closed as needed. Unless you absolutely
 need your background page to run all the time, prefer to use
 an event page.
 </p>
 
 <!-- PENDING: Perhaps show a picture of many background page processes.
-  This could build on a figure that shows the process architecture,
-  and perhaps the differences between packaged apps and extensions. -->
+  This could build on a figure that shows the process architecture. -->
 
 <p>
 See <a href="event_pages.html">Event Pages</a>
 and <a href="background_pages.html">Background Pages</a>
 for more details.
 </p>
 
 <h3 id="pages">UI pages</h3>
 
 <p>
@@ skipping 264 matching lines @@
 <h2 id="incognito"> Saving data and incognito mode </h2>
 
 <p>
 Extensions can save data using
 the HTML5 <a href="http://dev.w3.org/html5/webstorage/">web storage API</a>
 (such as <code>localStorage</code>)
 or by making server requests that result in saving data.
 Whenever you want to save something,
 first consider whether it's
 from a window that's in incognito mode.
-By default, extensions don't run in incognito windows,
-and packaged apps <em>do</em>.
+By default, extensions don't run in incognito windows.
 You need to consider what a user expects
-from your extension or packaged app
-when the browser is incognito.
+from your extension when the browser is incognito.
 </p>
 
 <p>
 <em>Incognito mode</em> promises that the window will leave no tracks.
 When dealing with data from incognito windows,
 do your best to honor this promise.
 For example, if your extension normally
 saves browsing history to the cloud,
 don't save history from incognito windows.
 On the other hand, you can store
@@ skipping 40 matching lines @@
 <ul>
   <li> <a href="getstarted.html">Tutorial: Getting Started</a> </li>
   <li> <a href="tut_debugging.html">Tutorial: Debugging</a> </li>
   <li> <a href="devguide.html">Developer's Guide</a> </li>
   <li> <a href="http://dev.chromium.org/developers/design-documents/extensions/samples">Samples</a> </li>
   <li> <a href="http://www.youtube.com/view_play_list?p=CA101D6A85FE9D4B">Videos</a>,
     such as
     <a href="http://www.youtube.com/watch?v=B4M_a7xejYI&feature=PlayList&p=CA101D6A85FE9D4B&index=6">Extension Message Passing</a>
     </li>
 </ul>