diff --git a/docs/architecture/ADR-002-QGB-ValSet.md b/docs/architecture/ADR-002-QGB-ValSet.md
index 39201f60ed..d3e416591f 100644
--- a/docs/architecture/ADR-002-QGB-ValSet.md
+++ b/docs/architecture/ADR-002-QGB-ValSet.md
@@ -12,6 +12,8 @@ To accommodate the requirements of the [Quantum Gravity Bridge](https://github.c
 
 Add the `ValSet` and `ValSetConfirm` type of messages in order to track the state of the validator set.
 
+PS: The `ValsetConfirm` have been updated in `ADR-005-QGB_reduce_state_usage`. Please take a look on it to know how we will be handling the confirms.
+
 ## Detailed Design
 
 Since the QGB is only a one way bridge and is not transferring assets, it doesn't require the portions of the gravity module that recreate state from the bridged chain. We only need to keep things relating to signing over the validator set (such as`MsgSetOrchestratorAddress` and `MsgValsetConfirm`) and relayer queries (such as `ValsetConfirm` and `GetDelegateKeyByOrchestrator`).
diff --git a/docs/architecture/ADR-003-QGB-DataCommitment.md b/docs/architecture/ADR-003-QGB-DataCommitment.md
index eb57907c04..2739b2f07b 100644
--- a/docs/architecture/ADR-003-QGB-DataCommitment.md
+++ b/docs/architecture/ADR-003-QGB-DataCommitment.md
@@ -12,6 +12,8 @@ To accommodate the requirements of the [Quantum Gravity Bridge](https://github.c
 
 Add the `DataCommitmentConfirm` type of messages in order to attest that a set of blocks has been finalized.
 
+PS: The `ValsetConfirm` have been updated in `ADR-005-QGB_reduce_state_usage`. Please take a look on it to know how we will be handling the confirms.
+
 ## Detailed Design
 
 To accommodate the QGB, validators need a way to submit signatures for a data commitments so that relayers can easily find them and submit them to the bridged chain. To do this, we will introduce `MsgDataCommitmentConfirm` messages. This latter will be persisted for the sole reason of slashing. If not for that, a P2P network would do the job.