Fix links to issue tracker in extensions docs

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

 <h1>Frequently Asked Questions</h1>
 
 
 <!--  -->
 
 <p>
 If you don't find an answer to your question here,
 try the
-<a href="https://developer.chrome.com/webstore/faq">Chrome Web Store FAQ</a>,
-the {{?is_apps}}
+<a href="https://developer.chrome.com/webstore/faq">Chrome Web Store FAQ</a>, the
+{{?is_apps}}
 <a href="http://stackoverflow.com/questions/tagged/google-chrome-app">[google-chrome-app] tag on Stack Overflow</a>, the
 <a href="http://groups.google.com/a/chromium.org/group/chromium-apps">chromium-apps group</a>, or the
 {{:is_apps}}
 <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension">[google-chrome-extension] tag on Stack Overflow</a>, the
 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions">chromium-extensions group</a>, or the
 {{/is_apps}}
 <a href="https://support.google.com/chrome_webstore/">store help</a>.
 </p>
 
 <div id="faq-TOC">
@@ skipping 376 matching lines @@
     you wish to report.  This extension should have as little code as possible
     to demonstrate the bug&mdash;generally this should be 100 lines of
     code or less.  Many times, developers find that they cannot reproduce their
     issues this way, which is a good indicator that the bug is in their own
     code.
   </li>
   <li>
     Search the issue tracker at
     <a href="http://crbug.com">http://crbug.com</a> to see whether
     someone has reported a similar issue.  Most issues related to
-    extensions are filed under <strong>Cr=Platform-Extensions</strong>, so to
+    extensions are filed under <strong>component=Platform>Extensions</strong>, so to
     look for an extension bug related to the
     chrome.tabs.executeScript function (for example), search for
-    "<code>Cr=Platform-Extensions Type=Bug chrome.tabs.executeScript</code>",
+    "<code>component=Platform>Extensions Type=Bug chrome.tabs.executeScript</code>",
     which will give you
-    <a href="https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DPlatform-Extensions+Type%3DBug+chrome.tabs.executeScript&colspec=ID+Pri+M+Iteration+ReleaseBlock+Cr+Status+Owner+Summary+Modified&x=m&y=releaseblock&cells=tiles">
+    <a href="https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DPlatform>Extensions+Type%3DBug+chrome.tabs.executeScript">
     this list of results</a>.
   </li>
   <li>
     If you find a bug that describes your issue, click the star icon to be
     notified when the bug receives an update.  <em>Do not respond to the
     bug to say "me too" or ask "when will this be fixed?"</em>; such updates
     can cause hundreds of emails to be sent.  Add a comment only if you have
     information (such as a better test case or a suggested fix) that is likely
     to be helpful.
   </li>
@@ skipping 29 matching lines @@
   API) that could be added to improve the extension development experience,
   make sure an appropriate request is filed in the issue tracker.</p>
 
 <p>The steps you should follow to ensure this are:</p>
 
 <ol>
   <li>
     Search the issue tracker at
     <a href="http://crbug.com">http://crbug.com</a> to see whether
     someone has requested a similar feature.  Most requests related to
-    extensions are filed under <strong>Cr=Platform-Extensions</strong>, so to
+    extensions are filed under <strong>component=Platform>Extensions</strong>, so to
     look for an extension feature request related to keyboard shortcuts
     (for example), search
-    for "<code>Cr=Platform-Extensions Type=Feature shortcuts</code>",
+    for "<code>component=Platform>Extensions Type=Feature shortcuts</code>",
     which will give you
-    <a href="https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DPlatform-Extensions+Type%3DFeature+shortcuts&colspec=ID+Pri+M+Iteration+ReleaseBlock+Cr+Status+Owner+Summary+Modified&x=m&y=releaseblock&cells=tiles">
+    <a href="https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3DPlatform>Extensions+Type%3DFeature+shortcuts">
     this list of results</a>.
   </li>
   <li>
     If you find a ticket that matches your request, click the star icon to be
     notified when the bug receives an update.  <em>Do not respond to the
     bug to say "me too" or ask "when will this be implemented?"</em>; such
     updates can cause hundreds of emails to be sent.
   </li>
   <li>
     If you found no appropriate ticket to star, file a new request at
     <a href="http://crbug.com/new">http://crbug.com/new</a>.  Be as detailed
     as possible when filling out this form: choose a descriptive title
     and explain exactly what feature you would like and how you plan to use it.
   </li>
   <li>
     Wait for the ticket to be updated.  Most new requests are triaged within a
     week, although it can sometimes take longer for an update.  <em>Do not reply
     to the ticket to ask when the feature will be added.</em>  If your
     ticket has not been modified after two weeks, please post a message to the
     <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">
     discussion group</a> with a link back to your request.
   </li>
   <li>
     If you originally reported your request on the discussion group and were
     directed to this FAQ entry, reply to your original thread with a link
     to the ticket you starred or opened.  This will make it easier for others
     with the same request to find the correct ticket.
   </li>
 </ol>