Remove .html extension from links

chrome/common/extensions/docs/templates/articles/manifest/storage.html

 <h1>Manifest for storage areas</h1>
 
 <p>
 Unlike the <code>local</code> and <code>sync</code> storage areas, the
 <code>managed</code> storage area requires its structure to be declared as
 <a href="http://tools.ietf.org/html/draft-zyp-json-schema-03">JSON Schema</a>
 and is strictly validated by Chrome. This schema must be stored in a file
 indicated by the <code>"managed_schema"</code> property of the
 <code>"storage"</code> manifest key and declares the enterprise
 policies supported by the {{platform}}.
 </p>
 
 <p>
 Policies are analogous to options but are configured by a system
 administrator instead of the user, allowing the {{platform}} to be
 preconfigured for all users of an organization. See
 <a href="http://www.chromium.org/administrators/">how Chrome handles policies</a>
 for examples from Chrome itself.
 </p>
 
 <p>
 After declaring the policies they can be read from the
-<a href="../storage.html#property-managed">storage.managed</a> API.
+<a href="../storage#property-managed">storage.managed</a> API.
 It's up to the {{platform}} to enforce the policies configured
 by the administrator.
 </p>
 
 <h2 id="manifest">Sample manifest.json</h2>
 
 <p>
 The <code>storage.managed_schema</code> property indicates a file
 within the {{platform}} that contains the policy schema.
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My enterprise {{platform}}",
   "storage": {
     "managed_schema": "schema.json"
   },
   ...
 }
 </pre>
 
 <p>
 Chrome will then load these policies from the underlying operating system
 and from Google Apps for signed-in users. The
-<a href="../storage.html#event-onChanged">storage.onChanged</a>
+<a href="../storage#event-onChanged">storage.onChanged</a>
 event is fired whenever a policy change is detected, including while
 the browser wasn't running if the {{platform}} uses
-<a href="../event_pages.html">event pages</a>.
+<a href="../event_pages">event pages</a>.
 You can verify the policies that Chrome loaded at
 <a href="chrome://policy">chrome://policy</a>.
 </p>
 
 <h2 id="format">Schema format</h2>
 
 <p>
 The JSON Schema format has some additional requirements from Chrome:
 </p>
 
@@ skipping 85 matching lines @@
         "type": "object",
         "properties": {
           "blacklisted": { "type": "boolean" },
           "bypass_proxy": { "type": "boolean" }
         }
       }
     }
   }
 }
 </pre>