Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/cloudMessagingV2.html
diff --git a/chrome/common/extensions/docs/templates/articles/cloudMessagingV2.html b/chrome/common/extensions/docs/templates/articles/cloudMessagingV2.html
index 65f420df93a81b918100c8574a54baa8b56090d5..f7b52772b4490420f50cce559d1bb7a0bb9ce80b 100644
--- a/chrome/common/extensions/docs/templates/articles/cloudMessagingV2.html
+++ b/chrome/common/extensions/docs/templates/articles/cloudMessagingV2.html
@@ -2,7 +2,7 @@
 <h1 id="gcm">Google Cloud Messaging</h1>
 
 <p>Google Cloud Messaging (GCM) is a service for both Android-powered device and
-Chrome instances to send and receive message data from servers. <a href="gcm.html">GCM Chrome
+Chrome instances to send and receive message data from servers. <a href="gcm">GCM Chrome
 API</a> allows the Chrome apps or extensions to access the GCM
 service for the signed-in Chrome users. The service works even if an app or
 extension isn't currently running. For example, calendar updates could be pushed
@@ -13,8 +13,8 @@ Service</a> and <a href="https://developers.google.com/cloud/terms/">Google Clou
 of Service</a>.</p>
 
 <p>This document describes how to set up and use GCM. For additional information
-see the reference documentation for the <a href="gcm.html">GCM Chrome API</a> and
-the <a href="http://developer.android.com/google/gcm/index.html">GCM Service</a>. To get
+see the reference documentation for the <a href="gcm">GCM Chrome API</a> and
+the <a href="http://developer.android.com/google/gcm/index">GCM Service</a>. To get
 help with GCM or to give us feedback, please see
 <a href="#feedback">Feedback</a>.</p>
 
@@ -121,7 +121,7 @@ Android</strong> toggle to ON.</li>
 
 <p>Please note that the <code>storage</code> permission is also provided here because the
 sample codes below needs to persist some data via the
-<a href="storage.html">chrome.storage</a> API.</p>
+<a href="storage">chrome.storage</a> API.</p>
 
 <h2 id="write_chrome_app_or_extension">Write Chrome App or Extension</h2>
 
@@ -234,7 +234,7 @@ recommended to stay unique across the lifetime of your app or extension, even
 after it restarts. If you use the same message ID, there may be a chance that
 the previous message gets overridden. If an auto-increment counter is used to
 create the message ID, your app or extension should persist the counter value
-via <a href="storage.html">chrome.storage</a> API and restore it when the app
+via <a href="storage">chrome.storage</a> API and restore it when the app
 reloads.</li>
 <li>Destination ID that identifies the server. This is the project number from the
 Google Developers Console plus the suffix "@gcm.googleapis.com".</li>
@@ -337,7 +337,7 @@ provided and multiple messages are queued up in the GCM servers for the same
 user, only the last one with any given collapse key is delivered to your app or
 extension. As a result the <code>message</code> object passed to the $(ref:gcm.onMessage) event
 will contain a <code>collapseKey</code>field. For more details about sending collapsible
-messages, please refer to <a href="http://developer.android.com/google/gcm/adv.html#collapsible">GCM Advance
+messages, please refer to <a href="http://developer.android.com/google/gcm/adv#collapsible">GCM Advance
 Topics</a>.</p>
 
 <h2 id="publish_your_app">Publish your app</h2>