From 8277b64ec3475176a503e3c52958c68c90837b6d Mon Sep 17 00:00:00 2001
From: Alexander Marshalov <_@marshalov.org>
Date: Tue, 11 Jul 2023 11:59:46 +0200
Subject: [PATCH] follow up for #4612 and #4584 (#4614)

Signed-off-by: Alexander Marshalov <_@marshalov.org>
---
 docs/keyConcepts.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/keyConcepts.md b/docs/keyConcepts.md
index f8191803e..a3670d766 100644
--- a/docs/keyConcepts.md
+++ b/docs/keyConcepts.md
@@ -751,12 +751,12 @@ But this flag avoids non-consistent results due to the fact that only part of th
 
 Here is an illustration of a potential problem when `search.latencyOffset` is set to zero:
 
-<img src="keyConcepts_without_LatencyOffset.png">
+<img src="keyConcepts_without_latencyOffset.png" width="1000">
 
 When this flag is set, the VM will return the last metric value collected before the `search.latencyOffset`
 duration throughout the `search.latencyOffset` duration:
 
-<img src="keyConcepts_with_LatencyOffset.png">
+<img src="keyConcepts_with_latencyOffset.png" width="1000">
 
 It can be overridden on per-query basis via `latency_offset` arg.