diff --git a/whitepapers/0001_generic_message_passing.md b/whitepapers/0001_generic_message_passing.md
index 4c494e14d2..4d205c530d 100644
--- a/whitepapers/0001_generic_message_passing.md
+++ b/whitepapers/0001_generic_message_passing.md
@@ -201,7 +201,7 @@ is provided by permissionless relayers.
 
 With IBC, for two chains to communicate directly with each other, they would have to be able to prove state mutually.
 This usually means implementing light clients for the other chain. In modern pBFT chains like those based
-on [Tendermint](https://v1.cosmos.network/resources/whitepaper) consensus, verifying light client proofs
+on [Tendermint](https://cosmos.network/whitepaper) consensus, verifying light client proofs
 is [very cheap](https://blog.cosmos.network/light-clients-in-tendermint-consensus-1237cfbda104) - all that is needed is
 to follow validator set changes, instead of a full header chain. However, chains talking to each other directly would
 get unmanageable with many chains - and this is where central hubs like Cosmos Hub come in. Instead of every individual
diff --git a/whitepapers/0011_accountant.md b/whitepapers/0011_accountant.md
index 12a2515227..ecc73edc5f 100644
--- a/whitepapers/0011_accountant.md
+++ b/whitepapers/0011_accountant.md
@@ -40,7 +40,7 @@ The core of the issue is the differing trust assumptions and security program ma
 
 ## Overview
 
-The `global-accountant` contract on wormchain acts as an [Integrity Checker](0010_integrity_checkers.md).  Guardians submit [pre-observations](0010_integrity_checker.md#pre-observations) to it and only finalize their observations if the `global-accountant` gives the go-ahead.
+The `global-accountant` contract on wormchain acts as an [Integrity Checker](0010_integrity_checkers.md).  Guardians submit [pre-observations](0010_integrity_checkers.md#pre-observations) to it and only finalize their observations if the `global-accountant` gives the go-ahead.
 
 `global-accountant`keeps track of the tokens locked and minted on each connected blockchain.