complete the Files API segment with a direct example

src/10-ipfs-0-4-0-released/index.md

@@ -95,12 +95,12 @@ you automatically. If you updated manually, and did not run the migration, ipfs
 will fail to run, and print a message saying that there is a mismatch in the repo
 versions.
 
-## The IPFS files API
+## The IPFS **Files API**
 
-In 0.4.0, we've added a new subcommand: `ipfs files`. This subcommand allows us to
-interact with IPFS as if it were a normal mutable filesystem, creating
-directories, reading writing and deleting files, listing out different
-directories, and so on.
+In 0.4.0, we've added a new feature, the Files API, available through the
+subcommand: `ipfs files`. This subcommand allows a program to interact with IPFS
+using familiar filesystem operations, namely: creating directories, reading, writing 
+and deleting files, listing out different directories, and so on.
 
 It is used like so:
 
@@ -115,17 +115,18 @@ $ ipfs files read /cats/foo
 bar
 ```
 
-TODO: Implications and use cases of this
+This feature enables any other application that uses an filesystem like backend for storage, to use IPFS as its storage driver without having change the application logic at all. One great example of this is the [ipfs-blob-store](https://github.com/ipfs/ipfs-blob-store), an IPFS backed storage driver that implements the [blob-store interface](https://github.com/maxogden/abstract-blob-store), so that any app that uses one of the other blob-store storage drivers (S3, indexeddb, levelDB, etc), can now use IPFS with a simple swap. [registry-mirror](https://github.com/diasdavid/registry-mirror) uses this approach to mirror the npm registry onto IPFS.
+
+We are looking forward to see more use cases with this new convinient and powerful API.
 
 ### The public gateway and bootstrappers
 
 We provide two essential public services to the IPFS community: the public
 gateway at https://ipfs.io and the default bootstrap nodes. We're making sure
 that despite the breaking changes, both will continue to work with 0.4.x and
 0.3.x for a while. You can read more about the details of this in an earlier
-blog post: [Migrating ipfs.io from go-ipfs 0.3.x to
-0.4.0](../9-v04x-migration). We expect to keep this grace period open until the
-end of April 2016.
+blog post: [Migrating ipfs.io from go-ipfs 0.3.x to 0.4.0](../9-v04x-migration).
+We expect to keep this grace period open until the end of April 2016.
 
 ## Other improvements and fixes