diff --git a/airflow/config_templates/config.yml b/airflow/config_templates/config.yml
index a7fb39881e511..00aeb23b1dd84 100644
--- a/airflow/config_templates/config.yml
+++ b/airflow/config_templates/config.yml
@@ -1762,8 +1762,10 @@ celery:
     worker_enable_remote_control:
       description: |
         Specify if remote control of the workers is enabled.
-        When using Amazon SQS as the broker, Celery creates lots of ``.*reply-celery-pidbox`` queues. You can
-        prevent this by setting this to false. However, with this disabled Flower won't work.
+        In some cases when the broker does not support remote control, Celery creates lots of
+        ``.*reply-celery-pidbox`` queues. You can prevent this by setting this to false.
+        However, with this disabled Flower won't work.
+        https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/index.html#broker-overview
       version_added: 2.3.0
       type: boolean
       example: ~
diff --git a/airflow/config_templates/default_airflow.cfg b/airflow/config_templates/default_airflow.cfg
index d99075a01035a..471b6c060e6bf 100644
--- a/airflow/config_templates/default_airflow.cfg
+++ b/airflow/config_templates/default_airflow.cfg
@@ -896,8 +896,10 @@ worker_concurrency = 16
 worker_prefetch_multiplier = 1
 
 # Specify if remote control of the workers is enabled.
-# When using Amazon SQS as the broker, Celery creates lots of ``.*reply-celery-pidbox`` queues. You can
-# prevent this by setting this to false. However, with this disabled Flower won't work.
+# In some cases when the broker does not support remote control, Celery creates lots of
+# ``.*reply-celery-pidbox`` queues. You can prevent this by setting this to false.
+# However, with this disabled Flower won't work.
+# https://docs.celeryq.dev/en/stable/getting-started/backends-and-brokers/index.html#broker-overview
 worker_enable_remote_control = true
 
 # The Celery broker URL. Celery supports RabbitMQ, Redis and experimentally