docs: use default dynamo queue in KAI-Scheduler example (#4625)

Signed-off-by: Dan Gil <dagil@nvidia.com>

docs/kubernetes/deployment/multinode-deployment.md

@@ -51,7 +51,7 @@ These systems provide enhanced scheduling capabilities including topology-aware
 ##### Prerequisites
 
 - [Grove](https://github.com/NVIDIA/grove/blob/main/docs/installation.md) installed on the cluster
-- (Optional) [KAI-Scheduler](https://github.com/NVIDIA/KAI-Scheduler) installed on the cluster with default queue name `dynamo` created. You can use a different queue name by setting the `nvidia.com/kai-scheduler-queue` annotation on the DGD resource.
+- (Optional) [KAI-Scheduler](https://github.com/NVIDIA/KAI-Scheduler) installed on the cluster with the default queue name `dynamo` created. If no queue annotation is specified on the DGD resource, the operator uses the `dynamo` queue by default. Custom queue names can be specified via the `nvidia.com/kai-scheduler-queue` annotation, but the queue must exist in the cluster before deployment.
 
 KAI-Scheduler is optional but recommended for advanced scheduling capabilities.
 
@@ -94,11 +94,13 @@ kind: DynamoGraphDeployment
 metadata:
   name: my-multinode-deployment
   annotations:
-    nvidia.com/kai-scheduler-queue: "gpu-intensive"  # Optional: defaults to "dynamo"
+    nvidia.com/kai-scheduler-queue: "dynamo"
 spec:
   # ... your deployment spec
 ```
 
+> **Note:** The `nvidia.com/kai-scheduler-queue` annotation defaults to `"dynamo"`. If you specify a custom queue name, ensure the queue exists in your cluster before deploying. You can verify available queues with `kubectl get queues`.
+
 **Force LWS usage:**
 ```yaml
 apiVersion: nvidia.com/v1alpha1