From f1ab5ba93f6d55f020ac9bc91dbda5ee57e9838b Mon Sep 17 00:00:00 2001
From: Prathamesh Jayale <85394583+Prathamesh180@users.noreply.github.com>
Date: Sat, 20 May 2023 08:15:53 +0530
Subject: [PATCH] Update 2_crossChainInteroperability.md

Fixed a typo in a word codebases.
---
 src/dapps/2_crossChainInteroperability.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/dapps/2_crossChainInteroperability.md b/src/dapps/2_crossChainInteroperability.md
index 522288b..f5022c3 100644
--- a/src/dapps/2_crossChainInteroperability.md
+++ b/src/dapps/2_crossChainInteroperability.md
@@ -15,7 +15,7 @@ There are some other essential things you should know about bridges before going
 - Bridges are all mutually incompatible with each other. Using multiple bridges just makes 'double wrapped' tokens.
 - If tokens have become double wrapped after traversing multiple bridges or blockchains, there can be a complex unwrapping process to get back to the original token.
 
-This explains how the ecosystem arrived at its current state -- CEXs are a solution to siloed blockchains, DEXs are a simple response to CEXs, and DEXs have created a demand for bridges. Each solution in this timeline is an ad-hoc patch to the previous problem, and the current landscape of fractured liquidity, double wrapped tokens, isolated userbases and wallet incompatibilities is the result.
+This explains how the ecosystem arrived at its current state -- CEXs are a solution to siloed blockchains, DEXs are a simple response to CEXs, and DEXs have created a demand for bridges. Each solution in this timeline is an ad-hoc patch to the previous problem, and the current landscape of fractured liquidity, double wrapped tokens, isolated user bases and wallet incompatibilities is the result.
 
 Adding to this complexity are blockchains moving toward being general-purpose computing platforms. As such, interoperability will require data structures that are more complex than tokens and operations that are more sophisticated than transfers.