Fix outdated documentation on blocking start and handling of synchronous requests

chrome/common/extensions/docs/extensions/webRequest.html

Index: chrome/common/extensions/docs/extensions/webRequest.html
diff --git a/chrome/common/extensions/docs/extensions/webRequest.html b/chrome/common/extensions/docs/extensions/webRequest.html
index d7d31f35e92c3f51b4650bfd2b195902459e78a3..c4976505c8baeaf323618283f2c8c2caee4a7e8c 100644
--- a/chrome/common/extensions/docs/extensions/webRequest.html
+++ b/chrome/common/extensions/docs/extensions/webRequest.html
@@ -302,14 +302,6 @@ For example:</p>
   ]</b>,
   ...
 }</pre>
-<p class="note">
-<b>Node:</b> If you request the "webRequestBlocking" permission, web requests
-are delayed until the background page of your extension has been loaded. This
-allows you to register event listeners before any web requests are processed.
-In order to avoid deadlocks, you must not start synchronous XmlHttpRequests or
-include scripts from the internet via <code>&lt;script src="..."&gt;</code> tags
-in your background page.
-</p>
 <h2 id="life_cycle">Life cycle of requests</h2>
 <p>
 The web request API defines a set of events that follow the life cycle of a web
@@ -411,7 +403,9 @@ are hidden, e.g.,
 <code>other_extension_id</code> is not the ID of the extension to handle
 the request,
 <code>https://www.google.com/chrome</code>,
-and others (this list is not complete).
+and others (this list is not complete). Also synchronous XMLHttpRequests from
+your extension are hidden from blocking event handlers in order to prevent
+deadlocks.
 </p>
 <h2 id="concepts">Concepts</h2>
 <p>As the following sections explain, events in the web request API use request