Reference 2013 Google IO Chrome Apps presentation from apps doc.

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

 <meta name="doc-family" content="apps">
 <h1>What Are Chrome Apps?</h1>
 
 <p>
 Chrome Apps deliver an experience as capable as a native app,
 but as safe as a web page.
 Just like web apps,
 Chrome Apps are written in HTML5, JavaScript, and CSS.
 But Chrome Apps look and behave like native apps,
 and they have native-like capabilities
@@ skipping 11 matching lines @@
 examples:
 </p>
 
 <ul>
         <li>Shells (VMWare, Citrix, SSH, RDP or VNC clients)</li>
         <li>Music/video streaming</li>
         <li>Photo/video/music editing</li>
 </ul>
 
 <p>
-Watch the <a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">Chrome Apps
-Google I/O presentation</a> for an in-depth introduction.
+Watch the Chrome Apps<strong>
+<a href="http://www.youtube.com/watch?v=j8oFAr1YR-0">2012</a>
+and
+<a href="http://www.youtube.com/watch?v=f2tJRXDTMuY">2013</a>
+Google I/O presentations</strong> for an in-depth introduction.
 </p>
 
 <h2 id="look">How they look</h2>
 
 <p>
 When a user opens a Chrome App,
 their focus is specifically on the tasks
 relating to the app.
 Chrome Apps have no traditional chrome:
 the omnibox (address bar), tab strip,
@@ skipping 63 matching lines @@
                 shows how to use the powerful network and hardware APIs.
         </li>
         <li>
                 <a href="app_deprecated.html">Disabled Features</a>
                 describes the web features that have been disabled
                 and what to use in their place, where relevant.
         </li>
 </ul>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>