Editor changes for 13, 2, 4

content/docs/rfcs/13/README.md

@@ -3,10 +3,10 @@ slug: 13
 title: 13/WAKU2-STORE
 name: Waku v2 Store
 status: draft
-editor: Oskar Thorén <oskar@status.im>
+editor: Sanaz Taheri <sanaz@status.im>
 contributors:
   - Dean Eigenmann <dean@status.im>
-  - Sanaz Taheri <sanaz@status.im>
+  - Oskar Thorén <oskar@status.im>
 ---
 
 This specification explains the Waku `WakuStore` protocol which enables querying of messages received through relay protocol and stored by other nodes. It also supports pagination for more efficient querying of historical messages. 

content/docs/rfcs/2/README.md

@@ -3,9 +3,10 @@ slug: 2
 title: 2/MVDS
 name: Minimum Viable Data Synchronization
 status: stable
-editor: Oskar Thorén <oskar@status.im>
+editor: Sanaz Taheri <sanaz@status.im>
 contributors:
   - Dean Eigenmann <dean@status.im>
+  - Oskar Thorén <oskar@status.im>
 ---
 
 In this specification, we describe a minimum viable protocol for data synchronization inspired by the Bramble Synchronization Protocol[^1]. This protocol is designed to ensure reliable messaging between peers across an unreliable peer-to-peer (P2P) network where they may be unreachable or unresponsive.

content/docs/rfcs/4/README.md

@@ -3,10 +3,11 @@ slug: 4
 title: 4/MVDS-META
 name: MVDS Metadata Field
 status: draft
-editor: Oskar Thorén <oskar@status.im>
+editor: Sanaz Taheri <sanaz@status.im>
 contributors:
   - Dean Eigenmann <dean@status.im>
   - Andrea Maria Piana <andreap@status.im>
+  - Oskar Thorén <oskar@status.im>
 ---
 
 In this specification, we describe a method to construct message history that will aid the consistency guarantees of [2/MVDS](/spec/2). Additionally, we explain how data sync can be used for more lightweight messages that do not require full synchronization.