docs: clarifications

Co-authored-by: Sanaz Taheri <[email protected]> Co-authored-by: Rootul P <[email protected]>
celestiaorg · Jun 29, 2023 · 89c03ac · 89c03ac
1 parent b36dcc4
commit 89c03ac
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/specs/src/specs/block_validity_rules.md b/specs/src/specs/block_validity_rules.md
@@ -4,7 +4,7 @@ Unlike most blockchains, Celestia derives most of its functionality from
 stateless commitments to data rather than stateful transitions. This means that
 the protocol relies heavily on block validity rules. Notably, resource
 constrained light clients must be able to detect when these validity rules have
-not been followed in order to avoid making an honest majority assumption. This
+not been followed in order to avoid making an honest majority assumption on the consensus network. This
 has a significant impact on thier design. More information on how light clients verify
 block validity rules can be foud in the [Fraud Proofs](./fraud_proofs.md) spec.
 

diff --git a/specs/src/specs/fraud_proofs.md b/specs/src/specs/fraud_proofs.md
@@ -18,7 +18,7 @@ TODO
 
 ## State
 
-State fraud proofs allow light clients to avoid making an honest majority for
+State fraud proofs allow light clients to avoid making an honest majority assumption for
 state validity. While these are not incorporated into the protocol as of v1.0.0,
 there are example implementations that can be found in
 [Rollkit](https://github.com/rollkit/rollkit). More info in