Update the Life of a URL request document to not reference IPCResourceLoaderBridge.

net/docs/life-of-a-url-request.md

Index: net/docs/life-of-a-url-request.md
diff --git a/net/docs/life-of-a-url-request.md b/net/docs/life-of-a-url-request.md
index 69e9e00a810ca5b49d1e64942d6f7e16e154e37c..dc12ae1cd0e8bbbdcc0da230093cf8b20cded9fc 100644
--- a/net/docs/life-of-a-url-request.md
+++ b/net/docs/life-of-a-url-request.md
@@ -103,10 +103,10 @@ work.
 
 Summary:
 
-* ResourceDispatcher creates an IPCResourceLoaderBridge.
-* The IPCResourceLoaderBridge asks ResourceDispatcher to start the request.
-* ResourceDispatcher sends an IPC to the ResourceDispatcherHost in the
-browser process.
+* Network consumers in child processes interact with ResourceDispatcher to
+start/cancel/read/write network requests.
+* ResourceDispatcher acts as a proxy to the browser process (where the
+networking is actually carried out).
 
 Chrome has a single browser process, which handles network requests and tab
 management, among other things, and multiple child processes, which are
@@ -117,12 +117,16 @@ processes are the ones that layout webpages and run HTML.
 Each child process has at most one ResourceDispatcher, which is responsible for
 all URL request-related communication with the browser process. When something
 in another process needs to issue a resource request, it calls into the
-ResourceDispatcher, which returns an IPCResourceLoaderBridge to the caller.
-The caller uses the bridge to start a request. When started, the
+ResourceDispatcher to start either a synchronous or asynchronous request.
+
 ResourceDispatcher assigns the request a per-renderer ID, and then sends the
 ID, along with all information needed to issue the request, to the
 ResourceDispatcherHost in the browser process.
 
+When starting asynchronous requests, callers provide a RequestPeer which acts
+much like a URLRequest::Delegate does in the browser process (receives
+notifications of progress/completion for the network request).
+
 ### ResourceDispatcherHost sets up the request in the browser process
 
 Summary:
@@ -241,11 +245,9 @@ to the URLRequest and on to the ResourceLoader.
 The ResourceLoader passes them through the chain of ResourceHandlers, and then
 they make their way to the AsyncResourceHandler. The AsyncResourceHandler uses
 the renderer process ID ("child ID") to figure out which process the request
-was associated with, and then sends the headers along with the request ID to
-that process's ResourceDispatcher. The ResourceDispatcher uses the ID to
-figure out which IPCResourceLoaderBridge the headers should be sent to, which
-sends them on to whatever created the IPCResourceLoaderBridge in the first
-place.
+originated from, and then sends the headers along with the request ID to
+that process's ResourceDispatcher. The ResourceDispatcher then forwards the
+response to the RequestPeer that was attached to the request.
 
 ### Response body is read