From 7f7c78ed90f138b7bc634e9f4e290caafdbab810 Mon Sep 17 00:00:00 2001
From: neo773 <62795688+neo773@users.noreply.github.com>
Date: Wed, 4 Sep 2024 01:17:24 +0530
Subject: [PATCH] Update meetings.md (#487)

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

diff --git a/docs/meetings.md b/docs/meetings.md
index 59e178e7..1e548318 100644
--- a/docs/meetings.md
+++ b/docs/meetings.md
@@ -37,7 +37,7 @@ Here we agreed on the following requirements:
 3. We need to support a broadcast strategy that reaches all nodes in the cluster very quickly (for example through high fanout values) and optimally
    supporting acknowledgement. This will be necessary for the consensus protocols.
 4. We should support some sort of immutable facts that can be spread across the cluster such as certificate revocation.
-5. For all of { CRDTs, strongly consistent mutable data, immutable facts } we want to support a time to live.
+5. For all of \{ CRDTs, strongly consistent mutable data, immutable facts \} we want to support a time to live.
 6. We want to have encryption and cryptographic signing built in from the beginning. Peter started posting about that.
 
 I believe this gives us enough requirements to begin creating a short list of possible protocol that we could use for this.