From b24ee047db9e3137f216462a53fb23bb5c8a08cf Mon Sep 17 00:00:00 2001
From: boneyard93501 <4523011+boneyard93501@users.noreply.github.com>
Date: Mon, 4 Jul 2022 14:12:32 -0500
Subject: [PATCH] fix sp

---
 aqua-examples/decentralized-blockchain-gateway/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aqua-examples/decentralized-blockchain-gateway/README.md b/aqua-examples/decentralized-blockchain-gateway/README.md
index 026456b..dc45024 100644
--- a/aqua-examples/decentralized-blockchain-gateway/README.md
+++ b/aqua-examples/decentralized-blockchain-gateway/README.md
@@ -38,7 +38,7 @@ If you are looking for another multi-blockchain API provider, checkout [BEWARELA
 
 Centralized hosted nodes introduce at best a single point of failure and at worst, a nefarious actor creating havoc with your DApp. Hence, a centralized source of truth easily negates the benefits of the decentralized backend. Without giving up all of the convenience and cost savings of hosted blochchain nodes, we can route identical requests to multiple hosted providers and determine, against some subjective metric, the acceptability of the responses. That is, we decentralize hosted provider responses. See Figure 1.
 
-**Figure 1: Stylize Decentralized Blockahinn APIs**
+**Figure 1: Stylize Decentralized Blockchain APIs**
 
 ```mermaid
     sequenceDiagram