Fix typos

monitoring/integrations.md

@@ -319,7 +319,7 @@ module.exports = {
 };
 ```
 
-Finally all we need to is modify the deployment script in order to add the verify step and an example transaction:
+Finally all we need to do is modify the deployment script in order to add the verify step and an example transaction:
 
 ```
 const hre = require("hardhat");
@@ -605,7 +605,7 @@ Error: 0x0 Error: INVALID OPCODE, execution stopped
 ...
 ```
 
-![This the the error we get when we don’t proxy our requests through the Tenderly CLI](<../.gitbook/assets/image (45).png>)
+![This the error we get when we don’t proxy our requests through the Tenderly CLI](<../.gitbook/assets/image (45).png>)
 
 ![And this is the human readable stack trace we get when we do proxy our requests thru the Tenderly CLI](<../.gitbook/assets/image (23).png>)
 
@@ -719,7 +719,7 @@ You are also able to import contracts into Remix from your Tenderly project:
 
 ![](<../.gitbook/assets/Screenshot 2021-11-18 at 09.50.58.png>)
 
-You can also add new contracts to your project and see them in Remix at any point. Let's say we want to add this Dai contract into our project in Tenderly. We will copy it's address, go back to the project we want to add it to and go through the flow:
+You can also add new contracts to your project and see them in Remix at any point. Let's say we want to add this Dai contract into our project in Tenderly. We will copy its address, go back to the project we want to add it to and go through the flow:
 
 ![](<../.gitbook/assets/Screenshot 2021-11-18 at 09.52.54.png>)
 

monitoring/smart-contract-verification/verifying-contracts-using-the-tenderly-hardhat-plugin/automatic-contract-verification.md

@@ -10,7 +10,7 @@ tdly.setup({ automaticVerifications: true });
 // tdly.setup();
 ```
 
-The code example below deploys the `Greeter` contract and verifies it in Tenderly. The only step is to wait for the the confirmation of contract's deployment by calling `await greeter.deployed()` , so the plugin gets a chance to verify the contract after it's confirmed.
+The code example below deploys the `Greeter` contract and verifies it in Tenderly. The only step is to wait for the confirmation of contract's deployment by calling `await greeter.deployed()` , so the plugin gets a chance to verify the contract after it's confirmed.
 
 ```tsx
 // File: scripts/greeter/automatic.ts

monitoring/smart-contract-verification/verifying-contracts-using-the-tenderly-hardhat-plugin/manual-contract-verification.md

@@ -197,7 +197,7 @@ The `contracts` property of the configuration is used to specify all the contrac
 
 Here’s a breakdown of the `contracts` property of the advanced verification configuration:
 
-| Paramater                   | Type   | Description                                                                                                                                                                                                                                                                                                    |
+| Parameter                   | Type   | Description                                                                                                                                                                                                                                                                                                    |
 | --------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | contractToVerify            | string | The name of the contract to verify. This can be a short name like `Greeter` or a fully qualified contract name like `contracts/A/Greeter.sol:Greeter`                                                                                                                                                          |
 | sources                     | string | A map of all sources that are needed in order to compile the contract. The key of the map is a source path to the contract.                                                                                                                                                                                    |

monitoring/smart-contract-verification/verifying-contracts-using-the-tenderly-hardhat-plugin/verifying-contracts-on-a-tenderly-fork.md

@@ -180,7 +180,7 @@ The `contracts` property of the configuration is used to specify all the contrac
 
 Here’s a breakdown of the `contracts` property of the advanced verification configuration:
 
-| Paramater            | Type   | Description                                                                                                                                                                                                                                                                                                    |
+| Parameter            | Type   | Description                                                                                                                                                                                                                                                                                                    |
 | -------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | contractName         | string | The name of the contract, as it will appear in the Tenderly dashboard. It doesn’t have to correspond to the actual name of the Smart Contract.                                                                                                                                                                 |
 | source               | string | The source code of your Smart Contract(s).                                                                                                                                                                                                                                                                     |

monitoring/smart-contract-verification/verifying-contracts-using-the-tenderly-hardhat-plugin/verifying-proxy-contracts-on-tenderly.md

@@ -31,7 +31,7 @@ tenderly.setup({ automaticVerifications: false });
 
 Additionally, to get the address where the implementation is deployed, we'll need to use `@openzeppelin/upgrades-core` package.
 
-Verification of the proxy implementation is usually quite straight forward: you'd verify it as you would verify any other contract:
+Verification of the proxy implementation is usually quite straightforward: you'd verify it as you would verify any other contract:
 
 ```ts
 await tenderly.verify({

monitoring/smart-contracts/proxy-contracts.md

@@ -12,7 +12,7 @@ You can import any contract through the standard flow:
 
 ![](<../../.gitbook/assets/Screenshot 2021-10-14 at 16.23.09.png>)
 
-Tenderly will automatically detect a proxy contract and give you the option to add it's latest implementation as well:
+Tenderly will automatically detect a proxy contract and give you the option to add its latest implementation as well:
 
 ![](<../../.gitbook/assets/Screenshot 2021-10-14 at 16.24.23.png>)