From c7499d40cb86d8ee93c71bf207657b9a935328c8 Mon Sep 17 00:00:00 2001 From: shuoer86 <129674997+shuoer86@users.noreply.github.com> Date: Fri, 10 Nov 2023 22:23:22 +0800 Subject: [PATCH] docs: fix typos --- docs/create-wallets/integrations/privy.md | 2 +- docs/use-wallets/validate-signatures.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/create-wallets/integrations/privy.md b/docs/create-wallets/integrations/privy.md index eb8fa1b..d1cb718 100644 --- a/docs/create-wallets/integrations/privy.md +++ b/docs/create-wallets/integrations/privy.md @@ -30,7 +30,7 @@ Want to see an end-to-end integration of Privy with ZeroDev? Check out [**our ex An [**EOA, or externally-owned account**](https://ethereum.org/en/developers/docs/accounts/), is any Ethereum account that is controlled by a private key. Privy's embedded wallets and most external wallets (MetaMask, Coinbase Wallet, Rainbow Wallet, etc.) are EOAs. -EOAs differ from **contract accounts**, which are instead controlled by smart contract code and do not have their own private key. ZeroDev's smart wallet is a contract account. Contract accounts have [enhanced capabilites, such as gas sponsorship and batched transactions](https://ethereum.org/en/roadmap/account-abstraction/). +EOAs differ from **contract accounts**, which are instead controlled by smart contract code and do not have their own private key. ZeroDev's smart wallet is a contract account. Contract accounts have [enhanced capabilities, such as gas sponsorship and batched transactions](https://ethereum.org/en/roadmap/account-abstraction/). Since they do not have their own private key, contract accounts cannot _directly_ produce signatures and initiate transaction flows. Instead, each contract account is generally "managed" by an EOA, which authorizes actions taken by the contract account via a signature; this EOA is called a **signer**. diff --git a/docs/use-wallets/validate-signatures.md b/docs/use-wallets/validate-signatures.md index c930e4c..5fc5a99 100644 --- a/docs/use-wallets/validate-signatures.md +++ b/docs/use-wallets/validate-signatures.md @@ -83,4 +83,4 @@ run().catch(e => console.error(e)) Since [SIWE doesn't support ERC-6492 yet](https://github.com/spruceid/siwe/pull/153), it will only work if the user's contract account bas been deployed. -Therefore, if you want to validate signatures for even undeployed accounts, you would have to implement your own validation flow as decribed above. \ No newline at end of file +Therefore, if you want to validate signatures for even undeployed accounts, you would have to implement your own validation flow as described above. \ No newline at end of file