diff --git a/FURPS/application/sds.md b/FURPS/application/sds.md
index 6a43095..2d5a55d 100644
--- a/FURPS/application/sds.md
+++ b/FURPS/application/sds.md
@@ -7,21 +7,21 @@
 
 ## Usability
 
-1. 🏗️ When sending a message to a large group, the application knows whether it was received by other group members, with high probability
-2. 🏗️ When being part of a large group, the application is able to know whether they are missing messages, and is able to retrieve missed messages
+1. When sending a message to a large group, the application knows whether it was received by other group members, with high probability
+2. When being part of a large group, the application is able to know whether they are missing messages, and is able to retrieve missed messages
 
 ## Reliability
 
-1. 🏗️ When sending a message in a group, the publisher can ascertain the message was received by at least one recipient **(Vac-QA)**
-2. 🏗️ When receiving messages in a group, the receiver can ascertain most missed messages by receiving one recent message from the group. **(Vac-QA)**
+1. When sending a message in a group, the publisher can ascertain the message was received by at least one recipient **(Vac-QA)**
+2. When receiving messages in a group, the receiver can ascertain most missed messages by receiving one recent message from the group. **(Vac-QA)**
 
 ## Performance
 
 Assuming messages in a group are sent at least every `S` seconds.
 
-1. 🏗️ When sending a message in a group, the publisher can ensure the message was received by at least one recipient within`S` seconds **(Vac-DST)**
-2. 🏗️ When receiving messages in a group, the receiver can detect 90% of missed messages within `3*S` seconds, and reach eventual consistency within `6*S` seconds **(Vac-DST)**
+1. When sending a message in a group, the publisher can ensure the message was received by at least one recipient within`S` seconds **(Vac-DST)**
+2. When receiving messages in a group, the receiver can detect 90% of missed messages within `3*S` seconds, and reach eventual consistency within `6*S` seconds **(Vac-DST)**
 
 ## Supportability
 
-1. 🏗️ Applied to Communities channels only, both Status Mobile and Desktop
+1. Applied to Communities channels only, both Status Mobile and Desktop
diff --git a/draft-roadmap/define_p2p_reliability.md b/draft-roadmap/define_p2p_reliability.md
index 0e2dc90..825844a 100644
--- a/draft-roadmap/define_p2p_reliability.md
+++ b/draft-roadmap/define_p2p_reliability.md
@@ -14,11 +14,17 @@ User experience is catered for, in terms of delay of message retrieval and reten
 which is why store performance is also review and maximized for the current circumstances.
 Limited effort will be spent on store performance as its relevance is expected to reduce mid-long term.
 
+**FURPS** (see deliverables)
+
 **Deliverables**:
 
+
+
 <!--
 Once the deliverables are created as GitHub issues, we can delete the content below
 and just provide a list of GitHub issues, or even simpler, a link to the GitHub milestone that contain them.
+
+Also copy the FURPS from deliverable here.
 -->
 
 ## Define and Implement Light Push Error codes in nwaku.
diff --git a/draft-roadmap/introduce_e2e_reliability_in_status.md b/draft-roadmap/introduce_e2e_reliability_in_status.md
index 3e69547..80ee855 100644
--- a/draft-roadmap/introduce_e2e_reliability_in_status.md
+++ b/draft-roadmap/introduce_e2e_reliability_in_status.md
@@ -14,7 +14,11 @@ With this milestone, we design and deliver a first PoC for an end-to-end reliabi
 This protocol will be specified and implemented in the Status app for Status Communities chat rooms;
 as well as in the browser for PoC Web Apps such as Qaku and Logos Forum.
 
-**deliverables**: https://github.com/waku-org/pm/milestone/29
+**FURPS**:
+
+- [SDS](/FURPS/application/sds.md): F1-2, U1-2, R1-2, P1-2, S1
+
+**GitHub Milestone and deliverables**: https://github.com/waku-org/pm/milestone/29
 
 ## [End-to-end reliability protocol - Status integration]()