From 1868cde6c1452319eeb25d6ad3c9abaea98ad7c1 Mon Sep 17 00:00:00 2001
From: Lena Hinrichsen <hinrichsen@hab.de>
Date: Fri, 24 Mar 2023 11:34:03 +0100
Subject: [PATCH] fix img src

---
 web_api.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/web_api.md b/web_api.md
index 54ee83a..599c1e1 100644
--- a/web_api.md
+++ b/web_api.md
@@ -90,12 +90,14 @@ There are various ways to build a system which implements this Web API. In this
 architecture, which greatly improves the scalability, flexibility, and reliability of the system compared to
 the [CLI](https://ocr-d.de/en/spec/cli) and the Distributed Processor REST Calls approach.
 
-<figure>
-  <img src="images/web-api-distributed-queue.jpg" alt="Distributed architecture with the Web API"/>
+<p class="figure img" style="max-height: 100%">
+	<a href="/assets/web-api-distributed-queue.jpg" style="max-height: 100%">
+		<img src="/assets/web-api-distributed-queue.jpg" alt="Distributed architecture with the Web API"/>
+	</a>
   <figcaption align="center">
     <b>Fig. 1:</b> OCR-D System Architecture
   </figcaption>
-</figure>
+</p>
 
 In this architecture, all servers are implemented using [FastAPI](https://fastapi.tiangolo.com/). Behind the scene, it
 runs [Uvicorn](https://www.uvicorn.org/), an [ASGI](https://asgi.readthedocs.io/en/latest/) web server implementation