diff --git a/docs/operator/monitoring.md b/docs/operator/monitoring.md
index 66f3f9196b..293b34adc3 100644
--- a/docs/operator/monitoring.md
+++ b/docs/operator/monitoring.md
@@ -72,5 +72,5 @@ spec:
 
 See more info about object [VMServiceScrape](./resources/vmservicescrape.md).
 
-You will also need a [vmsingle](https://docs.victoriametrics.com/vmoperatos/resources/vmsingle.html) where the metrics will be collected.
+You will also need a [vmsingle](https://docs.victoriametrics.com/operator/resources/vmsingle.html) where the metrics will be collected.
 
diff --git a/docs/operator/resources/README.md b/docs/operator/resources/README.md
index f388fcbd4b..c84d688e46 100644
--- a/docs/operator/resources/README.md
+++ b/docs/operator/resources/README.md
@@ -198,7 +198,7 @@ It's not efficient to sync its content immediately, and `kubelet` eventually syn
 
 That's why, applications managed by operator don't receive changes immediately. It usually takes 1-2 min, before content will be updated.
 
-It may trigger errors when an application was deleted, but [`VMAgent`](./README.mdvmagent) still tries to scrape it.
+It may trigger errors when an application was deleted, but [`VMAgent`](./vmagent.md) still tries to scrape it.
 
 ### Possible mitigations