Fixing path to chrome app samples in documentation

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

 <h1>User Authentication</h1>
 
 <p>
 Web authentication protocols utilize HTTP features,
 but Chrome Apps run inside the app container;
 they don’t load over HTTP and can’t perform redirects or set cookies.
 </p>
 
 <p>
 Use the <a href="identity">Chrome Identity API</a>
 to authenticate users:
 the <code>getAuthToken</code> for users logged into their Google Account and
 the <code>launchWebAuthFlow</code> for users logged into a non-Google account.
 If your app uses its own server to authenticate users, you will need to use the latter.
 </p>
 
 <p class="note">
 <b>API Samples: </b>
 Want to play with the code?
 Check out
 <a href="https://github.com/GoogleChrome/chrome-app-samples#_feature_identity">these samples</a>,
 in particular the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/identity#readme">identity sample</a>.
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/identity#readme">identity sample</a>.
 </p>
 
 <h2 id="how">How it works</h2>
 
 <p>
 Chrome Apps users have a Google account associated with their
 profile. Apps can get OAuth2 tokens for these users using
 the <code>getAuthToken</code> API.
 </p>
 
@@ skipping 91 matching lines @@
 If the app ID here does not match your app ID,
 an error will occur when your app calls <a href="#token">getAuthToken()</a>.
 </p>
 
 <h3 id="update_manifest">Update your manifest with OAuth2 client ID and scopes</h3>
 
 <p>
 You need to update your manifest to include
 the client ID and scopes.
 Here's the sample "oauth2" for the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/gdrive">gdrive sample</a>:
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/gdrive">gdrive sample</a>:
 </p>
 
 <pre data-filename="manifest.json">
 "oauth2": {
     "client_id": "665859454684.apps.googleusercontent.com",
     "scopes": [
       "https://www.googleapis.com/auth/drive"
     ]
   }
 </pre>
@@ skipping 202 matching lines @@
 </p>
 
 <p>
 The best practice we suggest is to use silent mode
 when there is no user gesture involved and use interactive mode
 if there is a user gesture (for example, the user clicked the Sign In button in your app).
 Note that we do not enforce gesture requirement.
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>