From 254c4f66e6f5b9ce5cb541ea320859aad7bc00ce Mon Sep 17 00:00:00 2001
From: Guru <19eucs071@skcet.ac.in>
Date: Tue, 14 May 2024 19:54:31 +0530
Subject: [PATCH] Fixing typos (#54)

* adding thegraph blog

* adding thegraph blog (#50) (#51)

* fixing typo

* Revert "adding thegraph blog (#50) (#51)" (#52)

This reverts commit b3f80d98759cafbe1978e877eabb3702555e7a24.

* FIx typo (#53)

---------

Co-authored-by: chair <29414216+chair28980@users.noreply.github.com>
---
 posts/2024-05-13-the-graph-case-study.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/posts/2024-05-13-the-graph-case-study.mdx b/posts/2024-05-13-the-graph-case-study.mdx
index fd3ccaa0..4d8fa753 100644
--- a/posts/2024-05-13-the-graph-case-study.mdx
+++ b/posts/2024-05-13-the-graph-case-study.mdx
@@ -74,7 +74,8 @@ Before the GraphOps team introduced GraphCast, the majority of the indexing solu
 **2. Old-fashioned group chat:** It is highly dependent on Web2 communications, which have a single point of failure and higher security risks.
 
 **3. Automated bots:** Several indexer bots running on centralised servers to automate communication on event signalling.
-All the three solutions listed above could have been more efficient. Hence, we wanted a more robust and decentralised communications infrastructure to fix several issues. The core contributors of GraphOps mention that Waku is an obvious choice for solving this problem. Continue reading to learn more about how GraphCast uses Waku.
+
+All three solutions listed above could have been more efficient. Hence, we wanted a more robust and decentralised communications infrastructure to fix several issues. The core contributors of GraphOps mention that Waku is an obvious choice for solving this problem. Continue reading to learn more about how GraphCast uses Waku.
 
 ## How does The Graph use Waku?