[docs] better links in devtools api docs

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

Index: chrome/common/extensions/docs/templates/articles/devtools.html
diff --git a/chrome/common/extensions/docs/templates/articles/devtools.html b/chrome/common/extensions/docs/templates/articles/devtools.html
index 0db7f589353a796da7f76d3a30d5f5103ee45f91..e6f1243d0b14f089ce71b47d46a2b5c304c34963 100644
--- a/chrome/common/extensions/docs/templates/articles/devtools.html
+++ b/chrome/common/extensions/docs/templates/articles/devtools.html
@@ -4,7 +4,7 @@
 
 <p>A DevTools extension adds functionality to the Chrome DevTools. It can add new
 UI panels and sidebars, interact with the inspected page, get information about
-network requests, and more. DevTools extensions have access to an additional set
+network requests, and more. View <a href="https://developer.chrome.com/devtools/docs/extensions-gallery">featured DevTools extensions</a>. DevTools extensions have access to an additional set
 of DevTools-specific extension APIs:</p>
 
 <ul>
@@ -406,9 +406,12 @@ window.addEventListener('message', function(event) {
 });
 </pre>
 
-Your message will now flow from the injected script, to the content script, to
+<p>Your message will now flow from the injected script, to the content script, to
 the background script, and finally to the DevTools page.

[mkearney1, 2015/02/17 19:08:02]

Small nit - end </p>

 
+<p>You can also consider <a href="https://github.com/GoogleChrome/devtools-docs/issues/143">two alternative message passing techniques here</a>.</p>
+
+
 <h3 id="detecting-open-close">Detecting When DevTools Opens and Closes</h3>
 
 <p>If your extension needs to track whether the DevTools window is open, you can