diff --git a/app/vmalert/README.md b/app/vmalert/README.md
index 3e15ca1225..3db89ac37a 100644
--- a/app/vmalert/README.md
+++ b/app/vmalert/README.md
@@ -68,7 +68,7 @@ Then configure `vmalert` accordingly:
     -external.label=replica=a                # Multiple external labels may be set
 ```
 
-Note there's a separate `remoteRead.url` to allow writing results of
+Note there's a separate `remoteWrite.url` to allow writing results of
 alerting/recording rules into a different storage than the initial data that's
 queried. This allows using `vmalert` to aggregate data from a short-term,
 high-frequency, high-cardinality storage into a long-term storage with
diff --git a/docs/vmalert.md b/docs/vmalert.md
index ebb337ff12..208552a3f5 100644
--- a/docs/vmalert.md
+++ b/docs/vmalert.md
@@ -72,7 +72,7 @@ Then configure `vmalert` accordingly:
     -external.label=replica=a                # Multiple external labels may be set
 ```
 
-Note there's a separate `remoteRead.url` to allow writing results of
+Note there's a separate `remoteWrite.url` to allow writing results of
 alerting/recording rules into a different storage than the initial data that's
 queried. This allows using `vmalert` to aggregate data from a short-term,
 high-frequency, high-cardinality storage into a long-term storage with
@@ -529,7 +529,7 @@ There are following non-required `replay` flags:
   (rules which depend on each other) rules. It is expected, that remote storage will be able to persist
   previously accepted data during the delay, so data will be available for the subsequent queries.
   Keep it equal or bigger than `-remoteWrite.flushInterval`.
-* `replay.disableProgressBar` - whether to disable progress bar which shows progress work.
+* `-replay.disableProgressBar` - whether to disable progress bar which shows progress work.
   Progress bar may generate a lot of log records, which is not formatted as standard VictoriaMetrics logger.
   It could break logs parsing by external system and generate additional load on it.