From c692c8a32dfe7f4d01b7ca0f316b7253d8655919 Mon Sep 17 00:00:00 2001
From: m4sterbunny <20266893+m4sterbunny@users.noreply.github.com>
Date: Sat, 20 Sep 2025 07:38:48 +0100
Subject: [PATCH] continues clearout

---
 glossary.md                      | 4 ++--
 technology/consensus-at-scale.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/glossary.md b/glossary.md
index 85aa548..f7db1a8 100644
--- a/glossary.md
+++ b/glossary.md
@@ -29,7 +29,7 @@ Individuals or organizations that operate and maintain Validator Services. They
 
 ### Checkpoint
 
-A finalized snapshot of Appchain states. At the end of each Pelagos epoch, validators agree on the current state root of every Appchain, bundle these into a single checkpoint, and commit it (along with its proofs) to one or more L1 restaking contracts.
+A finalized snapshot of Appchain states. At the end of each Pelagos epoch, validators agree on the current state root of every Appchain, bundle these into a single checkpoint, and commit it (along with its proofs) to one or more L1 restaking contracts. <!-- here -->
 
 ### Checkpoint Merkle root
 
@@ -164,7 +164,7 @@ A Pelagos open-source node that includes L1/L2 oracles, sequencing consensus, Ap
 
 ### Validator set
 
-The pool of validators authorized to participate in Pelagos' DAG consensus and TSS signing. It's dynamically updated based on restaking commitments from various L1 networks. A majority (⅔+1 by stake) must sign blocks, checkpoints, and external transactions.
+The pool of validators authorized to participate in Pelagos' DAG consensus and TSS signing. <!-- It's dynamically updated based on restaking commitments from various L1 networks. A majority (⅔+1 by stake) must sign blocks, checkpoints, and external transactions. -->
 
 <!-- ## W  -->
 
diff --git a/technology/consensus-at-scale.md b/technology/consensus-at-scale.md
index 42bcff7..138d8e0 100644
--- a/technology/consensus-at-scale.md
+++ b/technology/consensus-at-scale.md
@@ -23,7 +23,7 @@ The immutable database model provides a multichain, universal state, ensuring ef
 
 The DAG database achieves this through its key attributes: 
 -  Immutable state snapshots providing tamper-evident, incremental snapshots of blockchain states. 
-> These snapshots enable seamless synchronization and verifiable data integrity across Appchains, reinforced by restaking confirmations through Pelagos checkpoints.
+> These snapshots enable seamless synchronization and verifiable data integrity across Appchains, reinforced by confirmations through Pelagos checkpoints.
 - Incremental database design enabling rapid synchronization by processing
 only relevant components, making it highly adaptable for diverse Appchain architectures.
 - Advanced historical indexing enabling users to define comprehensive historical indexes across Appchains and external blockchains.