docs: Update rules from the 1.x to 2.x format

Author: sbadia

content/docs/alerting/notification_examples.md

@@ -33,15 +33,18 @@ In this example we again customize the text sent to our Slack receiver accessing
 Alert
 
 ```
-ALERT InstanceDown
-  IF up == 0
-  FOR 5m
-  LABELS { severity = "page" }
-  ANNOTATIONS {
+groups:
+- name: Instances
+  rules:
+  - alert: InstanceDown
+    expr: up == 0
+    for: 5m
+    labels:
+      severity: page
     # Prometheus templates apply here in the annotation and label fields of the alert.
-    summary = "Instance {{ $labels.instance }} down",
-    description = "{{ $labels.instance }} of job {{ $labels.job }} has been down for more than 5 minutes."
-  }
+    annotations:
+      description: '{{ $labels.instance }} of job {{ $labels.job }} has been down for more than 5 minutes.'
+      summary: Instance {{ $labels.instance }} down
 ```
 
 Receiver

content/docs/instrumenting/pushing.md

@@ -82,9 +82,14 @@ Set up an alert to fire if the job has not run recently. Add the following to
 the rules of a Prometheus server that is scraping the Pushgateway:
 
 ```
-ALERT MyBatchJobNotCompleted
-  IF min(time() - my_batch_job_last_success_unixtime{job="my_batch_job"}) > 60 * 60
-  FOR 5m
-  WITH { severity="page" }
-  SUMMARY "MyBatchJob has not completed successfully in over an hour"
+groups:
+- name: MyBatchJob
+  rules:
+  - alert: MyBatchJobNotCompleted
+    expr: min(time() - my_batch_job_last_success_unixtime{job="my_batch_job"}) > 60 * 60
+    for: 5m
+    labels:
+      severity: page
+    annotations:
+      summary: MyBatchJob has not completed successfully in over an hour
 ```