Add anchors to individual content_scripts properties

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

 <h1>Content Scripts</h1>
 
 
 <p>
 Content scripts are JavaScript files that run in the context of web pages.
 By using the standard
 <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document
 Object Model</a> (DOM),
 they can read details of the web pages the browser visits,
 or make changes to them.
@@ skipping 94 matching lines @@
 each of these content scripts can have multiple JavaScript and CSS files.
 Each item in the <code>content_scripts</code> array
 can have the following properties:</p>
 
 <table class="simple">
   <tr>
     <th>Name</th>
     <th>Type</th>
     <th>Description</th>
   </tr>
-  <tr>
+  <tr id="matches">
     <td><code>matches</code></td>
     <td>array of strings</td>
     <td><em>Required.</em>
     Specifies which pages this content script will be injected into.
     See <a href="match_patterns">Match Patterns</a>
     for more details on the syntax of these strings
     and <a href="#match-patterns-globs">Match patterns and globs</a>
     for information on how to exclude URLs.</td>
   </tr>
-  <tr>
+  <tr id="exclude_matches">
     <td><code>exclude_matches</code></td>
     <td>array of strings</td>
     <td><em>Optional.</em>
     Excludes pages that this content script would otherwise be
     injected into.
     See <a href="match_patterns">Match Patterns</a>
     for more details on the syntax of these strings
     and <a href="#match-patterns-globs">Match patterns and globs</a>
     for information on how to exclude URLs.</td>
   </tr>
-  <tr>
+  <tr id="match_about_blank">
     <td><code>match_about_blank<code></td>
     <td>boolean</td>
     <td><em>Optional.</em>
     Whether to insert the content script on <code>about:blank</code> and
     <code>about:srcdoc</code>. Content scripts will only be injected on pages
     when their inherit URL is matched by one of the declared patterns in the
     <code>matches</code> field. The inherit URL is the URL of the document that
     created the frame or window.
     <br>
     Content scripts cannot be inserted in sandboxed frames.
     <br><br>
     Defaults to <code>false</code>.</td>
   </tr>
-  <tr>
+  <tr id="css">
     <td><code>css<code></td>
     <td>array of strings</td>
     <td><em>Optional.</em>
     The list of CSS files to be injected into matching pages. These are injected in the order they appear in this array, before any DOM is constructed or displayed for the page.</td>
   </tr>
-  <tr>
+  <tr id="js">
     <td><code>js<code></td>
     <td><nobr>array of strings</nobr></td>
     <td><em>Optional.</em>
     The list of JavaScript files to be injected into matching pages. These are injected in the order they appear in this array.</td>
   </tr>
   <tr id="run_at">
     <td><code>run_at<code></td>
     <td>string</td>
     <td><em>Optional.</em>
     Controls when the files in <code>js</code> are injected. Can be "document_start", "document_end", or "document_idle". Defaults to "document_idle".
 
     <br><br>
 
     In the case of "document_start", the files are injected after any files from <code>css</code>, but before any other DOM is constructed or any other script is run.
 
     <br><br>
 
     In the case of "document_end", the files are injected immediately after the DOM is complete, but before subresources like images and frames have loaded.
 
     <br><br>
 
     In the case of "document_idle", the browser chooses a time to inject scripts between "document_end" and immediately after the <code><a href="http://www.whatwg.org/specs/web-apps/current-work/#handler-onload">window.onload</a></code> event fires. The exact moment of injection depends on how complex the document is and how long it is taking to load, and is optimized for page load speed.
 
     <br><br>
 
     <b>Note:</b> With "document_idle", content scripts may not necessarily receive the <code>window.onload</code> event, because they may run after it has
     already fired. In most cases, listening for the <code>onload</code> event is unnecessary for content scripts running at "document_idle" because they are guaranteed to run after the DOM is complete. If your script definitely needs to run after <code>window.onload</code>, you can check if <code>onload</code> has already fired by using the <code><a href="http://www.whatwg.org/specs/web-apps/current-work/#dom-document-readystate">document.readyState</a></code> property.</td>
   </tr>
-  <tr>
+  <tr id="all_frames">
     <td><code>all_frames<code></td>
     <td>boolean</td>
     <td><em>Optional.</em>
     Controls whether the content script runs in all frames of the matching page, or only the top frame.
     <br><br>
     Defaults to <code>false</code>, meaning that only the top frame is matched.</td>
   </tr>
-  <tr>
+  <tr id="include_globs">
     <td><code>include_globs</code></td>
     <td>array of string</td>
     <td><em>Optional.</em>
     Applied after <code>matches</code> to include only those URLs that also match this glob. Intended to emulate the <a href="http://wiki.greasespot.net/Metadata_Block#.40include"><code>@include</code></a> Greasemonkey keyword.
     See <a href="#match-patterns-globs">Match patterns and globs</a> below for more details.</td>
   </tr>
-  <tr>
+  <tr id="exclude_globs">
     <td><code>exclude_globs</code></td>
     <td>array of string</td>
     <td><em>Optional.</em>
     Applied after <code>matches</code> to exclude URLs that match this glob.
     Intended to emulate the <a href="http://wiki.greasespot.net/Metadata_Block#.40include"><code>@exclude</code></a> Greasemonkey keyword.
     See <a href="#match-patterns-globs">Match patterns and globs</a> below for more details.</td>
   </tr>
 </table>
 
 <h3 id="match-patterns-globs">Match patterns and globs</h3>
@@ skipping 255 matching lines @@
 
 <p>
 The next video describes message passing,
 featuring an example of a content script
 sending a request to its parent extension.
 </p>
 
 <div class="video-container">
   <iframe title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/B4M_a7xejYI?rel=0" frameborder="0" allowfullscreen></iframe>
 </div>