Update README.md

1 files changed, 12 insertions, 9 deletions

diff --git a/README.md b/README.md
index 1508494..f625aac 100644
--- a/README.md
+++ b/README.md
@@ -283,16 +283,8 @@ krr simple --logtostderr -f yaml > result.yaml
 
 <details>
   <summary>Centralized Prometheus (multi-cluster)</summary>
+  <p ><a href="#scanning-with-a-centralized-prometheus">See below on filtering output from a centralized prometheus, so it matches only one cluster</a></p>
 
-If your Prometheus monitors multiple clusters we require the label you defined for your cluster in Prometheus.
-
-For example, if your cluster has the Prometheus label `cluster: "my-cluster-name"`, then run this command:
-
-```sh
-krr.py simple --prometheus-label cluster -l my-cluster-name
-```
-
-You may also need the `-p` flag to explicitly give Prometheus' URL.
 </details>
 
 <details>
@@ -447,6 +439,17 @@ If none of those labels result in finding Prometheus, Victoria Metrics or Thanos
 
 <p align="right">(<a href="#readme-top">back to top</a>)</p>
 
+## Scanning with a Centralized Prometheus
+If your Prometheus monitors multiple clusters we require the label you defined for your cluster in Prometheus.
+
+For example, if your cluster has the Prometheus label `cluster: "my-cluster-name"`, then run this command:
+
+```sh
+krr.py simple --prometheus-label cluster -l my-cluster-name
+```
+
+You may also need the `-p` flag to explicitly give Prometheus' URL.
+
 ## Azure Managed Prometheus
 
 For Azure managed Prometheus you need to generate an access token, which can be done by running the following command: