diff --git a/doc/devel/rfc.txt b/doc/devel/rfc.txt
index 9879727e2..d435feded 100644
--- a/doc/devel/rfc.txt
+++ b/doc/devel/rfc.txt
@@ -1,18 +1,19 @@
 Design Process
 ==============
 
-//Menu:   include rfc
-//Menu:   include rfc_parked
+//Menu:   include rfc_final
 //Menu:   include rfc_pending
+//Menu:   include rfc_parked
 //Menu:   include rfc_dropped
 
-//Menu:   put child 'rfc_dropped' after 'rfc'
+//Menu: put child 'rfc_dropped' after 'rfc_final'
+
 
 How it Works
 ------------
 Design Process entries (Request for Comment) can be created by anyone.
 Each entry goes through several stages until it's accepted (or rejected).
-All our RfC entries are filed here, either in the  link:rfc/index.html[RfC accepted] section,
+All our RfC entries are filed here, either in the  link:rfc_final/index.html[RfC accepted] section,
 or as link:rfc_pending/index.html[pending RfC] or as link:rfc_dropped/index.html[RfC dropped].
 
 * Every proposal starts out as _*Idea*_, allowing other people to review and comment on it, while still working out details.
diff --git a/doc/devel/rfc/index.txt b/doc/devel/rfc/index.txt
index 23814933a..ecb1fd47c 100644
--- a/doc/devel/rfc/index.txt
+++ b/doc/devel/rfc/index.txt
@@ -1,10 +1,13 @@
 Design Proposal Pool
 ====================
 
-//Menu: off
+//Menu: discard
 //Menu: sort children
 
 -> read link:../rfc.html[more about Lumiera RfC] and the Design Process
 
-This is the poll where all Design Proposals are stored.
+This is the pool where all Design Proposals are stored.
+According to the current state of each RfC (pending, final, dropped, parked),
+there is also a symlink from the respective subdirectory to the actual document
+stored here.
 
diff --git a/doc/devel/rfc_final/index.txt b/doc/devel/rfc_final/index.txt
index c9e8a4515..a29cff26d 100644
--- a/doc/devel/rfc_final/index.txt
+++ b/doc/devel/rfc_final/index.txt
@@ -6,6 +6,8 @@ Accepted Design Proposals
 
 -> read link:../rfc.html[more about Lumiera RfC] and the Design Process
 
-The RfC entries listed here where discussed, maybe modified and finally agreed upon
-during some developers meeting in the past. So they represent design decisions taken.
+The RfC entries listed here where discussed, modified and finally agreed upon
+during some developers meeting in the past.
+
+So they represent design decisions taken and can be considered binding.