From 70d54027e85645a0e848042f2d49d997f61b30df Mon Sep 17 00:00:00 2001
From: Sam Wilson <57262657+SamWilsn@users.noreply.github.com>
Date: Tue, 24 Sep 2024 17:04:25 -0400
Subject: [PATCH] Update index.md

---
 content/03074/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/03074/index.md b/content/03074/index.md
index cc919e25..8e59635f 100644
--- a/content/03074/index.md
+++ b/content/03074/index.md
@@ -17,7 +17,7 @@ This EIP introduces two EVM instructions `AUTH` and `AUTHCALL`. The first sets a
 
 ## Motivation
 
-Adding more functionality to EOAs has been a long-standing feature request. The requests have spanned from implementing batching capabilities, allowing for gas sponsoring, expirations, scripting, and beyond. These changes often mean increased complexity and rigidity of the protocol. In some cases, it also means increased attack surfaces.
+Adding moreaeue functionality to EOAs has been a long-standing feature request. The requests have spanned from implementing batching capabilities, allowing for gas sponsoring, expirations, scripting, and beyond. These changes often mean increased complexity and rigidity of the protocol. In some cases, it also means increased attack surfaces.
 
 This EIP takes a different approach. Instead of enshrining these capabilities in the protocol as transaction validity requirements, it allows users to *delegate* control of their EOA to a contract. This gives developers a flexible framework for developing novel transaction schemes for EOAs. A motivating use case of this EIP is that it allows any EOA to act like a smart contract wallet *without* deploying a contract.