Fixed image call

EnterpriseDB · Jan 14, 2025 · 3be7049 · 3be7049
1 parent 46ed73a
commit 3be7049
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx b/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx
@@ -36,7 +36,7 @@ At the highest level, PGD comprises two main components: Bi-Directional Replicat
 BDR is a Postgres extension that enables a multi-master replication mesh between different BDR-enabled Postgres instances/nodes. 
 [PGD proxy](../routing) sends requests to the write leader—ensuring a lower risk of conflicts between nodes.
 
-![Diagram showing 3 application nodes, 3 proxy instances, and 3 PGD nodes. Traffic is being directed from each of the proxy instances to the write leader node.](/docs/product_docs/docs/pgd/5.6/overview/img/always_on_1x3_updated.png)
+![Diagram showing 3 application nodes, 3 proxy instances, and 3 PGD nodes. Traffic is being directed from each of the proxy instances to the write leader node.](./img/always_on_1x3_updated.png)
 
 Changes are replicated directly, row-by-row between all nodes. 
 [Logical replication](../terminology/#logical-replication) in PGD is asynchronous by default, so only eventual consistency is guaranteed (within seconds usually).