Fixed based on comments

Author: pavangudiwada

docs/configuration/alertmanager-integration/_testing_integration.rst

@@ -19,7 +19,7 @@ Send a dummy alert to AlertManager:
 
         .. image:: /images/robusta-ui-simulate-alert-1.png
            :alt: Choose the cluster
-           :width: 600
+           :width: 900
            :align: center
 
         Then 
@@ -36,6 +36,10 @@ Send a dummy alert to AlertManager:
 
 If everything is setup properly, this alert will reach Robusta. It will show up in the Robusta UI, Slack, and other configured sinks.
 
+.. note::
+
+    It might take a few minutes for the alert to arrive due to AlertManager's `group_wait` and `group_interval` settings. For more details, more info `here <https://prometheus.io/docs/alerting/latest/configuration/#:~:text=How%20long%20to%20wait%20before%20sending%20a%20notification%20about%20new%20alerts%20that%0A%23%20are%20added%20to%20a%20group%20of%20alerts%20for%20which%20an%20initial%20notification%20has%0A%23%20already%20been%20sent>`_.
+
 .. details:: I configured AlertManager, but I'm not receiving alerts?
     :class: warning
 

docs/configuration/alertmanager-integration/victoria-metrics.rst

@@ -13,43 +13,42 @@ Add the following to your Victoria Metrics Alertmanager configuration (e.g., Hel
 .. code-block:: yaml
 
     receivers:
-        - name: 'robusta'
-        webhook_configs:
-            - url: 'http://<ROBUSTA-HELM-RELEASE-NAME>-runner.<NAMESPACE>.svc.cluster.local/api/alerts'
-            send_resolved: true # (3)
+      - name: 'robusta'
+      webhook_configs:
+          - url: 'http://<ROBUSTA-HELM-RELEASE-NAME>-runner.<NAMESPACE>.svc.cluster.local/api/alerts'
+          send_resolved: true # (3)
 
     route: # (1)
-        routes:
-        - receiver: 'robusta'
-            group_by: [ '...' ]
-            group_wait: 1s
-            group_interval: 1s
-            matchers:
-            - severity =~ ".*"
-            repeat_interval: 4h
-            continue: true # (2)
+      routes:
+      - receiver: 'robusta'
+          group_by: [ '...' ]
+          group_wait: 1s
+          group_interval: 1s
+          matchers:
+          - severity =~ ".*"
+          repeat_interval: 4h
+          continue: true # (2)
 
 .. code-annotations::
-    1. Put Robusta's route as the first route, to guarantee it receives alerts. If you can't do so, you must guarantee all previous routes set ``continue: true`` set.
+    1. Put Robusta's route as the first route, to guarantee it receives alerts. If you can't do so, you must guarantee all previous routes has ``continue: true`` set.
     2. Keep sending alerts to receivers defined after Robusta.
     3. Important, so Robusta knows when alerts are resolved.
 
 
 .. include:: ./_testing_integration.rst
 
-Configure Metric Querying
+Configure Metrics Querying
 ====================================
 
 Robusta can query metrics and create silences using Victoria Metrics. If both are in the same Kubernetes cluster, Robusta can auto-detect the Victoria Metrics service. To verify, go to the "Apps" tab in Robusta, select an application, and check for usage graphs.
 
-If auto-detection fails or if Robusta and Victoria Metrics are in different clusters, add the following to ``generated_values.yaml`` and :ref:`update Robusta <Simple Upgrade>`.
+If auto-detection fails you must add the ``prometheus_url`` parameter and :ref:`update Robusta <Simple Upgrade>`.
 
 .. code-block:: yaml
 
     globalConfig: # this line should already exist
         # add the lines below
         alertmanager_url: "http://<VM_ALERT_MANAGER_SERVICE_NAME>.<NAMESPACE>.svc.cluster.local:9093" # Example:"http://vmalertmanager-victoria-metrics-vm.default.svc.cluster.local:9093/"        
-        grafana_url: ""
         prometheus_url: "http://VM_Metrics_SERVICE_NAME.NAMESPACE.svc.cluster.local:8429" # Example:"http://vmsingle-vmks-victoria-metrics-k8s-stack.default.svc.cluster.local:8429"
         # Add any labels that are relevant to the specific cluster (optional)
         # prometheus_additional_labels: