Move chrome.experimental.app.onLaunched event handler to chrome.app.runtime.onLaunched.

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

 <h1>Embed Content</h1>
 
 
 <p>
 The <a href="app_architecture.html#security">packaged apps security model</a> disallows
 external content in iframes and
 the use of inline scripting and <code>eval()</code>.
 You can override these restrictions,
 but your external content must be isolated from the app.
 </p>
@@ skipping 161 matching lines @@
 
 <p>
 Just like any other app pages,
 you can create a window that the sandboxed page opens in.
 Here's a sample that creates two windows,
 one for the main app window that isn't sandboxed,
 and one for the sandboxed page:
 </p>
 
 <pre>
-chrome.experimental.app.onLaunched.addListener(function() {
+chrome.app.runtime.onLaunched.addListener(function() {
   chrome.app.window.create('window.html', {
     'width': 400,
     'height': 400,
     'left': 0,
     'top': 0
   });
 
   chrome.app.window.create('sandboxed.html', {
     'width': 400,
     'height': 400,
@@ skipping 36 matching lines @@
 You can use <code>postMessage</code> to communicate
 between your app and sandboxed content.
 Here's a sample background script
 that posts a message to the sandboxed page it
 opens:
 </p>
 
 <pre>
 var myWin = null;
 
-chrome.experimental.app.onLaunched.addListener(function() {
+chrome.app.runtime.onLaunched.addListener(function() {
   chrome.app.window.create('sandboxed.html', {
     'width': 400,
     'height': 400
   }, function(win) {
        myWin = win;
        myWin.postMessage('Just wanted to say hey.', '*');
      });
 });
 </pre>
 
@@ skipping 22 matching lines @@
 
 <pre>
 var messageHandler = function(e) {
   console.log('Background script says hello.', e.data);
 };
 
 window.addEventListener('message', messageHandler);
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>