From a91a2b97ed0b2f70f654d18838bb413cb9ab62fc Mon Sep 17 00:00:00 2001
From: Zakhar Bessarab <z.bessarab@victoriametrics.com>
Date: Fri, 14 Jun 2024 16:01:44 +0400
Subject: [PATCH] docs/guides/otel-guide: update sentence to make it less
 obscure (#6483)

### Describe Your Changes

Please provide a brief description of the changes you made. Be as
specific as possible to help others understand the purpose and impact of
your modifications.

### Checklist

The following checks are **mandatory**:

- [x] My change adheres [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/contributing/).

Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com>
(cherry picked from commit f11261dc444e5bf3c8c94d271a19748d351da9ee)
---
 docs/guides/getting-started-with-opentelemetry.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/guides/getting-started-with-opentelemetry.md b/docs/guides/getting-started-with-opentelemetry.md
index 268afee999..e8f444516e 100644
--- a/docs/guides/getting-started-with-opentelemetry.md
+++ b/docs/guides/getting-started-with-opentelemetry.md
@@ -248,7 +248,8 @@ See the full source code of the example [here](/guides/getting-started-with-open
 
 ### Test metrics ingestion
 
-For metrics from our WEB server to be shipped to VictoriaMetrics we need make it available for ingestion.
+In order to push metrics of our WEB server to VictoriaMetrics it is necessary to ensure that VictoriaMetrics ingestion
+endpoint is available locally.
 In previous steps we already deployed a single-server VictoriaMetrics, so let's make it available locally:
 ```sh
 # port-forward victoriametrics to ingest metrics