From 5fa2a387450aad3725ae32c4a2ef0efc74273637 Mon Sep 17 00:00:00 2001
From: Adam Wozniak <29418299+adamewozniak@users.noreply.github.com>
Date: Fri, 22 Mar 2024 14:47:19 -0700
Subject: [PATCH] Update README.md

Co-authored-by: ryanbajollari <54822716+rbajollari@users.noreply.github.com>
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1a4da24..f22bbae 100644
--- a/README.md
+++ b/README.md
@@ -20,7 +20,7 @@ Ojo-evm is a set of contracts which use Axelar's GMP to request data from the Oj
 Ojo-evm is a pull-style oracle which executes DeFi transactions after oracle updates are successful. If they do not succeed or time out, the DeFi transaction will not go through. This design was created to stop tx-spam attacks on EVM, and to minimize the delta between DeFi transactions and oracle updates.
 
 1. User executes a DeFi transaction
-2. The Defi contract requests an Ojo update. During this request, the DeFi contract sends along the parameters and function to call after the oracle update goes through.
+2. The DeFi contract requests an Ojo update. During this request, the DeFi contract sends along the parameters and function to call after the oracle update goes through.
 3. The oracle update goes through Axelar's GMP
 4. Axelar's GMP relays the message over IBC to the Ojo blockchain
 5. The ojo blockchain reaches into the KV store to read the current price data