Move Chrome Apps Codelab docs to developer.chrome.com

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

 <h1 id="lab_6_lifecycle">Lab 6 - Lifecycle</h1>
 
 <p>Like everything in this world, apps have a lifecycle.  They are installed, launched, restarted, suspended when the system needs to free up resources and uninstalled.  This lab will show you the basics of the Chrome app lifecycle and how its heart, the event page (aka background script), is used.</p>
 
 <h2 id="you_should_also_read">You should also read</h2>
 
 <p><a href="http://developer.chrome.com/apps/app_lifecycle.html">Manage App Lifecycle</a> in Chrome app docs</p>
 
 <h2 id="the_event_page">The event page</h2>
 
@@ skipping 13 matching lines @@
 
 <p>Execute your app as it is now, move and resize the window, close and restart it. The app will reopen in the original location, right? Now add a property <code>id</code> to the <a href="https://github.com/GoogleChrome/chrome-app-codelab/blob/master/lab6_lifecycle/angularjs/main.js">main.js</a>, reload the app and test again:</p>
 
 <pre><code><pre>
 chrome.app.runtime.onLaunched.addListener(function() {
     chrome.app.window.create(&#39;index.html&#39;,
       {id: &#39;mainwindow&#39;, width: 500, height: 309});
   });
 </pre></code></pre>
 
-If your application requires, you can open more than one window.
+<p>If your application requires, you can open more than one window.</p>
 
 <h2 id="the_onrestarted_event">The onRestarted event</h2>
 
-The $ref:app.runtime.onRestarted event is not as essential as <code>onLaunched</code>, but it might be relevant to certain types of apps.
+<p>The $ref:app.runtime.onRestarted event is not as essential as <code>onLaunched</code>, but it might be relevant to certain types of apps.
 This event is executed when the app is restarted, for example, when Chrome quits, restarts, and the app is launched again.
-You can use this event to restore a transient state. 
+You can use this event to restore a transient state. </p>
 
-For example, if your app has a form with several fields, you won&#39;t always want to save the partial form while the user is typing.
+<p>For example, if your app has a form with several fields, you won&#39;t always want to save the partial form while the user is typing.
 If the user quits the app on purpose, she might not be interested keeping the partial data.
-If the Chrome runtime restarted for some reason other than by a user&#39;s intention, the user will want that data when the app is restarted.
+If the Chrome runtime restarted for some reason other than by a user&#39;s intention, the user will want that data when the app is restarted.</p>
 
-Let&#39;s change our code to save the Todo input field in $ref:storage as the user types, only restoring it if the <code>onRestarted</code> event is triggered.
+<p>Let&#39;s change our code to save the Todo input field in $ref:storage as the user types, only restoring it if the <code>onRestarted</code> event is triggered.</p>
 
 <p class="note"><b>Note:</b>  We learned about <code>chrome.storage.sync</code> before, but <a href="http://developer.chrome.com/trunk/apps/storage.html#using-sync">chrome.storage.local</a> wasn&#39;t mentioned until now. Both have exactly the same syntax, but the semantics of <code>chrome.storage.local</code> is, as the name says, completely local.
 There&#39;s no attempt to synchronize or to save the data in the cloud.</p>
 
 <ul>
 <li>Event page: <a href="https://github.com/GoogleChrome/chrome-app-codelab/blob/master/lab6_lifecycle/angularjs/main.js">main.js</a>
 <pre>
 chrome.app.runtime.onLaunched.addListener(function() {
   // normal launch initiated by the user, let&#39;s start clean.
   // note that this is not related to the persistent state, which is
@@ skipping 48 matching lines @@
     saveTransientState();<br>
   })
 })
 </pre></p></li><li><p>Save the changes by reloading the app: open the app, right-click and select Reload.</p></li>
 </ul>
 
 <p>If Chrome and the app shuts down for any reason (other than a user-gesture), the <code>onRestarted</code> event is fired.
 Any text entered in the input field (but not yet saved as a Todo item) will reappear when Chrome and the app are reopened.</p>
 
 <p class="note"><b>Note:</b>  If you get stuck and want to see the app in action, go to <code>chrome://extensions</code>,
-load the unpacked <a href="app_codelab6_lifecycle.html">lab6_lifecycle</a>, and launch the app from a new tab.</p>
+load the unpacked <a href="https://github.com/GoogleChrome/chrome-app-codelab/tree/master/lab6_lifecycle">lab6 app</a>, and launch the app from a new tab.</p>
 
 <h1 id="takeaways_">Takeaways:</h1>
 
 <ul>
 <li>The event page may continue to run even when your windows are closed. You can move logic that is shared among windows to the event page, as we will see in <a href="app_codelab9_multipleviews.html">lab9</a>.</li>
 </ul>
 
 <h1 id="what_39_s_next_">What&#39;s next?</h1>
 
 <p>In <a href="app_codelab7_useridentification.html">lab7_useridentification</a>,
 you will learn how to identify users and use OAuth2.0 to access Google and other third party services.</p>
 
 <p class="note"><b>Note:</b>  The <a href="http://developer.chrome.com/trunk/apps/app_identity.html">identify API</a> covered in lab 7 is still experimental.</p>