diff --git a/_includes/example-backends-gdocs.js b/_includes/example-backends-gdocs.js
index 55f6c630..72fa38fd 100644
--- a/_includes/example-backends-gdocs.js
+++ b/_includes/example-backends-gdocs.js
@@ -2,7 +2,8 @@
var dataset = new recline.Model.Dataset({
url: 'https://docs.google.com/spreadsheet/ccc?key=0Aon3JiuouxLUdGZPaUZsMjBxeGhfOWRlWm85MmV0UUE#gid=0'
},
- backend='gdoc'
+ // backend name or instance
+ 'gdocs'
);
// Optional - display the results in a grid
diff --git a/_includes/recline-deps.html b/_includes/recline-deps.html
index a03aa292..ad77703a 100644
--- a/_includes/recline-deps.html
+++ b/_includes/recline-deps.html
@@ -2,6 +2,7 @@
+
@@ -14,7 +15,7 @@
-
+
diff --git a/example-backends.markdown b/example-backends.markdown
index c2cc55ee..c6480089 100644
--- a/example-backends.markdown
+++ b/example-backends.markdown
@@ -56,8 +56,8 @@ How do you know the backend identifier for a given Backend? It's just the name o
* [memory: Memory Backend (local data)](docs/backend/memory.html)
* [elasticsearch: ElasticSearch Backend](docs/backend/elasticsearch.html)
* [dataproxy: DataProxy Backend (CSV and XLS on the Web)](docs/backend/dataproxy.html)
-* [gdoc: Google Docs (Spreadsheet) Backend](docs/backend/gdocs.html)
-* [csv: Local CSV file backend](docs/backend/localcsv.html)
+* [gdocs: Google Docs (Spreadsheet) Backend](docs/backend/gdocs.html)
+* [csv: Local CSV file backend](docs/backend/csv.html)
Backend not on this list that you would like to see? It's very easy to write a new backend -- see below for more details.
diff --git a/example-quickstart.markdown b/example-quickstart.markdown
index 35110e96..497df0a5 100644
--- a/example-quickstart.markdown
+++ b/example-quickstart.markdown
@@ -60,7 +60,7 @@ no reason you cannot have objects as values allowing you to nest data.
We can now create a recline Dataset object (and memory backend) from this raw data:
{% highlight javascript %}
-var dataset = recline.Backend.createDataset(data);
+var dataset = recline.Backend.Memory.createDataset(data);
{% endhighlight %}
Note that behind the scenes Recline will create a Memory backend for this dataset as in Recline every dataset object must have a backend from which it can push and pull data. In the case of in-memory data this is a little artificial since all the data is available locally but this makes more sense for situations where one is connecting to a remote data source (and one which may contain a lot of data).
@@ -85,7 +85,7 @@ And hey presto: