(fleet/prometheus-alerts) reword readme and adjust repeat

Author: csilva-cl

fleet/lib/kube-prometheus-stack/overlays/antu/values.yaml

@@ -192,7 +192,7 @@ alertmanager:
         - site
       group_wait: 30s
       group_interval: 5m
-      repeat_interval: 8760h
+      repeat_interval: 120h
       receiver: blackhole
       routes:
         - receiver: blackhole

fleet/lib/prometheus-alerts/README.md

@@ -13,9 +13,9 @@ file with the `rules.namespace` key.
 
 ## Prometheus rule AURA standards
 
-* `summary` annotation: This annotation MAY contain a templated variable to differentiate between hosts,   pods, clusters, etc. and provides a simple single sentence summary of what the alert is about. For example "Disk space full in acme.lsst.org". When a cluster triggers several alerts, it can be handy to group these alerts into a single notification, this is when the `summary` can be used. It is also useful to set an appropiate title for jira tickets.
-* `discription` annotation: This provides a detailed overview of the alert specifically to this instance of the alert. It MAY contain templated variables to enrich the message.
-* routing label: Rubin uses labels to route alerts. The label is used by alertmanager to decide on the routing of the notification for the alert. By default, all alerts should be routed to Squadcast. The escalation and notification will be handled by Squadcast API.
+* `summary` annotation: This annotation MAY contain a templated variable to differentiate between hosts, pods, clusters, etc. and provides a simple single sentence summary of what the alert is about. For example, "Disk space full in acme.lsst.org". When a cluster triggers several alerts, it can be helpful to group these alerts into a single notification. A distinctive summary, it is also useful as a title for Jira tickets.
+* `description` annotation: This provides a detailed overview of the alert specifically to this instance of the alert. It MAY contain templated variables to enrich the message.
+* routing label: Rubin uses labels to route alerts. The label is used by alertmanager to determine the routing of the notification for the alert. By default, all alerts should be routed to Squadcast. The escalation and notification will be handled by Squadcast API.
 
   Currently (20250616) the following receivers are configured:
 * `gnocpush`: Requires label `gnoc: "true"`