diff --git a/DjangoCon-US-2012-Sprints.md b/DjangoCon-US-2012-Sprints.md
index 6e13131..5bf14d6 100644
--- a/DjangoCon-US-2012-Sprints.md
+++ b/DjangoCon-US-2012-Sprints.md
@@ -71,7 +71,7 @@ Resources are view-like classes that implement everything except the actual `.ge
 
 I think the base ModelResource will probably need to be composed of `APIView` Django's `MultipleObjectMixin` *and* `SingleObjectMixin`, plus *all* the REST framework mixins. 
 
-> Maybe instead it can just be derived from `object`, and act as a mixin itself.  Then, the routers would just construct classes that derive from the appropriate mixins as needed. - @mjumbewu
+> Maybe instead it can just be derived from `object`, and act as a mixin itself.  Then, the routers would just construct classes that derive from the appropriate mixins as needed. I'm gonna try that approach out. - @mjumbewu
 
 ### Test out object-level permissions.