fix: typos

pkg/store/store.go

@@ -13,7 +13,7 @@ import (
 	pb "github.com/rollkit/rollkit/types/pb/rollkit/v1"
 )
 
-// DefaultStore is a default store implmementation.
+// DefaultStore is a default store implementation.
 type DefaultStore struct {
 	db ds.Batching
 }

specs/lazy-adr/adr-007-header-commit-to-shares.md

@@ -7,7 +7,7 @@
 ## Context
 
 1. Only [a single data root must be included in the Celestia block header](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/data_structures.md#header); if more than one data root is included, light nodes will not have any guarantees that the data behind the other data roots is available unless they run a separate sampling process per data root.
-1. [PayForMessaage transactions](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/data_structures.md#signedtransactiondatapayformessage) include a commitment of roots of subtrees of the Celestia data root. This is a requirement for compact proofs that a message was or was not included correctly.
+1. [PayForMessage transactions](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/data_structures.md#signedtransactiondatapayformessage) include a commitment of roots of subtrees of the Celestia data root. This is a requirement for compact proofs that a message was or was not included correctly.
 1. [Over the wire](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/networking.md#wiretxpayformessage), PayForMessage transactions include (potentially) multiple signatures for the same message with different sizes of Celestia block, to allow for [non-interactive message inclusion](https://github.com/celestiaorg/celestia-specs/blob/master/src/rationale/message_block_layout.md#non-interactive-default-rules).
 
 Blocks must follow a similar strategy to the above. Specifically, the data root in block headers [must commit to subtree roots in the Celestia data root](https://github.com/rollkit/rollkit/issues/133), otherwise nodes would not have any guarantees that the data behind the data root in a block header is available.

specs/src/specs/block-manager.md

@@ -106,7 +106,7 @@ Rollkit should support blocks arriving out-of-order on DA, like so:
 #### Termination Condition
 
 If the sequencer double-signs two blocks at the same height, evidence of the fault should be posted to DA. Rollkit full nodes should process the longest valid chain up to the height of the fault evidence, and terminate. See diagram:
-![termination conidition](./termination.png)
+![termination condition](./termination.png)
 
 ### Block Sync Service