Fixing path to chrome app samples in documentation

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

 <h1>Storage APIs</h1>
 
 <p>
 Almost every aspect of app development involves some element
 of sending or receiving data.
 Starting with the basics,
 you should use an MVC framework to help you design and implement your app
 so that data is completely separate from the app's view on that data
 (see <a href="app_frameworks">MVC Architecture</a>).
 </p>
 
 <p>
 You also need to think about how data is handled when your app is offline
 (see <a href="offline_apps">Offline First</a>).
 This doc briefly introduces the storage options
 for sending, receiving, and saving data locally;
 the remainder of the doc shows you how
 to use Chrome's File System and Sync File System APIs
 (see also <a href="fileSystem">fileSystem API</a> and
 <a href="syncFileSystem">syncFileSystem API</a>).
 </p>
 
 <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/filesystem-access">filesystem-access</a>,
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/syncfs-editor">syncfs-editor</a>
-and <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/storage">storage</a> samples.
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/filesystem-access">filesystem-access</a>,
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/syncfs-editor">syncfs-editor</a>
+and <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/storage">storage</a> samples.
 </p>
 
 <h2 id="options">Storage options</h2>
 
 <p>
 Packaged apps use many different mechanisms
 to send and receive data.
 For external data (resources, web pages),
 you need to be aware of the
 <a href="contentSecurityPolicy">Content Security Policy (CSP)</a>.
@@ skipping 31 matching lines @@
 a photo-sharing app can use the Filesystem API
 to read and write any photos that a user selects.
 </p>
 
 <p>
 With Chrome's Sync Filesystem API,
 apps can save and synchronize data
 on a user's Google Drive
 so that the same data can be available across different clients.
 For example, a
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/syncfs-editor">cloud-backed text editor</a>
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/syncfs-editor">cloud-backed text editor</a>
 app can automatically sync new text files to a user's Google Drive account.
 When the user opens the text editor in a new client,
 Google Drive pushes new text files to that instance of the text editor.
 </p>
 
 <p>
 Note: Unlike regular Filesystem API, Chrome's Sync Filesystem API
 currently does <b>NOT</b> support directory operations, except for
 reading directory entries in the root directory.
 An attempt to create a directory in Sync Filesystem will result
@@ skipping 46 matching lines @@
   });
 }
 </pre>
 
 <h3 id="drag">Implementing drag-and-drop</h3>
 
 <p>
 If you need to implement drag-and-drop selection,
 the drag-and-drop file controller
 (<code>dnd.js</code>) in the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/filesystem-access">filesystem-access</a>
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/filesystem-access">filesystem-access</a>
 sample is a good starting point.
 The controller creates a file entry
 from a <code>DataTransferItem</code>
 via drag-and-drop.
 In this example,
 the <code>fileEntry</code> is set
 to the first dropped item.
 </p>
 
 <pre>
 var dnd = new DnDFileController('body', function(data) {
   var fileEntry = data.items[0].webkitGetAsEntry();
   displayPath(fileEntry);
 });
 </pre>
 
 <h3 id="read">Reading a file</h3>
 
 <p>
 The following code opens the file (read-only) and
 reads it as text using a <code>FileReader</code> object.
 If the file doesn't exist, an error is thrown.
 </p>
 
 <pre>
 var chosenFileEntry = null;
 
 chooseFileButton.addEventListener('click', function(e) {
   chrome.fileSystem.chooseEntry({type: 'openFile'}, function(readOnlyEntry) {
- 
+
     readOnlyEntry.file(function(file) {
       var reader = new FileReader();
 
       reader.onerror = errorHandler;
       reader.onloadend = function(e) {
         console.log(e.target.result);
       };
 
       reader.readAsText(file);
     });
@@ skipping 226 matching lines @@
 You can also look at the user's sync backend service storage (in Google Drive).
 Synced files are saved in a hidden Google Drive folder,
 <strong>Chrome Syncable FileSystem</strong>. The folder won't be shown in
 your 'My Drive' list but can be accessed by searching the folder name
 in the search box.  (Note that the remote folder layout is
 <strong>not</strong> guaranteed to remain backwards compatible between
 releases.)
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>