From 830464908e49e68297eb7dbe9d6d8a39ed168107 Mon Sep 17 00:00:00 2001
From: Luca Donno <30298476+lucadonnoh@users.noreply.github.com>
Date: Tue, 8 Oct 2024 16:04:28 +0200
Subject: [PATCH] Remove incorrect example

---
 docs/spec/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/spec/overview.md b/docs/spec/overview.md
index 9e325f98d..42bfa9a9a 100644
--- a/docs/spec/overview.md
+++ b/docs/spec/overview.md
@@ -25,7 +25,7 @@ Because of this, EigenDA makes use of the EigenLayer state, which is stored on E
 
 Among extant DA solutions, EigenDA takes an approach to scalability which is unique in that it yields true horizontal scalability: Every additional unit of capacity contributed by an operator can increase the total system capacity. 
 
-This property is achieved by using a Reed Solomon erasure encoding scheme to shard the blob data across the DA nodes. While other systems such as Celestia and Danksharding (planned) also make use of Reed Solomon encoding, they do so only for the purpose of supporting certain observability properties of Data Availability Sampling (DAS) by light nodes. On the other hand, all incentivized/full nodes of the system download, store, and serve the full system bandwidth. 
+This property is achieved by using a Reed Solomon erasure encoding scheme to shard the blob data across the DA nodes. While other systems such as Celestia also make use of Reed Solomon encoding, they do so only for the purpose of supporting certain observability properties of Data Availability Sampling (DAS) by light nodes. On the other hand, all incentivized/full nodes of the system download, store, and serve the full system bandwidth. 
 
 Horizontal scalability provides the promise for the technological bottlenecks of DA capacity to continually track demand, which has enormous implications for Layer 2 ecosystems.