More docs fixes.

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

@@ -255,7 +255,7 @@ since it turns the asynchronous call into a synchronous one::
     4
 
 In case the task raised an exception, :meth:`~@AsyncResult.get` will
-re-raise the exception, but you can override this by specyfing
+re-raise the exception, but you can override this by specifying
 the ``propagate`` argument::
 
     >>> result.get(propagate=True)

docs/userguide/tasks.rst

@@ -540,8 +540,8 @@ Result Backends
 ---------------
 
 Celery needs to store or send the states somewhere.  There are several
-built-in backends to choose from: SQLAlchemy/Django ORM, Memcached, Redis,
-RabbitMQ (amqp), MongoDB, Tokyo Tyrant and Redis -- or you can define your own.
+built-in 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