Don't reference CELERY_AMQP_TASK_RESULT_EXPIRES in the docs

Replace with the new and not-depreciated CELERY_TASK_RESULT_EXPIRES.

Signed-off-by: Dan McGee <dan@archlinux.org>

docs/configuration.rst

@@ -240,7 +240,7 @@ Example configuration
 .. code-block:: python
 
     CELERY_RESULT_BACKEND = "amqp"
-    CELERY_AMQP_TASK_RESULT_EXPIRES = 18000  # 5 hours.
+    CELERY_TASK_RESULT_EXPIRES = 18000  # 5 hours.
 
 .. _conf-cache-result-backend:
 

docs/getting-started/first-steps-with-celery.rst

@@ -160,7 +160,7 @@ you can configure::
     #: We want the results to expire in 5 minutes, note that this requires
     #: RabbitMQ version 2.1.1 or higher, so please comment out if you have
     #: an earlier version.
-    CELERY_AMQP_TASK_RESULT_EXPIRES = 300
+    CELERY_TASK_RESULT_EXPIRES = 300
 
 To read more about result backends please see :ref:`task-result-backends`.
 

docs/userguide/tasks.rst

@@ -528,7 +528,7 @@ backend:
   control.  If you're running RabbitMQ 2.1.1 or higher you can take advantage
   of the ``x-expires`` argument to queues, which will expire queues after a
   certain time limit after they are unused.  The queue expiry can be set (in
-  seconds) by the :setting:`CELERY_AMQP_TASK_RESULT_EXPIRES` setting (not
+  seconds) by the :setting:`CELERY_TASK_RESULT_EXPIRES` setting (not
   enabled by default).
 
 For a list of options supported by the AMQP result backend, please see