chore: fix some typos in comment

chain/standard_cheat_code_contract.go

@@ -491,7 +491,7 @@ func getStandardCheatCodeContract(tracer *cheatCodeTracer) (*CheatCodeContract,
 			}
 			// TODO: Spoof tx.origin
 
-			// Propogate the prank into next call in the same scope.
+			// Propagate the prank into next call in the same scope.
 			if tracer.callDepth > prankData.setAtCallDepth {
 				tracer.PreviousCallFrame().onNextFrameEnterHooks.Push(hookFn)
 			}

docs/src/api/api_overview.md

@@ -22,7 +22,7 @@ A rudimentary description of the objects/providers and their roles are explained
 
 ### Providers
 
-- `ValueGenerator`: This is an object that provides methods to generate values of different kinds for transactions. Examples include the `RandomValueGenerator` and superceding `MutationalValueGenerator`. They are provided a `ValueSet` by their worker, which they may use in generation operations.
+- `ValueGenerator`: This is an object that provides methods to generate values of different kinds for transactions. Examples include the `RandomValueGenerator` and superseding `MutationalValueGenerator`. They are provided a `ValueSet` by their worker, which they may use in generation operations.
 
 - `TestChain`: This is a fake chain that operates on fake block structures created for the purpose of testing. Rather than operating on `types.Transaction` (which requires signing), it operates on `core.Message`s, which are derived from transactions and simply allow you to set the `sender` field. It is responsible for:
 
@@ -133,7 +133,7 @@ The `TestChain` maintains event emitters for the following events under `TestCha
 
 - `PendingBlockCreatedEvent`: This indicates a new block is being created but has not yet been committed to the chain. The block is empty at this point but will likely be populated. It provides a reference to the `Block` and `TestChain`.
 
-- `PendingBlockAddedTxEvent`: This indicates a pending block which has not yet been commited to chain has added a transaction to it, as it is being constructed. It provides a reference to the `Block`, `TestChain`, and index of the transaction in the `Block`.
+- `PendingBlockAddedTxEvent`: This indicates a pending block which has not yet been committed to chain has added a transaction to it, as it is being constructed. It provides a reference to the `Block`, `TestChain`, and index of the transaction in the `Block`.
 
 - `PendingBlockCommittedEvent`: This indicates a pending block was committed to chain as the new head. It provides a reference to the `Block` and `TestChain`.
 

docs/src/testing/writing-tests.md

@@ -121,7 +121,7 @@ contract TestContract {
 }
 ```
 
-`medusa` deploys your contract containing optimization tests and generates a sequence of calls to execute against all publicly accessible methods. After each function call, it calls upon your otpimization tests to identify whether the return value of those tests are greater than the currently stored values.
+`medusa` deploys your contract containing optimization tests and generates a sequence of calls to execute against all publicly accessible methods. After each function call, it calls upon your optimization tests to identify whether the return value of those tests are greater than the currently stored values.
 
 ### Testing in optimization-mode
 

fuzzing/testdata/contracts/cheat_codes/vm/start_prank.sol

@@ -30,7 +30,7 @@ contract TestContract {
         assert(msg.sender == address(1)); // from main entry point
 
         // stopPrank does not act like a stack allowing you to do multiple start/stop pranks
-        // encapsulated within eachother. Although the current call scope still had its
+        // encapsulated within each other. Although the current call scope still had its
         // msg.sender set, a subsequent call should not. Lets test this.
         thisExternal.checkStartPrankInner(originalMsgSender, false);
     }

utils/fs_utils.go

@@ -79,7 +79,7 @@ func CopyFile(sourcePath string, targetPath string) error {
 	return os.Chmod(targetPath, sourceInfo.Mode())
 }
 
-// MoveFile will move a given file from the source path to the target path. Returns an error if one occured.
+// MoveFile will move a given file from the source path to the target path. Returns an error if one occurred.
 func MoveFile(sourcePath string, targetPath string) error {
 	// Obtain file info for the source file
 	sourceInfo, err := os.Stat(sourcePath)