From 824c00368ce9a5d3665c890352b1c670876ede9f Mon Sep 17 00:00:00 2001
From: Bitcoin Txoko <142011724+bitcointxoko@users.noreply.github.com>
Date: Thu, 2 Nov 2023 10:52:54 +0100
Subject: [PATCH] Update cashu.md

---
 en/cashu.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en/cashu.md b/en/cashu.md
index 1cc4a46..e1e88a2 100644
--- a/en/cashu.md
+++ b/en/cashu.md
@@ -16,7 +16,7 @@ As we can see, Cashu sacrifices trustlessness and decentralisation for privacy.
 
 In contrast, Cashu mints can act as custodians that do not know who their users are, how much funds they have, nor with whom they are transacting. The only data record the mint has is a list of spent secrets that cannot be reused, with no way to associate them with users. 
 
-![https://raw.githubusercontent.com/bitcointxoko/guides/main/images/cashu/onchain-ark-lightning-ecash.jpeg]
+![](https://raw.githubusercontent.com/bitcointxoko/guides/main/images/cashu/onchain-ark-lightning-ecash.jpeg)
 
 Some use cases for Cashu include vouchers which are already centralised and custodial; pay-per-resource usage such as APIs, nostr relays and mixnets; integrated systems replacing the account and balance model; and exchange/mixing services to unlink deposits and withdrawals. 
 ### History