From d5e90fd26409edb0a9ba4f1b55b5f4bc9e00c98c Mon Sep 17 00:00:00 2001
From: Subhojeet Dutta <103040725+Subhojeet28@users.noreply.github.com>
Date: Mon, 12 Jun 2023 16:40:23 +0530
Subject: [PATCH] Update 5_guardianNetwork.md

Changed Upgradeability to Upgradability
---
 src/wormhole/5_guardianNetwork.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/wormhole/5_guardianNetwork.md b/src/wormhole/5_guardianNetwork.md
index 38af065..0127632 100644
--- a/src/wormhole/5_guardianNetwork.md
+++ b/src/wormhole/5_guardianNetwork.md
@@ -8,7 +8,7 @@ To understand not just _how_ the Guardian Network works, but _why_ it works the
 2. **Modularity** - Disparate parts of the ecosystem such as the oracle, relayer, applications, etc, should be kept as separate and modular as possible so they can be designed, modified and upgraded independently.
 3. **Chain Agnosticism** - Wormhole should be able to support not only EVM, but also chains like Solana, Algorand, Cosmos, and even platforms that haven't been created yet. It also should not have any one chain as a single point of failure.
 4. **Scalability** - Wormhole should be able to secure a large amount of value immediately and be able to handle the large transaction volume.
-5. **Upgradeability** - As the decentralized computing ecosystem evolves, Wormhole will need to be able to change the implementation of its existing modules without breaking integrators.
+5. **Upgradability** - As the decentralized computing ecosystem evolves, Wormhole will need to be able to change the implementation of its existing modules without breaking integrators.
 
 Next, let's go into how Wormhole achieves these one at a time.