fix typos

docs/src/content/hardhat-runner/docs/troubleshooting/verbose-logging.md

@@ -15,7 +15,7 @@ $ npx hardhat test --verbose
   hardhat:core:hre Running task compile:solidity:get-source-names +9ms
   hardhat:core:hre Running task compile:solidity:get-dependency-graph +4ms
   hardhat:core:hre Running task compile:solidity:get-compilation-jobs +10ms
-  hardhat:core:tasks:compile The dependency graph was dividied in '1' connected components +0ms
+  hardhat:core:tasks:compile The dependency graph was divided in '1' connected components +0ms
   hardhat:core:hre Running task compile:solidity:get-compilation-job-for-file +1ms
   hardhat:core:compilation-job File '/tmp/hardhat-project/contracts/Greeter.sol' will be compiled with version '0.7.3' +0ms
   hardhat:core:compilation-job File '/tmp/hardhat-project/node_modules/hardhat/console.sol' added as dependency of '/tmp/hardhat-project/contracts/Greeter.sol' +0ms

docs/src/content/ignition/docs/advanced/execution.md

@@ -34,7 +34,7 @@ The first batch will contain `Future` objects that meet one of these rules:
 
 - It has started executing in a previous run and has neither completed nor failed.
 - It has no dependency.
-- All of its dependencies were successfully executed in a the previous run.
+- All of its dependencies were successfully executed in the previous run.
 
 The successive batches will have `Future` objects whose dependencies are included in the batches preceding it. For example, batch 4 would have `Future` objects whose dependencies were executed in a previous run, or are included in the batches 1, 2 or 3.
 

packages/hardhat-verify/src/internal/solc/bytecode.ts

@@ -51,7 +51,7 @@ export class Bytecode {
     //     compiler seems to add REVERT in all cases, meaning it currently won't happen and this check
     //     will always be correct.
     //   - It is possible, though very unlikely, that this string appears in the bytecode of an EVM
-    //     contract. As a result result, this _isOvm flag should only be used after trying to infer
+    //     contract. As a result, this _isOvm flag should only be used after trying to infer
     //     the solc version
     //   - We need this check because OVM bytecode has no metadata, so when verifying
     //     OVM bytecode the check in `inferSolcVersion` will always return `MISSING_METADATA_VERSION_RANGE`.