From fe0393d38f4908a5fc5da7fc031beb1cd15dfca3 Mon Sep 17 00:00:00 2001
From: Karen Miller <84039272+KMiller-Grafana@users.noreply.github.com>
Date: Wed, 22 Dec 2021 10:30:02 -0800
Subject: [PATCH] Docs: fix callouts for images in the Deployment modes section
 (#4992)

---
 docs/sources/fundamentals/architecture/deployment-modes.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/sources/fundamentals/architecture/deployment-modes.md b/docs/sources/fundamentals/architecture/deployment-modes.md
index 135f38c835..540d2864dd 100644
--- a/docs/sources/fundamentals/architecture/deployment-modes.md
+++ b/docs/sources/fundamentals/architecture/deployment-modes.md
@@ -28,7 +28,7 @@ This is monolithic mode;
 it runs all of Loki’s microservice components inside a single process
 as a single binary or Docker image.
 
-![monolithic mode diagram](monolithic-mode.png)
+![monolithic mode diagram](../monolithic-mode.png)
 
 Monolithic mode is useful for getting started quickly to experiment with Loki,
 as well as for small read/write volumes of up to approximately 100GB per day.
@@ -54,7 +54,7 @@ Loki provides the simple scalable deployment mode.
 This deployment mode can scale to several TBs of logs per day and more.
 Consider the microservices mode approach for very large Loki installations.
 
-![simple scalable deployment mode diagram](simple-scalable.png)
+![simple scalable deployment mode diagram](../simple-scalable.png)
 
 In this mode the component microservices of Loki are bundled into two targets:
 `-target=read` and `-target=write`.
@@ -87,7 +87,7 @@ Each process is invoked specifying its `target`:
 * ruler
 * compactor
 
-![microservices mode diagram](microservices-mode.png)
+![microservices mode diagram](../microservices-mode.png)
 
 Running components as individual microservices allows scaling up
 by increasing the quantity of microservices.