Merge pull request #367 from odsantos/update-en-blob

Update "Blob" article

Author: odsantos

4-binary/03-blob/article.md

@@ -101,7 +101,7 @@ For each URL generated by `URL.createObjectURL` the browser stores a URL -> `Blo
 
 A generated URL (and hence the link with it) is only valid within the current document, while it's open. And it allows to reference the `Blob` in `<img>`, `<a>`, basically any other object that expects a URL.
 
-There's a side-effect though. While there's a mapping for a `Blob`, the `Blob` itself resides in the memory. The browser can't free it.
+There's a side effect though. While there's a mapping for a `Blob`, the `Blob` itself resides in the memory. The browser can't free it.
 
 The mapping is automatically cleared on document unload, so `Blob` objects are freed then. But if an app is long-living, then that doesn't happen soon.
 
@@ -237,16 +237,16 @@ const readableStream = blob.stream();
 const stream = readableStream.getReader();
 
 while (true) {
-  // for each iteration: data is the next blob fragment
-  let { done, data } = await stream.read();
+  // for each iteration: value is the next blob fragment
+  let { done, value } = await stream.read();
   if (done) {
     // no more data in the stream
     console.log('all blob processed.');
     break;
   }
 
    // do something with the data portion we've just read from the blob
-  console.log(data);
+  console.log(value);
 }
 ```