chore: fix typos (#2595)

Fix some typos

Author: bethoffman

docs/adr/adr-014-header-and-data-separation.md

@@ -115,9 +115,9 @@ The `publishBlock` method in `manager.go` now creates the header and data struct
 
 ### Header Producer
 
-Before the separation: Only the entire `Block` struct composed of both header and data was submitted to the DA layer. The `Block` and `SignedHeader` were both gossipped over two separate p2p layers: gossipping `Block` to just full nodes and gossipping the `SignedHeader` to full nodes and future light nodes to join that will only sync headers (and proofs).
+Before the separation: Only the entire `Block` struct composed of both header and data was submitted to the DA layer. The `Block` and `SignedHeader` were both gossipped over two separate p2p layers: gossiping `Block` to just full nodes and gossiping the `SignedHeader` to full nodes and future light nodes to join that will only sync headers (and proofs).
 
-After the separation: The `SignedHeader` and `Data` are submitted separately to the DA layer. Note that the `SignedHeader` has a `Header` that is linked to the `Data` via a `DataCommitment` from the DA layer. `SignedHeader` and `Data` are both gossipped over two separate p2p layers: gossipping `Data` to just full nodes and gossipping the `SignedHeader` to full nodes and future light nodes to join that will only sync headers (and proofs).
+After the separation: The `SignedHeader` and `Data` are submitted separately to the DA layer. Note that the `SignedHeader` has a `Header` that is linked to the `Data` via a `DataCommitment` from the DA layer. `SignedHeader` and `Data` are both gossipped over two separate p2p layers: gossiping `Data` to just full nodes and gossiping the `SignedHeader` to full nodes and future light nodes to join that will only sync headers (and proofs).
 
 In based sequencing mode, the header producer is equivalent to a full node.
 
@@ -161,7 +161,7 @@ flowchart LR
 
 ### Syncing Full Node
 
-Before the separation: Full Nodes get the entire `Block` struct via p2p or the DA layer. They can choose to apply the block as soon as they get it via p2p OR just wait to see it on the DA layer. This depends on whether a full node opts in to the p2p layer or not. Gossipping the `SignedHeader` over p2p is primarily for light nodes to get the header.
+Before the separation: Full Nodes get the entire `Block` struct via p2p or the DA layer. They can choose to apply the block as soon as they get it via p2p OR just wait to see it on the DA layer. This depends on whether a full node opts in to the p2p layer or not. Gossiping the `SignedHeader` over p2p is primarily for light nodes to get the header.
 
 After the separation: Full nodes get the `Data` struct and the `SignedHeader` struct separately over p2p and DA layers. In code, this refers to the `HeaderStore` and the `DataStore` in block manager. A Full node should wait for having both the `Data` struct and the corresponding `SignedHeader` to it before applying the block data to its associated state machine. This is so that the full node can verify that its locally produced header's state commitment after it applies the `Data` associated to a block is consistent with the `Header` inside the `SignedHeader` that is received from the header producer. The `Header` should contain a link to its associated Data via a `DataCommitment` that is a pointer to the location of the `Data` on the DA layer.
 

docs/learn/transaction-flow.md

@@ -3,7 +3,7 @@
 Chain users use a light node to communicate with the chain P2P network for two primary reasons:
 
 - submitting transactions
-- gossipping headers and fraud proofs
+- gossiping headers and fraud proofs
 
 Here's what the typical transaction flow looks like:
 

pkg/p2p/README.md

@@ -177,7 +177,7 @@ This namespace approach ensures that messages only propagate within the intended
 ## Key Functions
 
 - `NewClient`: Creates a new P2P client with the provided configuration
-- `Start`: Establishes P2P connectivity (sets up host, gossipping, DHT, and peer discovery)
+- `Start`: Establishes P2P connectivity (sets up host, gossiping, DHT, and peer discovery)
 - `Close`: Gracefully stops the client
 - `Peers`: Returns a list of connected peers
 - `BroadcastTx`: Broadcasts a transaction to the P2P network