Fix spelling issues (ethereum-optimism#11190)

* add preposition README.md

* add adverb channel_builder.go

* add missing verb README.md

cannon/docs/README.md

@@ -82,7 +82,7 @@ along the branch of the leaf value, starting from the bottom.
 
 To verify the proof, start with the leaf value as `node`, and combine it with respective sibling values:
 `node = keccak256(node ++ sibling)` or `node = keccak256(sibling ++ node)`,
-depending the position of `node` at that level of the tree.
+depending on the position of `node` at that level of the tree.
 
 During the onchain execution, each instruction only executes 1 or 2 memory reads, followed by 0 or 1 writes,
 where the write is over the same memory as was last read.

op-batcher/batcher/channel_builder.go

@@ -254,7 +254,7 @@ func (c *ChannelBuilder) updateSwTimeout(batch *derive.SingularBatch) {
 }
 
 // updateTimeout updates the timeout block to the given block number if it is
-// earlier than the current block timeout, or if it still unset.
+// earlier than the current block timeout, or if it is still unset.
 //
 // If the timeout is updated, the provided reason will be set as the channel
 // full error reason in case the timeout is hit in the future.

op-node/README.md

@@ -52,7 +52,7 @@ an OP Stack based Execution Client that supports the [Ethereum JSON-RPC spec][et
 - L1: use any L1 client, RPC, websocket, or IPC (connection config may differ)
 - L2: use any OP Stack Execution Client like [`op-geth`](https://github.com/ethereum-optimism/op-geth)
 
-Note that websockets or IPC preferred for event notifications to improve sync, http RPC works with adaptive polling.
+Note that websockets or IPC is preferred for event notifications to improve sync, http RPC works with adaptive polling.
 
 ```shell
 ./bin/op-node \