Update docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md

Co-authored-by: Marius Poke <[email protected]>

docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md

@@ -31,7 +31,7 @@ or using skipping, where intermediate headers are verified and must be signed by
 from the last trusted header validators. The latter is the default method, as it is faster in most cases.
 Additionally, light clients are cross-checking new headers obtained from a primary with witnesses to ensure all nodes share the same state.
 
-A light client attack occurs when a Byzantine validator sends incorrect states to a light client.
+A light client attack occurs when a Byzantine validator sends invalid headers to a light client.
 As the light client doesn't execute transactions, it can be deceived into trusting corrupted application states.
 For instance, if a light client receives header A from the primary and header `B` from the witness for the same block height `H`,
 and both headers are successfully verified, it indicates a light client attack.