Removing references to legacy packaged apps across extension docs.

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

Index: chrome/common/extensions/docs/server2/templates/articles/overview.html
diff --git a/chrome/common/extensions/docs/server2/templates/articles/overview.html b/chrome/common/extensions/docs/server2/templates/articles/overview.html
index f193d6b30b5874e0d676eb7a82ac1cb40c93568f..b499092f735c880eb048dd609721b287eb5574ad 100644
--- a/chrome/common/extensions/docs/server2/templates/articles/overview.html
+++ b/chrome/common/extensions/docs/server2/templates/articles/overview.html
@@ -1,18 +1,10 @@
 <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>
@@ -40,8 +32,7 @@ and <a href="tabs.html">tabs</a>.
 <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.
@@ -93,7 +84,7 @@ depending on the page.
 </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.
@@ -103,25 +94,6 @@ 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:
@@ -289,8 +261,7 @@ 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>
@@ -575,11 +546,9 @@ 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>