Index: chrome/common/extensions/docs/templates/intros/debugger.html |
diff --git a/chrome/common/extensions/docs/templates/intros/debugger.html b/chrome/common/extensions/docs/templates/intros/debugger.html |
index a815425d7dbf3ff947275f81e60bbf7105c4c3e5..a77f9b11c82e1ab4d81efbe41e593cf35cb3e5d1 100644 |
--- a/chrome/common/extensions/docs/templates/intros/debugger.html |
+++ b/chrome/common/extensions/docs/templates/intros/debugger.html |
@@ -1,15 +1,6 @@ |
<h2 id="manifest">Notes</h2> |
<p> |
-Debugger API serves as an alternate transport for Chrome's |
-<a href="http://code.google.com/chrome/devtools/docs/remote-debugging.html"> |
-remote debugging protocol</a>. Use <code>chrome.debugger</code> |
-to attach to one or more tabs to instrument network interaction, debug |
-JavaScript, mutate the DOM and CSS, etc. Use the Debuggee tabId to target tabs |
-with sendCommand and route events by <code>tabId</code> from onEvent callbacks. |
-</p> |
- |
-<p> |
As of today, attaching to the tab by means of the debugger API |
and using embedded Chrome DevTools with that tab are mutually exclusive. |
If user invokes Chrome DevTools while extension is attached to the tab, |
@@ -38,4 +29,4 @@ to use this API. |
<p> |
You can find samples of this API in |
<a href="samples.html#debugger">Samples</a>. |
-</p> |
+</p> |