diff --git a/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org b/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org
index 4aa7181c..98b8592b 100644
--- a/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org
+++ b/journal/2020-11-26--10-11-23Z--meta_rfc_for_dev_team.org
@@ -90,7 +90,7 @@ Describe the objective of this RFC.
 + pros
 + cons
 
-**** Considerations
+**** Furter Considerations and Remarks
 
 Generic place to put comment not suitable in any other subsection.
 Typically, we could add
@@ -98,11 +98,14 @@ Typically, we could add
 + Security
 + Communication
 
-** Considerations
+** Further Considerations and Remarks
 
+*** =dev= label
 
-Here  are my proposed templates.
-We already have a =dev= label we should probably use for RFC meaningful
-only for developpers, and we should continu to use the =Epic= label for
-issues whose goal is the provide a spcecification document that we could
-give to Managers with an Execution Plan.
+We already have a =dev= label we should probably use for RFC whose audience
+is just the iroh team.
+
+*** =Epic= label
+
+We should continu to use the =Epic= label for issues whose goal is to
+produce a specification document along with an execution plan.