diff --git a/CTng/server/Readme.md b/CTng/server/Readme.md
index 28b2f0b..63a3601 100644
--- a/CTng/server/Readme.md
+++ b/CTng/server/Readme.md
@@ -1,23 +1,3 @@
-Monitor_ng and Monitor Context explanation:  
-
-Types.go  
-
-For Monitor Context, there are 4 attributes that function as a timer  
-
-Timer_CAs                 TimedMap  
-Timer_Loggers             TimedMap  
-Timer_Loggers_LastCheckIn int64 (Unix() format)  
-Timer_CAs_LastCheckIn     int64 (Unix() format)  
-
-Invoke func (c *MonitorContext) InitializeTimedMap() when starting the monitor  
-
-If the monitor receives the information (a valid gossip object) from a logger, it will update the Timer from the Timer_loggers with the URL of that logger as the key.  
-If the monitor receives the information (a valid gossip object) from a CA, it will update the Timer from the Timer_CAs with the URL of that CA as the key.  
-If it has been more than 1 MMD since last check in, the monitor will do a linear search on the Timer_loggers, accuse all loggers that didn't repond in this MMD,   
-and update the Timer_Loggers_LastCheckIn.  
-If it has been more than 1 MRD since last check in, the monitor will do a linear search on the Timer_CAs, accuse all CAs that didn't repond in this MMD,   
-and update the Timer_CArs_LastCheckIn.  
-
 Monitor_ng.go  
 
 func Monitor_accuseEntity(c *crypto.CryptoConfig, Accused string) (gossip.Gossip_object, error)