Fixing path to chrome app samples in documentation

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

 <meta name="doc-family" content="apps">
 <h1>Create Your First App</h1>
 
 
 <p>
 This tutorial walks you through creating your first Chrome App.
 Chrome Apps are structured similarly to extensions
 so current developers will recognize the manifest and packaging methods.
 When you're done,
 you'll just need to produce a zip file of your code and assets
@@ skipping 12 matching lines @@
   <li>All code must be included in the Chrome App package. This includes HTML, JS, CSS
     and Native Client modules.</li>
   <li>All <strong>icons</strong> and other assets must be included
     in the package as well.</li>
 </ul>
 
 <p class="note">
 <b>API Samples: </b>
 Want to play with the code?
 Check out the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/hello-world">hello-world</a>
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/hello-world">hello-world</a>
 sample.
 </p>
 
 <h2 id="one">Step 1: Create the manifest</h2>
 
 <p>
 First create your <code>manifest.json</code> file
 (<a href="manifest">Formats: Manifest Files</a>
 describes this manifest in detail):
 </p>
@@ skipping 135 matching lines @@
   </li>
   <li>
     <code>--app-id=ajjhbohkjpincjgiieeomimlgnll</code> launches an app
     already loaded into Chrome. It does not restart any previously running
     app, but it does launch the new app with any updated content.
   </li>
 </ul>
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>