From 263d1a94e1a4240c2eaada850d1117dde95b1881 Mon Sep 17 00:00:00 2001
From: chloefeal <188809157+chloefeal@users.noreply.github.com>
Date: Wed, 25 Dec 2024 21:44:08 +0800
Subject: [PATCH] Update EIP-7819: fix typos

---
 EIPS/eip-7819.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/EIPS/eip-7819.md b/EIPS/eip-7819.md
index 32ed772916cb3f..8238a0a340607a 100644
--- a/EIPS/eip-7819.md
+++ b/EIPS/eip-7819.md
@@ -84,7 +84,7 @@ Reusing EIP-7702 behavior, including clearing the code if the target is 0, resul
 
 ### Delegator chaining
 
-As documented in EIP-7702, designator chains or loops are not resolved. This means that, unlike clones, chaining is an issue. This is however something developpers are used to, as chaining proxy can result in strange behaviors, including infinite delegation loops.
+As documented in EIP-7702, designator chains or loops are not resolved. This means that, unlike clones, chaining is an issue. This is however something developers are used to, as chaining proxy can result in strange behaviors, including infinite delegation loops.
 
 Factories may want to protect against this risk by verifying that the `target` doesn't contain a designator. This can be achieved using a legacy contract helper that has access to `EXTCODEHASH`. It could also be done using other forms of introspection such as an `ACCOUNT_TYPE` instruction.