minimal on README

docs/advanced_topics.rst

@@ -57,7 +57,7 @@ Depending on the OAuth2 flow in use and the access token policy, users might be
 same authorization multiple times: sometimes this is acceptable or even desiderable but other it isn't.
 To control DOT behaviour you can use `approval_prompt` parameter when hitting the authorization endpoint.
 Possible values are:
- * `force` - users are always prompted for authorization.
+* `force` - users are always prompted for authorization.
 
- * `auto` - users are prompted only the first time, subsequent authorizations for the same application
-   and scopes will be automatically accepted.
+* `auto` - users are prompted only the first time, subsequent authorizations for the same application
+  and scopes will be automatically accepted.

docs/index.rst

@@ -21,8 +21,8 @@ If you need support please send a message to the `Django OAuth Toolkit Google Gr
 Requirements
 ------------
 
-* Python 2.7, 3.3
-* Django 1.4, 1.5, 1.6
+* Python 2.6, 2.7, 3.3, 3.4
+* Django 1.4, 1.5, 1.6, 1.7rc1
 
 Index
 =====

docs/rest-framework/getting_started.rst

@@ -5,7 +5,7 @@ Django OAuth Toolkit provide a support layer for `Django REST Framework <http://
 This tutorial it's based on the Django REST Framework example and shows you how to easily integrate with it.
 
 Step 1: Minimal setup
-----------------------------
+---------------------
 
 Create a virtualenv and install following packages using `pip`...
 
@@ -36,7 +36,7 @@ To do so add the following lines add the end of your `settings.py` module:
     }
 
 Step 2: Create a simple API
---------------------------
+---------------------------
 
 Let's create a simple API for accessing users and groups.
 
@@ -158,7 +158,7 @@ Grab your access_token and start using your new OAuth2 API:
 Step 5: Testing Restricted Access
 ---------------------------------
 
-Let's try to access resources usign a token with a restricted scope adding a `scope` parameter to the token request
+Let's try to access resources using a token with a restricted scope adding a `scope` parameter to the token request
 
 ::