removed references to syncdb

Author: synasius

docs/install.rst

@@ -29,7 +29,6 @@ Sync your database
 
 .. sourcecode:: sh
 
-    $ python manage.py syncdb
     $ python manage.py migrate oauth2_provider
 
 Next step is our :doc:`first tutorial <tutorial/tutorial_01>`.

docs/tutorial/tutorial_01.rst

@@ -8,7 +8,7 @@ You want to make your own :term:`Authorization Server` to issue access tokens to
 Start Your App
 --------------
 During this tutorial you will make an XHR POST from a Heroku deployed app to your localhost instance.
-Since the domain that will originate the request (the app on Heroku) is different than the destination domain (your local instance), 
+Since the domain that will originate the request (the app on Heroku) is different than the destination domain (your local instance),
 you will need to install the `django-cors-headers <https://github.com/ottoyiu/django-cors-headers>`_ app.
 These "cross-domain" requests are by default forbidden by web browsers unless you use `CORS <http://en.wikipedia.org/wiki/Cross-origin_resource_sharing>`_.
 
@@ -60,29 +60,29 @@ Allow CORS requests from all domains (just for the scope of this tutorial):
 
 Include the required hidden input in your login template, `registration/login.html`.
 The ``{{ next }}`` template context variable will be populated with the correct
-redirect value. See the `Django documentation <https://docs.djangoproject.com/en/dev/topics/auth/default/#django.contrib.auth.views.login>`_ 
+redirect value. See the `Django documentation <https://docs.djangoproject.com/en/dev/topics/auth/default/#django.contrib.auth.views.login>`_
 for details on using login templates.
 
 .. code-block:: html
 
     <input type="hidden" name="next" value="{{ next }}" />
 
-As a final step, execute syncdb, start the internal server, and login with your credentials.
+As a final step, execute migrate command, start the internal server, and login with your credentials.
 
 Create an OAuth2 Client Application
 -----------------------------------
-Before your :term:`Application` can use the :term:`Authorization Server` for user login, 
-you must first register the app (also known as the :term:`Client`.) Once registered, your app will be granted access to 
+Before your :term:`Application` can use the :term:`Authorization Server` for user login,
+you must first register the app (also known as the :term:`Client`.) Once registered, your app will be granted access to
 the API, subject to approval by its users.
 
-Let's register your application. 
+Let's register your application.
 
 Point your browser to http://localhost:8000/o/applications/ and add an Application instance.
 `Client id` and `Client Secret` are automatically generated, you have to provide the rest of the informations:
 
  * `User`: the owner of the Application (e.g. a developer, or the currently logged in user.)
 
- * `Redirect uris`: Applications must register at least one redirection endpoint prior to utilizing the 
+ * `Redirect uris`: Applications must register at least one redirection endpoint prior to utilizing the
    authorization endpoint. The :term:`Authorization Server` will deliver the access token to the client only if the client
    specifies one of the verified redirection uris. For this tutorial, paste verbatim the value
    `http://django-oauth-toolkit.herokuapp.com/consumer/exchange/`
@@ -101,16 +101,16 @@ process we'll explain shortly)
 Test Your Authorization Server
 ------------------------------
 Your authorization server is ready and can begin issuing access tokens. To test the process you need an OAuth2
-consumer; if you are familiar enough with OAuth2, you can use curl, requests, or anything that speaks http. For the rest 
-of us, there is a `consumer service <http://django-oauth-toolkit.herokuapp.com/consumer/>`_ deployed on Heroku to test 
+consumer; if you are familiar enough with OAuth2, you can use curl, requests, or anything that speaks http. For the rest
+of us, there is a `consumer service <http://django-oauth-toolkit.herokuapp.com/consumer/>`_ deployed on Heroku to test
 your provider.
 
 Build an Authorization Link for Your Users
 ++++++++++++++++++++++++++++++++++++++++++
 Authorizing an application to access OAuth2 protected data in an :term:`Authorization Code` flow is always initiated
-by the user. Your application can prompt users to click a special link to start the process. Go to the 
+by the user. Your application can prompt users to click a special link to start the process. Go to the
 `Consumer <http://django-oauth-toolkit.herokuapp.com/consumer/>`_ page and complete the form by filling in your
-application's details obtained from the steps in this tutorial. Submit the form, and you'll receive a link your users can 
+application's details obtained from the steps in this tutorial. Submit the form, and you'll receive a link your users can
 use to access the authorization page.
 
 Authorize the Application