diff --git a/Dockerfile b/Dockerfile
index aef10e22666cc809da99a01d221ba4c13095fd1e..58088f69ed7ed52575190654da0558977fdf2c2e 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -21,7 +21,7 @@ ENV LD_LIBRARY_PATH "/usr/local/lib"
 # Install DGraph and update dependencies to right versions.
 RUN go get -v github.com/robfig/glock && \
 	go get -v github.com/dgraph-io/dgraph/... && \
-	glock sync github.com/dgraph-io/dgraph && echo "v0.1.1"
+	glock sync github.com/dgraph-io/dgraph && echo "v0.1.2"
 
 # Run some tests, don't build an image if we're failing tests.
 RUN go test github.com/dgraph-io/dgraph/...
diff --git a/README.md b/README.md
index 5cddf18aa75d6082ebc8b1fa5c0b95c7da8f023b..74bc93bdc568a5dd2ed22a6c3e261564eafb15c8 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,7 @@ $ docker run -t -i -v /somedir:/dgraph -v $HOME/go/src/github.com/dgraph-io/benc
 ```
 
 Once into the dgraph container, you can now load your data. Also see [Data Loading](#data-loading) below.
+You can also skip this step, if you just want to play with DGraph. See [Use Freebase Film data](#use-freebase-film-data).
 ```
 $ loader --postings /dgraph/p --rdfgzips /data/rdf-data.gzip --max_ram_mb 3000
 ```
@@ -69,6 +70,11 @@ go test github.com/dgraph-io/dgraph/...
 # Usage
 
 ## Data Loading
+### Use Freebase Film data
+If you just want to play with the system, you can [download this postings directory](https://www.dropbox.com/s/o0lghhd6u7e9eiq/dgraph-p.tar.gz?dl=0),
+unzip/untar it and skip right to [Querying](#querying). This directory contains all the Freebase film data in DGraph posting lists format.
+
+### Bulk Loading
 Let's load up data first. If you have RDF data, you can use that.
 Or, there's [Freebase film rdf data here](https://github.com/dgraph-io/benchmarks).
 
@@ -86,7 +92,7 @@ $ cd $GOPATH/src/github.com/dgraph-io/dgraph/server/loader
 $ go build . && ./loader --rdfgzips=path_of_benchmarks_dir/data/rdf-films.gz,path_of_benchmarks_dir/data/names.gz --postings DIRPATH/p
 ```
 
-### Loading performance
+#### Loading performance
 Loader is memory bound. Every mutation loads a posting list in memory, where mutations
 are applied in layers above posting lists.
 While loader doesn't write to disk every time a mutation happens, it does periodically