Docs: fix spelling issues (#242)

README.md

@@ -139,7 +139,7 @@ npx hardhat hhgas:merge "gasReporterOutput-*.json"
 
 ## Supported Networks
 
-API keys for the networks this plugin auto-configures via the `L1` and `L2` options are available from the links below. In many cases these aren't equired - you'll only need to set them if you start seeing rate-limit warnings.
+API keys for the networks this plugin auto-configures via the `L1` and `L2` options are available from the links below. In many cases these aren't required - you'll only need to set them if you start seeing rate-limit warnings.
 
 :warning:   **UPDATE:** Etherscan now requires api keys to fetch both L1 (Ethereum Mainnet) **and** L2 gas price data. (An example config [can be found here][2])
 

docs/advanced.md

@@ -162,7 +162,7 @@ const config: HardhatUserConfig = {
 
 ## Proxy Resolvers
 
-Some contract systems route calls through proxies (for upgradeability or other reasons) which means the reporter can't know which contract is the target of a transaction without additional help. The `proxyResolver` option lets you define a custom class to help resolve these unindentified method calls.
+Some contract systems route calls through proxies (for upgradeability or other reasons) which means the reporter can't know which contract is the target of a transaction without additional help. The `proxyResolver` option lets you define a custom class to help resolve these unidentified method calls.
 
 There are two examples in the code base here to use as templates if you're writing your own:
 

src/lib/render/json.ts

@@ -3,7 +3,7 @@ import { GasData } from "../gasData";
 import { GasReporterOptions, GasReporterOutput } from "../../types";
 
 /**
- * Writes acccumulated data and the current options to gasReporterOutput.json so it
+ * Writes accumulated data and the current options to gasReporterOutput.json so it
  * can be consumed by other tools (CI etc...)
  * @param {GasData}               data
  * @param {GasReporterOptions}    options