life-of-a-url-request.md typo fix: HttpResponseParser -> HttpStreamParser

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

 # Life of a URLRequest
 
 This document is intended as an overview of the core layers of the network
 stack, their basic responsibilities, how they fit together, and where some of
 the pain points are, without going into too much detail. Though it touches a
 bit on child processes and the content/loader stack, the focus is on net/
 itself.
 
 It's particularly targeted at people new to the Chrome network stack, but
 should also be useful for team members who may be experts at some parts of the
@@ skipping 247 matching lines @@
 * AsyncResourceHandler informs the ResourceDispatcher of each read using
 cross-process IPCs.
 * ResourceDispatcher tells the AsyncResourceHandler when it's done with the
 data with each read, so it knows when parts of the buffer can be reused.
 
 Without waiting to hear back from the ResourceDispatcher, the ResourceLoader
 tells its ResourceHandler chain to allocate memory to receive the response
 body. The AsyncResourceHandler creates a 512KB ring buffer of shared memory,
 and then passes the first 32KB of it to the ResourceLoader for the first read.
 The ResourceLoader then passes a 32KB body read request down through the
-URLRequest all the way down to the HttpResponseParser. Once some data is read,
+URLRequest all the way down to the HttpStreamParser. Once some data is read,
 possibly less than 32KB, the number of bytes read makes its way back to the
 AsyncResourceHandler, which passes the shared memory buffer and the offset and
 amount of data read to the renderer process.
 
 The AsyncResourceHandler relies on ACKs from the renderer to prevent it from
 overwriting data that the renderer has yet to consume. This process repeats
 until the response body is completely read.
 
 ### URLRequest is destroyed
 
@@ skipping 224 matching lines @@
 connection is established, the first usable connection goes to the highest
 priority socket request.
 
 ## Non-HTTP Schemes
 
 The URLRequestJobFactory has a ProtocolHander for each supported scheme.
 Non-HTTP URLRequests have their own ProtocolHandlers. Some are implemented in
 net/, (like FTP, file, and data, though the renderer handles some data URLs
 internally), and others are implemented in content/ or chrome (like blob,
 chrome, and chrome-extension).