Document optional parameters of ...devtools.inspectedWindow.reload()

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 fb1c49c0f8b3ca314ba740fb18451b4ed8b411aa..bc822c7d93ceded0925b31e711cbbd0e0d600aa8 100644
--- a/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
+++ b/chrome/common/extensions/docs/static/experimental.devtools.inspectedWindow.html
@@ -20,12 +20,12 @@ exposed to the Developer Tools extension pages due to security considerations
 — you will need to pass the tab ID to the background page and invoke
 the <code>chrome.tabs.*</code> API functions from there.
 </p></p>
-The <code>eval()</code> provides the ability for extensions to execute
+The <code>eval()</code> method provides the ability for extensions to execute
 JavaScript code in the context of the main frame of the inspected page.
-This function is different from 
+This method is different from 
 <code>chrome.tabs.executeScript()</code> in the following aspects:
 </p><ul>
-<li>The <code>eval()</code> does not
+<li>The <code>eval()</code> method does not
 use an isolated world for the code being evaluated, so the JavaScript state
 of the inspected window is accessible to the code.
 </li><li>
@@ -46,16 +46,16 @@ Tools console API</a> (e.g. <code>inspect()</code>, <code>$0</code> etc).
 </ul>
 <p class="caution">
 <strong>Important:</strong> 
-Due to the security considerations explained above,
+Due to the security considerations explained above, the
 <a href="tabs.html#method-executeScript"><code
->chrome.tabs.executeScript()</code></a> is the preferred way for an extension
-to access DOM data of the inspected page in cases where the access to
+>chrome.tabs.executeScript()</code></a> method is the preferred way for an
+extension to access DOM data of the inspected page in cases where the access to
 JavaScript state of the inspected page is not required.</em>
 </p><p>
-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.
+The <code>reload()</code> method may be used to reload the inspected page.
+Additionally, the caller can specify an override for the user agent string,
+a script that will be injected early upon page load, and an option to force
+reload of cached resources.
 </p><p>
 Use the <code>getResources()</code> call and the <code>onResourceContent</code>
 event to obtain the list of resources (documents, stylesheets, scripts, images