Extensions Docs Server: Fix headings with no IDs

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

Index: chrome/common/extensions/docs/templates/articles/npapi.html
diff --git a/chrome/common/extensions/docs/templates/articles/npapi.html b/chrome/common/extensions/docs/templates/articles/npapi.html
index b3408abf2d5327b4cef99040b0658d06a47f0d4a..a47d75e68cab43335520fc78372ca21479a54509 100644
--- a/chrome/common/extensions/docs/templates/articles/npapi.html
+++ b/chrome/common/extensions/docs/templates/articles/npapi.html
@@ -9,7 +9,7 @@ You can bundle an NPAPI plugin with your extension,
 allowing you to call into native binary code from JavaScript.
 </p>
 
-<h2>Warning</h2>
+<h2 id="warning">Warning</h2>
 
 <p align="center"><b>NPAPI is a really big hammer that should only be used when no other approach will work.</b>
 
@@ -18,7 +18,7 @@ allowing you to call into native binary code from JavaScript.
 <p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the
 <a href="https://chrome.google.com/webstore">Chrome Web Store</a>.</p>
 
-<h2>Details</h2>
+<h2 id="details">Details</h2>
 
 <p>
 How to develop an NPAPI plugin is outside the scope of this document.
@@ -94,4 +94,4 @@ Marking your NPAPI plugin "public" increase the attack surface of your
 extension because the plugin is exposed directly to web content, making
 it easier for a malicious web site to manipulate your plugin.  Instead,
 avoid making your NPAPI plugin public whenever possible.
-</p>
+</p>