Merge pull request #44 from RichardLitt/feature/edit-data-example

Edited the data example

Author: RichardLitt

examples/data/readme.md

@@ -1,9 +1,9 @@
 ## Dealing With Blocks
-The `ipfs add` command will create a merkle dag out of the data in the files you
-specify, it follows the unixfs data format when doing this. what this means, is
+The `ipfs add` command will create a Merkle DAG out of the data in the files you
+specify. It follows the [unixfs data format](https://github.com/ipfs/go-ipfs/blob/master/unixfs/pb/unixfs.proto) when doing this. This means
 that your files are broken down into blocks, and then arranged in a tree-like
-structure using 'link nodes' to tie them together. a given files 'hash' is
-actually the hash of the root (uppermost) node in the dag. for a given dag, you
+structure using 'link nodes' to tie them together. A given file's 'hash' is
+actually the hash of the root (uppermost) node in the DAG. For a given DAG, you
 can easily view the sub-blocks under it with `ipfs ls`.
 
 For example:
@@ -23,33 +23,33 @@ qmrolalcquyo5vu5v8bvqmgjcpzow16wukq3s3vrll2tdk 7866189
 qmwk51jygpchgwr3srdnmhyerheqd22qw3vvyamb3emhuw 5244129
 ```
 
-What this is showing is all of the immediate sub-blocks of your file, and the
-size of them and their children on disk.
+This shows all of the immediate sub-blocks of your file, as well as the
+size of them and their children on the disk.
 
-### What to do With Blocks?
-If you feel adventurous you can get a lot of different information out of these
-different blocks. you can use the sub-block hashes as input to `ipfs cat` to
+### What to do with Blocks?
+If you feel adventurous, you can get a lot of different information out of these
+different blocks. You can use the sub-block hashes as input to `ipfs cat` to
 see only the data in any given sub-tree (the data of that block and its
-children). to see just the data of a given block and not its children, use
-`ipfs block get`. but be careful, as `ipfs block get` on an intermediate block
-will print out the raw binary data of its dag structure to your screen.
+children). To see just the data of a given block and not its children, use
+`ipfs block get`. But be careful, as `ipfs block get` on an intermediate block
+will print out the raw binary data of its DAG structure to your screen.
 
 `ipfs block stat` will tell you the exact size of a given block (without its
 children), and `ipfs refs` will tell you all the children of that block. 
-similarly, `ipfs ls` or `ipfs object links` will show you all children and
+Similarly, `ipfs ls` or `ipfs object links` will show you all children and
 their sizes. `ipfs refs` is a more suitable command for scripting something
 to run on each child block of a given object.
 
 ### Blocks vs Objects
-In ipfs, a block refers to a single unit of data, identified by its key (hash).
-a block can be any sort of data, and does not necessarily have any sort of 
-format associated with it. an object, on the other hand, refers to a block that
-follows the merkledag protobuf data format. it can be parsed and manipulated
-via the `ipfs object` command. any given hash may represent an object or a block.
+In IPFS, a block refers to a single unit of data, identified by its key (hash).
+A block can be any sort of data, and does not necessarily have any sort of 
+format associated with it. An object, on the other hand, refers to a block that
+follows the Merkle DAG protobuf data format. It can be parsed and manipulated
+via the `ipfs object` command. Any given hash may represent an object or a block.
 
-### Creating a block from scratch
-Creating your own blocks is easy! simply put your data in a file and run
-`ipfs block put <yourfile>` on it, or you can pipe your filedata into 
+### Creating a Block from scratch
+Creating your own blocks is easy! Simply put your data in a file and run
+`ipfs block put <yourfile>` on it. Or, you can pipe your filedata into 
 `ipfs block put`, like so:
 
 ```
@@ -58,8 +58,8 @@ QmfQ5QAjvg4GtA3wg3adpnDJug8ktA1BxurVqBD8rtgVjM
 $ ipfs block get QmfQ5QAjvg4GtA3wg3adpnDJug8ktA1BxurVqBD8rtgVjM
 This is some data
 ```
-Note: When making your own block data, you wont be able to read the data with
-`ipfs cat`, this is because you are inputting raw data without the unixfs data
-format. To read raw blocks use `ipfs block get` as shown in the example.
+Note: When making your own block data, you won't be able to read the data with
+`ipfs cat`. This is because you are inputting raw data without the unixfs data
+format. To read raw blocks, use `ipfs block get` as shown in the example.
 
 By [whyrusleeping](http://github.com/whyrusleeping)