Improve queue docs (#5154) [ci skip]

Signed-off-by: Paolo Di Tommaso <[email protected]>
Co-authored-by: Ben Sherman <[email protected]>

docs/aws.md

@@ -190,7 +190,7 @@ The `aws` command can be made available by either (1) installing it in the conta
 To configure your pipeline for AWS Batch:
 
 1. Specify the AWS Batch {ref}`executor <awsbatch-executor>`
-2. Specify one or more AWS Batch queues with the {ref}`process-queue` directive
+2. Specify the AWS Batch queue with the {ref}`process-queue` directive
 3. Specify any Batch job container options with the {ref}`process-containerOptions` directive.
 
 An example `nextflow.config` file is shown below:
@@ -212,7 +212,9 @@ aws {
 }
 ```
 
-Different queues bound to the same or different Compute Environments can be configured according to each process' requirements.
+:::{tip}
+Each process can be configured with its own queue by using the {ref}`process-queue` directive in the process definition or via {ref}`config-process-selectors` in your Nextflow configuration.
+:::
 
 ## Container Options
 

docs/process.md

@@ -2370,18 +2370,10 @@ process grid_job {
 }
 ```
 
-Multiple queues can be specified by separating their names with a comma for example:
-
-```groovy
-process grid_job {
-    queue 'short,long,cn-el6'
-    executor 'sge'
-
-    """
-    your task script here
-    """
-}
-```
+:::{tip}
+Grid executors allow specifying multiple queue names separating them with a comma e.g. `queue 'short,long,cn-el6'`.
+However, this does not generally apply to other executors such as AWS Batch, Azure Batch, Google Batch.
+:::
 
 :::{note}
 This directive is only used by certain executors. Refer to the {ref}`executor-page` page to see which executors support this directive.