From 84122197810f66ca4b35d1e1b0963401f7bbb3de Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@victoriametrics.com>
Date: Wed, 17 Apr 2024 21:12:44 +0200
Subject: [PATCH] docs/vmagent.md: typo fixes after
 dc326f70b4026a802ba0db0c891b856d56b08c0d

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6053
---
 docs/vmagent.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/vmagent.md b/docs/vmagent.md
index 391ece303..03c1a6311 100644
--- a/docs/vmagent.md
+++ b/docs/vmagent.md
@@ -280,9 +280,9 @@ record into TCP address with hostname and TCP port, and then uses the resulting
 
 SRV urls are supported in the following places:
 
-- In `-remoteWrite.url` command-line flags. For example, if `victoria-metrics` [DNS SRV](https://en.wikipedia.org/wiki/SRV_record) record contains
+- In `-remoteWrite.url` command-line flag. For example, if `victoria-metrics` [DNS SRV](https://en.wikipedia.org/wiki/SRV_record) record contains
   `victoria-metrics-host:8428` TCP address, then `-remoteWrite.url=http://srv+victoria-metrics/api/v1/write` is automatically resolved into
-  `-remoteWrite.url=http://victoria-metrics-host:8428/api/v1/write`. If the DNS SRV record is resolved into multiple TCP addresses, then `vmauth`
+  `-remoteWrite.url=http://victoria-metrics-host:8428/api/v1/write`. If the DNS SRV record is resolved into multiple TCP addresses, then `vmagent`
   uses randomly chosen address per each connection it establishes to the remote storage.
 
 - In scrape target addresses aka `__address__` label - see [these docs](https://docs.victoriametrics.com/relabeling/#how-to-modify-scrape-urls-in-targets) for details.