Wording

docs/getting-started/brokers/sqs.rst

@@ -156,7 +156,7 @@ at this point.
 
 .. warning::
 
-    Do not use the ``amqp`` backend with SQS.
+    Do not use the ``amqp`` result backend with SQS.
 
     It will create one queue for every task, and the queues will
     not be collected.  This could cost you money that would be better

docs/getting-started/next-steps.rst

@@ -47,7 +47,7 @@ you simply import this instance.
 - The ``backend`` argument specifies the result backend to use,
 
     It's used to keep track of task state and results.
-    While results are disabled by default I use the amqp backend here
+    While results are disabled by default I use the amqp result backend here
     because I demonstrate how retrieving results work later, you may want to use
     a different backend for your application. They all have different
     strengths and weaknesses.  If you don't need results it's better

docs/whatsnew-3.1.rst

@@ -536,7 +536,7 @@ the task is always the process to retrieve the result.
 
 It uses Kombu to send and retrieve results, and each client
 uses a unique queue for replies to be sent to.  This avoids
-the significant overhead of the original amqp backend which creates
+the significant overhead of the original amqp result backend which creates
 one queue per task.
 
 By default results sent using this backend will not persist, so they won't