From 71608adbbe9af80483d9c37a6632c782f967e388 Mon Sep 17 00:00:00 2001
From: md00ux <54084524+md00ux@users.noreply.github.com>
Date: Mon, 26 Jun 2023 00:12:57 +0300
Subject: [PATCH] Update deploying-aquarius.md

update diagram
---
 infrastructure/deploying-aquarius.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/infrastructure/deploying-aquarius.md b/infrastructure/deploying-aquarius.md
index 8861fdc1..7b1a6829 100644
--- a/infrastructure/deploying-aquarius.md
+++ b/infrastructure/deploying-aquarius.md
@@ -292,7 +292,8 @@ $ curl localhost:9200
 
 Aquarius supports indexing multiple chains using a single instance to serve API requests and one instance for each chain that must be indexed.
 
-<figure><img src="https://user-images.githubusercontent.com/54084524/128821016-f2f2b98d-a62d-469a-9bca-dfd2164df3ae.png" alt=""><figcaption><p>Aquarius</p></figcaption></figure>
+![image](https://github.com/oceanprotocol/docs/assets/54084524/8099e7d7-171d-4d5a-8475-61706c99f4e5)
+
 
 The following deployment templates could be used for guidance. Some parameters are [optional](https://github.com/oceanprotocol/aquarius) and the template could be adjusted based on these considerations. Common cases are the deployments for one/multiple multiple Ethereum networks: