Fixing path to chrome app samples in documentation

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

 <h1>Connect Apps with Web Intents</h1>
 
 <p class="warning">
 <b>Warning: </b>
 Deprecated in Chrome 24.
 Web intents are no longer supported.
 </p>
 
 <p>
 <a href="http://webintents.org/">Web Intents</a>
 allow your application to quickly communicate
 with other applications on the user's system and inside their browser.
 Your application can register to handle specific user actions
 such as editing images via the <code>manifest.json</code>;
 your application can also invoke actions to be handled by other applications.
 </p>
 
-<p>Chrome Apps use Web Intents as their primary mechanism for inter-app 
+<p>Chrome Apps use Web Intents as their primary mechanism for inter-app
 communication.</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/webintents">webintents</a> sample.
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/webintents">webintents</a> sample.
 </p>
 
 <h2 id="register">Register your app to handle an action</h2>
 
 <p class="warning">
 <b>Warning: </b>
 Deprecated in Chrome 24.
 Web intents are no longer supported.
 </p>
 
 <p>
 You must supply the intent in the manifest:
 </p>
 
 <pre data-filename="manifest.json">
 "intents":{
  "http://webintents.org/edit" : [{
    "title" : "Best Image editing app",
    "type" : ["image/*"]
  }]
 }
 </pre>
 
 <p>
-Unlike extensions and hosted apps, Chrome applications do not 
-need a "href" attribute in the manifest declaration, this is 
-because Chrome Apps have a single entry point for 
-launch - the <code>onLaunched</code> event.  
+Unlike extensions and hosted apps, Chrome applications do not
+need a "href" attribute in the manifest declaration, this is
+because Chrome Apps have a single entry point for
+launch - the <code>onLaunched</code> event.
 </p>
 
 <h2 id="content">Handling content types</h2>
 
 <p class="warning">
 <b>Warning: </b>
 Deprecated in Chrome 24.
 Web intents are no longer supported.
 </p>
 
 <p>
 Your application can be the user's preferred choice for handling a file type.
 For example, your application could handle viewing images or viewing pdfs.
 You must supply the intent in the manifest
 and use the "http://webintents.org/view" action:
 </p>
-<p>To be able declare your application's ability to view RSS and ATOM 
+<p>To be able declare your application's ability to view RSS and ATOM
 feeds, you would add the following to your manifest.
 </p>
 <pre data-filename="manifest.json">
 "intents": {
  "http://webintents.org/view" : [{
    "title" : "RSS Feed Reader",
    "type" : ["application/atom+xml", "application/rss+xml"]
  }]
 }
 </pre>
@@ skipping 23 matching lines @@
 
 <p>
 If your app handles the <code>view</code> intent,
 it is possible to launch it from the command line with a file as a parameter.
 </p>
 <pre>
 chrome.exe --app-id [app_id] [path_to_file]
 </pre>
 <p>
 This will implicity launch your application with an intent payload populated
-with the action set to "http://webintents.org/view", the type set to the 
+with the action set to "http://webintents.org/view", the type set to the
 mime-type of the file and the data as a <code>FileEntry</code> object.
 </p>
 <pre>
 chrome.app.runtime.onLaunched(function(intent) {
   // App Launched
   var data = intent.data;
 });
 </pre>
 
 <h2 id="launching">Manipulating the file</h2>
@@ skipping 147 matching lines @@
   console.log(intent.action);
   console.log(intent.type);
   var data = intent.data;
   // Do something with the data;
 
   intent.postResult(newData);
 });
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>