Merge pull request #7095 from Sabnock01/sabnock/challenger-spec-typo

docs: minor doc fixes

README.md

@@ -57,6 +57,7 @@ Refer to the Directory Structure section below to understand which packages are
 ├── <a href="./op-exporter">op-exporter</a>: Prometheus exporter client
 ├── <a href="./op-heartbeat">op-heartbeat</a>: Heartbeat monitor service
 ├── <a href="./op-node">op-node</a>: rollup consensus-layer client
+├── <a href="./op-preimage">op-preimage</a>: Go bindings for Preimage Oracle
 ├── <a href="./op-program">op-program</a>: Fault proof program
 ├── <a href="./op-proposer">op-proposer</a>: L2-Output Submitter, submits proposals to L1
 ├── <a href="./op-service">op-service</a>: Common codebase utilities

specs/challenger.md

@@ -73,7 +73,7 @@ to each of the different game types. For specification of dispute game types, se
   created by the `DisputeGameFactory` is equal to the output root of their `rollup-node` at the game's `l2BlockNumber`.
   - If it is, the Challenger should sign the [EIP-712 typeHash](./dispute-game.md) of the struct containing the
     `AttestationDisputeGame`'s `rootClaim` and `l2BlockNumber`. The Challenger should then submit the abi-encoded
-    signature to the `AttetationDisputeGame`'s `challenge` function.
+    signature to the `AttestationDisputeGame`'s `challenge` function.
   - If it is not, the Challenger should do nothing in support of this dispute game.
   ![Attestation `DisputeGameCreated` Diagram](./assets/challenger_attestation_dispute_game_created.png)