Added doc for cleartokens command

Author: outsbart

docs/index.rst

@@ -38,6 +38,7 @@ Index
    models
    advanced_topics
    settings
+   management_commands
    glossary
 
 .. toctree::

docs/management_commands.rst

@@ -0,0 +1,20 @@
+Management commands
+===================
+
+Django OAuth Toolkit exposes some useful management commands that can be run via shell or by other means (eg: cron)
+
+.. _cleartokens:
+
+cleartokens
+~~~~~~~~~~~
+
+The ``cleartokens`` management command allows the user to remove those refresh tokens whose lifetime is greater than the
+amount specified by ``REFRESH_TOKEN_EXPIRE_SECONDS`` settings. It is important that this command is run regularly
+(eg: via cron) to avoid cluttering the database with expired refresh tokens.
+
+If ``cleartokens`` runs daily the maximum delay before a refresh token is
+removed is ``REFRESH_TOKEN_EXPIRE_SECONDS`` + 1 day. This is normally not a
+problem since refresh tokens are long lived.
+
+Note: Refresh tokens need to expire before AccessTokens can be removed from the
+database. Using ``cleartokens`` without ``REFRESH_TOKEN_EXPIRE_SECONDS`` has limited effect.

docs/settings.rst

@@ -98,15 +98,7 @@ The name of the *write* scope.
 REFRESH_TOKEN_EXPIRE_SECONDS
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 The number of seconds before a refresh token gets removed from the database by
-the ``cleartokens``` management command. It's important that ``cleartokens``
-runs regularly (eg: via cron) in order for this setting to work.
-
-If ``cleartokens`` runs daily the maximum delay before a refresh token is
-removed is ``REFRESH_TOKEN_EXPIRE_SECONDS`` + 1 day. This is normally not a
-problem since refresh tokens are long lived.
-
-Note: Refresh tokens need to expire before AccessTokens can be removed from the
-database. Using ``cleartokens`` without ``REFRESH_TOKEN_EXPIRE_SECONDS`` has limited effect.
+the ``cleartokens`` management command. Check :ref:`cleartokens` management command for further info.
 
 REQUEST_APPROVAL_PROMPT
 ~~~~~~~~~~~~~~~~~~~~~~~