diff --git a/Getting-to-1.0.md b/Getting-to-1.0.md
index f4c0ee3..bd479f3 100644
--- a/Getting-to-1.0.md
+++ b/Getting-to-1.0.md
@@ -9,7 +9,7 @@ a lot of the hard work has been done, but there's still a little way to go befor
Stuff that needs to change
==========================
-1. Drop short status codes. [#126](https://github.com/tomchristie/django-rest-framework/issues/126) **DONE**
+1. Drop short status codes. [#126](https://github.com/tomchristie/django-rest-framework/issues/126) **DONE**
2. Response to inherit from `HttpResponse`. [#127](https://github.com/tomchristie/django-rest-framework/issues/127)
+ Becomes a type of standard Django Template Response, with `.render()` method.
+ `add_header()` dropped from `View` - set headers on the response as with standard Django.
@@ -26,11 +26,11 @@ Stuff that needs to change
+ Resources never deal with anything at HTTP level.
+ Views no longer have optional `model`, `form` properties that automagically create resources,
if they use a resource, it must be provided using `.resource`
-6. Drop `set_script_prefix` munging. [#167](https://github.com/tomchristie/django-rest-framework/issues/167)
- + Provide a `reverse` call that extends the standard `reverse`,
- but can take the current request as an argument if an absolute URL is required.
+6. Drop `set_script_prefix` munging. [#167](https://github.com/tomchristie/django-rest-framework/issues/167) **DONE**
+ + Provide a `reverse` call that extends the standard `reverse`,
+ but can take the current request as an argument if an absolute URL is required.
7. Hooks throughout for creating `.resource`, `.serializer`, `.renderer` etc... instances inside the View, given the classes.
-8. Drop support for unnamed args in URLs filtering as pk. Better to always be explicit in the urlconf. **DONE**
+8. Drop support for unnamed args in URLs filtering as pk. Better to always be explicit in the urlconf. **DONE**
9. `InstanceMixin` needs to disappear.
10. `.CONTENT` probably needs to disappear. To confusing to have that as well as `.DATA` and `.FILES`.
11. Explorable JSON: The default JSON output could have a section for placing meta information either by default or by swapping in a new serializer. This is common in REST API's as a place to give clients things such as type information, pagination links, etc... Two approaches seem to make sense: a Tastypie compatible approach ( with a meta dict and objects list) or something like the well-regarded foursquare API (with meta, and response dicts) (@poswald)