Index: chrome/common/extensions/docs/templates/articles/app_codelab6_lifecycle.html |
diff --git a/chrome/common/extensions/docs/templates/articles/app_codelab6_lifecycle.html b/chrome/common/extensions/docs/templates/articles/app_codelab6_lifecycle.html |
index 8e7000be62ec681aee0c26f4e78168919e00eeb1..9b66fd1b8dd2fd6da734f96651348aff773ed658 100644 |
--- a/chrome/common/extensions/docs/templates/articles/app_codelab6_lifecycle.html |
+++ b/chrome/common/extensions/docs/templates/articles/app_codelab6_lifecycle.html |
@@ -61,7 +61,7 @@ only restoring it if the <code>onRestarted</code> event is triggered.</p> |
<p class="note"><b>Note:</b> |
We learned about <code>chrome.storage.sync</code> before, but |
-<a href="storage.html#using-sync">chrome.storage.local</a> |
+<a href="storage#using-sync">chrome.storage.local</a> |
wasn't mentioned until now. |
Both have exactly the same syntax, |
but the semantics of <code>chrome.storage.local</code> is, as the name says, completely local. |
@@ -201,11 +201,11 @@ you can move logic that is shared amoung windows to the event page.</li> |
<h2 id="you_should_also_read">You should also read</h2> |
-<p><a href="app_lifecycle.html">Manage App Lifecycle</a> tutorial</p> |
+<p><a href="app_lifecycle">Manage App Lifecycle</a> tutorial</p> |
<h2 id="what_39_s_next_">What's next?</h2> |
-<p>In <a href="app_codelab7_useridentification.html">6 - Access User's Data</a>, |
+<p>In <a href="app_codelab7_useridentification">6 - Access User's Data</a>, |
you will learn how to identify users and use OAuth2.0 to access Google and other third party services.</p> |
<p class="note"><b>Note:</b> |