Fixing typos (#54)

* adding thegraph blog * adding thegraph blog (#50) (#51) * fixing typo * Revert "adding thegraph blog (#50) (#51)" (#52) This reverts commit b3f80d9. * FIx typo (#53) --------- Co-authored-by: chair <[email protected]>
waku-org · May 14, 2024 · 254c4f6 · 254c4f6
1 parent 6d6607e
commit 254c4f6
Showing 1 changed file with 2 additions and 1 deletion.
diff --git 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?