Merge branch 'main' of https://github.com/zkemail/zk-email-wallet

README.md

@@ -32,10 +32,10 @@ This is first proposed at [ICBC2023](https://speakerdeck.com/sorasuegami/icbc202
 - ✓ Use NFT extension to mint NFTs.
   - `NFT Send 1337 of Punks to [email protected]` (and more)
 
-- ✓ [Advanced] Use custom DKIM Registry for complete control.
+- ✓  Use custom DKIM Registry for complete control.
   - `DKIM registry set to 0x1ababab111...`
 
-- ✓ [Advanced] Exit email wallet to a new owner. New owner (EOA) can control the wallet by executing any calldata on a target contract.
+- ✓ Set email wallet to a new owner. New owner (EOA) can control the wallet by executing any calldata on a target contract.
   - `Exit Email Wallet. Set owner to 0x1ababab111...`
 
 #### Features:
@@ -67,9 +67,9 @@ Here is how a typical interaction with the wallet looks like:
 
 - You send an email to your Relayer's email address with a subject like "Send 1 ETH to [email protected]".
 - The Relayer verifies the DKIM signature and creates a zk proof of email.
-- The ZK circuit also extract the subject, recipient email, timestamp, and other data from the email.
+- The ZK circuit extracts the subject, recipient email, timestamp, and other data from the email.
 - Relayer calls the smart contract with the zk proof and the extracted data.
-- Contract computed the subject from the extracted data and match it with the subject passed by the Relayer.
+- Contract computes the subject from the extracted data and matches it with the subject passed by the Relayer.
 - The ZK proof of email is validated on-chain, which also validates the subject.
 - Private data like the sender email, recipient's email in the subject line, is  not exposed on-chain.
 - The smart contract executes the transaction and sends 1 ETH to recipient's Email Wallet address.