document update

Author: giventocode

README.md

@@ -21,9 +21,17 @@ Sources and targets are decoupled, this design enables the composition of variou
 
 *\*   The HTTP/HTTPS source must support HTTP byte ranges and return the file size as a response to a HTTP HEAD request.*
 
+### What's new (0.6.20) ?
+
+- Blob to Block Blobs transfers use the [Put Block from URL API](https://docs.microsoft.com/en-us/rest/api/storageservices/put-block-from-url).
+- Proxy support.
+- Minor fixes and performance improvements.
+- Upgrade to Go 1.11
+
 
 ## Documentation
 
+
 * [Getting Started](http://blobporter.readthedocs.io/en/latest/gettingstarted.html)
 
   * [Linux](http://blobporter.readthedocs.io/en/latest/gettingstarted.html#linux)

docs/examples.rst

@@ -90,8 +90,8 @@ Then you can specify the URI of the source. The source could be a page, block or
 
 .. note::
 
-    BlobPorter will upload the data as it downloads it from the source.
-    The performance of the transfer will be constraint by the bandwidth of the host running BlobPorter. Consider running this type of transfer from a Virtual Machine running in the same Azure region as the target or the source.
+    BlobPorter won't use the bandwidth of the host for this scenario. BlobPorter uses the Put Block From URL API_.
+    .. _API:https://docs.microsoft.com/en-us/rest/api/storageservices/put-block-from-url
 
 Transfer from an HTTP/HTTPS source to Azure Blob Storage
 --------------------------------------------------------