diff --git a/README.md b/README.md
index 047a4c97f83af7b4054a3680bf988bdb25df54ee..3230567db2f522114fb1f648e481908337c42ff5 100644
--- a/README.md
+++ b/README.md
@@ -203,7 +203,7 @@ local daemonset = k.apps.v1beta2.daemonSet;
 
 ### Customizing Prometheus alerting/recording rules and Grafana dashboards
 
-See [developing alerts and dashboards](developing-alerts-and-dashboards.md) guide.
+See [developing alerts and dashboards](developing-prometheus-rules-and-grafana-dashboards.md) guide.
 
 ## Example
 
diff --git a/docs/monitoring-external-etcd.md b/docs/monitoring-external-etcd.md
index f46f4010f1b3e7903aff982cc7a14f716f79edbd..bfdc58a3cd8b2eac8b2f5ef13faaab7c606d27fb 100644
--- a/docs/monitoring-external-etcd.md
+++ b/docs/monitoring-external-etcd.md
@@ -153,10 +153,10 @@ https://grafana.com/dashboards/3070
 
 ## Save the dashboard in the configmap
 
-As documented here, [Developing Alerts and Dashboards](developing-alerts-and-dashboards.md), the Grafana instances are stateless. The dashboards are automatically re-loaded from the ConfigMap.
+As documented here, [Developing Alerts and Dashboards](developing-prometheus-rules-and-grafana-dashboards.md), the Grafana instances are stateless. The dashboards are automatically re-loaded from the ConfigMap.
 So if you load a dashboard through the Grafana UI, it won't be kept unless saved in ConfigMap
 
-Read [the document](developing-alerts-and-dashboards.md), but in summary:
+Read [the document](developing-prometheus-rules-and-grafana-dashboards.md), but in summary:
 
 ### Copy your dashboard:
 Once you are happy with the dashboard, export it and move it to `prometheus-operator/contrib/kube-prometheus/assets/grafana/` (ending in "-dashboard.json")