From eeaa58b797d98109049b8d616bcce89e0e354468 Mon Sep 17 00:00:00 2001
From: rymnc <43716372+rymnc@users.noreply.github.com>
Date: Wed, 7 Sep 2022 09:37:39 +0530
Subject: [PATCH] chore(WAKU2-STORE): address review

---
 content/docs/rfcs/13/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/docs/rfcs/13/README.md b/content/docs/rfcs/13/README.md
index 1163929d..29185514 100644
--- a/content/docs/rfcs/13/README.md
+++ b/content/docs/rfcs/13/README.md
@@ -21,7 +21,9 @@ As such, they are required to be *highly available* and in specific have a *high
 The high uptime requirement makes sure that no message is missed out hence a complete and intact view of the message history is delivered to the querying nodes.
 Nevertheless, in case that storage provider nodes cannot afford high availability, the querying nodes may retrieve the historical messages from multiple sources to achieve a full and intact view of the past.
 
-The concept of "ephemeral" messages exists while using `13/WAKU2-STORE` as well. Any `WakuMessage` that has the ephemeral flag set to true will not be added to the store, thereby reducing the amount of one-time use messages on disk. While the node SHOULD not store messages with the ephemeral flag set to true, they MAY do so for archival.
+The concept of "ephemeral" messages exists while using `13/WAKU2-STORE` as well.
+Any `WakuMessage` that has the `ephemeral` flag set to `true` MAY be ignored by the store service node, thereby reducing the amount of one-time use messages stored.
+Nodes SHOULD NOT not store messages with the `ephemeral` flag set to `true`.
 
 # Security Consideration