Merge pull request #11671 from SihanoukSolver29/fix

Documentation Improvements in Ethereum Tutorials

Author: corwintines

src/content/developers/tutorials/how-to-use-echidna-to-test-smart-contracts/index.md

@@ -40,7 +40,7 @@ Echidna is a property-based fuzzer, we described in our previous blogposts ([1](
 
 ### Fuzzing {#fuzzing}
 
-[Fuzzing](https://wikipedia.org/wiki/Fuzzing) is a well-known technique in the security community. It consists to generate more or less randomly inputs to find bugs in the program. Fuzzers for traditional software (such as [AFL](http://lcamtuf.coredump.cx/afl/) or [LibFuzzer](https://llvm.org/docs/LibFuzzer.html)) are known to be efficient tools to find bugs.
+[Fuzzing](https://wikipedia.org/wiki/Fuzzing) is a well-known technique in the security community. It consists of generating inputs that are more or less random to find bugs in the program. Fuzzers for traditional software (such as [AFL](http://lcamtuf.coredump.cx/afl/) or [LibFuzzer](https://llvm.org/docs/LibFuzzer.html)) are known to be efficient tools to find bugs.
 
 Beyond the purely random generation of inputs, there are many techniques and strategies to generate good inputs, including:
 

src/content/developers/tutorials/how-to-view-nft-in-metamask/index.md

@@ -1,6 +1,6 @@
 ---
 title: How to View Your NFT in Your Wallet (Part 3/3 of NFT Tutorial Series)
-description: This tutorial describes how to view an existing an NFT on MetaMask!
+description: This tutorial describes how to view an existing NFT on MetaMask!
 author: "Sumi Mudgil"
 tags: ["ERC-721", "Alchemy", "Solidity"]
 skill: beginner

src/content/developers/tutorials/learn-foundational-ethereum-topics-with-sql/index.md

@@ -10,7 +10,7 @@ source: paulapivat.com
 sourceUrl: https://paulapivat.com/post/query_ethereum/
 ---
 
-Many Ethereum tutorials target developers, but there’s a lack of educational resources for data analyst or for people who wish to see on-chain data without running a client or node.
+Many Ethereum tutorials target developers, but there’s a lack of educational resources for data analysts or for people who wish to see on-chain data without running a client or node.
 
 This tutorial helps readers understand fundamental Ethereum concepts including transactions, blocks and gas by querying on-chain data with structured query language (SQL) through an interface provided by [Dune Analytics](https://dune.xyz/home).
 
@@ -26,7 +26,7 @@ However, a user may wish to query the data directly to reconcile the information
 
 For reference, the smart contract account for the Ethereum Foundation (EF) can be viewed on [Etherscan](https://etherscan.io/address/0xde0b295669a9fd93d5f28d9ec85e40f4cb697bae).
 
-One thing to note is that all accounts, including the EF’s, has a public address that can be used to send and receive transactions.
+One thing to note is that all accounts, including the EF’s, have a public address that can be used to send and receive transactions.
 
 The account balance on Etherscan comprises regular transactions and internal transactions. Internal transactions, despite the name, are not _actual_ transactions that change the state of the chain. They are value transfers initiated by executing a contract ([source](https://ethereum.stackexchange.com/questions/3417/how-to-get-contract-internal-transactions)). Since internal transactions have no signature, they are **not** included on the blockchain and cannot be queried with Dune Analytics.
 

src/content/developers/tutorials/reverse-engineering-a-contract/index.md

@@ -274,7 +274,7 @@ If the call data size is four bytes or more this might be a valid ABI call.
 |     10 | PUSH1 0xe0   | 0xE0 (((First word (256 bits) of the call data))) |
 |     12 | SHR          | (((first 32 bits (4 bytes) of the call data)))    |
 
-Etherscan tells us that `1C` is an unknown opcode, because [it was added after Etherscan wrote this feature](https://eips.ethereum.org/EIPS/eip-145) and they haven't updated it. An [up to data opcode table](https://github.com/wolflo/evm-opcodes) shows us that this is shift right
+Etherscan tells us that `1C` is an unknown opcode, because [it was added after Etherscan wrote this feature](https://eips.ethereum.org/EIPS/eip-145) and they haven't updated it. An [up to date opcode table](https://github.com/wolflo/evm-opcodes) shows us that this is shift right
 
 | Offset | Opcode           | Stack                                                                                                    |
 | -----: | ---------------- | -------------------------------------------------------------------------------------------------------- |