Merge pull request #12841 from ethereum/tutorial-error-fixes

Fix errors in developer tutorials

public/content/developers/tutorials/deploying-your-first-smart-contract/index.md

@@ -70,7 +70,7 @@ Then click on the compile button:
 
 You can choose to select the “Auto compile” option so the contract will always be compiled when you save the content on the text editor.
 
-Then navigate to the deploy and run transactions screen:
+Then navigate to the "deploy and run transactions" screen:
 
 ![The deploy icon in the Remix toolbar](./remix-deploy.png)
 

public/content/developers/tutorials/guide-to-smart-contract-security-tools/index.md

@@ -49,7 +49,7 @@ To effectively test and verify your code, you must identify the areas that need
 
 - [Rapid Risk Assessments](https://infosec.mozilla.org/guidelines/risk/rapid_risk_assessment.html) (our preferred approach when time is short)
 - [Guide to Data-Centric System Threat Modeling](https://csrc.nist.gov/publications/detail/sp/800-154/draft) (aka NIST 800-154)
-- [Shostack thread modeling](https://www.amazon.com/Threat-Modeling-Designing-Adam-Shostack/dp/1118809998)
+- [Shostack threat modeling](https://www.amazon.com/Threat-Modeling-Designing-Adam-Shostack/dp/1118809998)
 - [STRIDE](<https://wikipedia.org/wiki/STRIDE_(security)>) / [DREAD](<https://wikipedia.org/wiki/DREAD_(risk_assessment_model)>)
 - [PASTA](https://wikipedia.org/wiki/Threat_model#P.A.S.T.A.)
 - [Use of Assertions](https://blog.regehr.org/archives/1091)

public/content/developers/tutorials/how-to-use-manticore-to-find-smart-contract-bugs/index.md

@@ -464,7 +464,7 @@ m.transaction(caller=user_account,
 
 #### State constraint {#state-constraint}
 
-Use [state.constrain(constraint)](https://manticore.readthedocs.io/en/latest/states.html?highlight=StateBase#manticore.core.state.StateBase.constrain) to add a constraint to a specific state
+Use [state.constrain(constraint)](https://manticore.readthedocs.io/en/latest/states.html?highlight=StateBase#manticore.core.state.StateBase.constrain) to add a constraint to a specific state.
 It can be used to constrain the state after its exploration to check some property on it.
 
 ### Checking Constraint {#checking-constraint}

public/content/developers/tutorials/nft-minter/index.md

@@ -46,7 +46,7 @@ Cool, now that we understand how making an NFT works, let's clone our starter fi
 
 ## Clone the starter files {#clone-the-starter-files}
 
-First, go to the [nft-minter-tutorial GitHub repository](https://github.com/alchemyplatform/nft-minter-tutorial) to get the starter files for this project. Clone this repository into your local environment.=
+First, go to the [nft-minter-tutorial GitHub repository](https://github.com/alchemyplatform/nft-minter-tutorial) to get the starter files for this project. Clone this repository into your local environment.
 
 When you open this cloned `nft-minter-tutorial` repository, you'll notice that it contains two folders: `minter-starter-files` and `nft-minter`.
 

public/content/developers/tutorials/optimism-std-bridge-annotated-code/index.md

@@ -698,7 +698,7 @@ These two functions are wrappers around `_initiateETHDeposit`, the function that
 ```
 
 The way that cross domain messages work is that the destination contract is called with the message as its calldata.
-Solidity contracts always interpret their calldata is accordance with
+Solidity contracts always interpret their calldata in accordance with
 [the ABI specifications](https://docs.soliditylang.org/en/v0.8.12/abi-spec.html).
 The Solidity function [`abi.encodeWithSelector`](https://docs.soliditylang.org/en/v0.8.12/units-and-global-variables.html#abi-encoding-and-decoding-functions) creates that calldata.
 
@@ -722,7 +722,7 @@ The message here is to call [the `finalizeDeposit` function](https://github.com/
 | \_from    | \_from                         | The address on L1 that sends the ETH                                                                                                         |
 | \_to      | \_to                           | The address on L2 that receives the ETH                                                                                                      |
 | amount    | msg.value                      | Amount of wei sent (which has already been sent to the bridge)                                                                               |
-| \_data    | \_data                         | Additional date to attach to the deposit                                                                                                     |
+| \_data    | \_data                         | Additional data to attach to the deposit                                                                                                     |
 
 ```solidity
         // Send calldata into L2

public/content/developers/tutorials/the-graph-fixing-web3-data-querying/index.md

@@ -242,7 +242,7 @@ export function handleNewBet(event: PlacedBet): void {
 
 ## Using it in the Frontend {#using-it-in-the-frontend}
 
-Using something like Apollo Boost, you can easily integrate The Graph in your React dapp (or Apollo-Vue). Especially when using React hooks and Apollo, fetching data is as simple as writing a single GraphQl query in your component. A typical setup might look like this:
+Using something like Apollo Boost, you can easily integrate The Graph in your React dapp (or Apollo-Vue). Especially when using React hooks and Apollo, fetching data is as simple as writing a single GraphQL query in your component. A typical setup might look like this:
 
 ```javascript
 // See all subgraphs: https://thegraph.com/explorer/