Cleaning up apps codelab

chrome/common/extensions/docs/templates/articles/develop_apps.html

 <h1>Before You Start</h1>
 
-
 <p>
 This documentation tells you how to write packaged apps.
 All developers, however, should know that the new APIs
 for packaged apps are being released as a developer preview.
 This means that they are evolving daily,
 and anything you read now might be different in the near future.
 Please keep up to date with the API reference and documentation.
-If you hit any stumbling blocks,
-feedback is welcome at
-<a href="http://groups.google.com/a/chromium.org/group/chromium-apps">#chromium-apps</a>
 </p>
 
 <p class="caution">
 <b>Note:</b>
 If you've written packaged apps before,
 your <a href="http://developer.chrome.com/trunk/extensions/apps.html">legacy packaged apps</a>
 will still work the way they always have,
 but they won't have access to the new APIs.
 </p>
 
+<h2 id="common">Common platform</h2>
+
+<p>
+Packaged apps and extensions share a common platform.
+They can access many of the same APIs and
+they have the same manifest and permissions format.
+If you're familiar with the
+<a href="http://developer.chrome.com/extensions/">Chrome Extension docs</a>,
+then the Reference docs should seem familiar.
+Many of the reference docs are shared;
+we've filtered accessibility to docs that aren't.
+</p>
+
 <h2 id="start">Where to start</h2>
 
+<ul>
+  <li>Read the
+  <a href="about_apps.html">Getting Started</a> guide.</li>
+  <li>Follow the
+  <a href="app_codelab.html">Todo App Codelab</a>.</li>
+  <li>Check out the
+  <a href="api_index.html">Chrome JavaScript APIs</a>.</li>
+  <li>Fork any and all
+  <a href="https://github.com/GoogleChrome/chrome-app-samples">chrome-app-samples</a> and make something of your own.</li>
+  <li>Watch the
+<a href="https://developers.google.com/live/chrome/">Chrome Apps GDL sessions</a>.</li>
+</ul>
+
+<h2 id="help">Send feedback!</h2>
+
 <p>
-The <a href="about_apps.html">Getting Started</a> guide is a great place to start.
-It's fast reading; shouldn't take more than 10 minutes to read all three docs.
-After the Getting Started guide,
-decide what's most relevant to you.
-The <a href="app_lifecycle.html">Fundamentals</a> guide covers
-the details of the app and data lifecycle,
-or learn more about good app design
-by reading <a href="app_frameworks.html">MVC Architecture</a>.
-We've also got lots of sample code in our repository
-that is linked to directly from the documentation.
+For Chrome packaged apps to succeed,
+we need and want your feedback.
+You can enter feedback at the
+<a href="https://groups.google.com/a/chromium.org/group/chromium-apps">chromium-apps group</a>,
+file a bug at the
+<a href="http://crbug.com/new">official issue tracker</a>,
+or press "Send Feedback" at the bottom of every doc page.
 </p>
 
-<p>
-If you're familiar with the Chrome extension docs,
-then the Reference docs should seem familiar.
-Packaged apps and extensions share a common platform.
-They can access many of the same APIs,
-they have the same manifest and permissions format.
-Many of the reference docs are shared;
-we've filtered accessibility to docs that aren't shared.
-</p>
-
-<p class="backtotop"><a href="#top">Back to top</a></p>
+<p class="backtotop"><a href="#top">Back to top</a></p>