From e48fad9a617dce986c23b7752fe8602a8ed71f98 Mon Sep 17 00:00:00 2001
From: Vika <info@victoriametrics.com>
Date: Tue, 11 Jul 2023 10:00:09 +0000
Subject: [PATCH] update wiki pages

---
 keyConcepts.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/keyConcepts.md b/keyConcepts.md
index f819180..a3670d7 100644
--- a/keyConcepts.md
+++ b/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.