Wording

docs/userguide/tasks.rst

@@ -576,9 +576,10 @@ You can also define :ref:`custom-states`.
 Result Backends
 ---------------
 
-Celery needs to store or send the states somewhere.  There are several
-built-in backends to choose from: SQLAlchemy/Django ORM, Memcached,
-RabbitMQ (amqp), MongoDB, and Redis -- or you can define your own.
+If you want to keep track of tasks or need the return values, then Celery
+must store or send the states somewhere so that they can be retrieved later.
+There are several built-in result backends to choose from: SQLAlchemy/Django ORM,
+Memcached, RabbitMQ (amqp), MongoDB, and Redis -- or you can define your own.
 
 No backend works well for every use case.
 You should read about the strengths and weaknesses of each backend, and choose