Added devtools.console.* and resource-related calls in inspectedWindow

chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html

Index: chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
diff --git a/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html b/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
index 7ab4addf57074aa79b2c0268cff9d091f9d16ca4..fb1c49c0f8b3ca314ba740fb18451b4ed8b411aa 100644
--- a/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
+++ b/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
@@ -56,6 +56,13 @@ The <code>reload()</code> may be used to reload the inspected page.
 Additionally, a user agent string may be specifcied, which will cause Chrome
 to use the given string in the User-Agent HTTP header while fetching the page
 and its resources, and return it to the scripts running in that page.
+</p><p>
+Use the <code>getResources()</code> call and the <code>onResourceContent</code>
+event to obtain the list of resources (documents, stylesheets, scripts, images
+etc) within the inspected page. The <code>getContent()</code> and <code
+>setContent()</code> methods of the <code>Resource</code> class along with the
+<code>onResourceContentCommitted</code> event may be used to support
+modification of the resource content, e.g. by an external editor.
 </p>
 
 <h2 id="overview-examples">Examples</h2>