clearly describe `r.raw` in Body Content Workflow

diff --git a/docs/api.rst b/docs/api.rst
index 12ae8a8a5a800c8d9cf3a62903660901abec9dcb..444ce2fccef593ac978da960e381414041c10e86 100644 (file)
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -147,7 +147,7 @@ API Changes
 
 * The parameter for streaming requests was changed from ``prefetch`` to
   ``stream`` and the logic was inverted. In addition, ``stream`` is now
-  required for chunked response reading.
+  required for raw response reading.
 
   ::
 

diff --git a/docs/user/advanced.rst b/docs/user/advanced.rst
index 5a8b9b2864f2e009f7c591621fcc7a5185ab26e0..5ef0ffd309be0ad34021a560c78358f2a569056b 100644 (file)
--- a/docs/user/advanced.rst
+++ b/docs/user/advanced.rst
@@ -161,7 +161,7 @@ At this point only the response headers have been downloaded and the connection
       content = r.content
       ...
 
-You can further control the workflow by use of the :class:`Response.iter_content` and :class:`Response.iter_lines` methods.
+You can further control the workflow by use of the :class:`Response.iter_content` and :class:`Response.iter_lines` methods. Also you can read undecoded body from the underlying urllib3 :class:`urllib3.HTTPResponse` at :class:`Response.raw`.
 
 
 Keep-Alive