diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index a45bbd22..4f3032af 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -12,29 +12,9 @@ ____________
 ## CURRENT STAGE: 
 
 
-	
-todo: "NotifyEvent QUEUE" ui area where OPS ADMIN can see all notifyevent and remove any that they deem as stuck or won't deliver
-	Can delete 
-		if can't actually view the contents then it's an ops thing but if can view contents then it's a biz thing
-
-
-
-todo: notifysubscriptionbiz DELETE must CASCADE delete notifyevent records with that sub id
-	is this a DDL configuration of the table thing?  Is it already actually done?
-	No need to log the notifevent part deletion, just remove those fuckers
-
-todo: send test notification from both ops and admin pages
-	also from any user form and will troubleshoot as a matter of course before it sends
-	also from client users form
-	Will then issue warning if  OPS smtp notification is turned off (Active=false) or other problem, mirror of the code in the OPS notification setup form
-
-todo: notification system docs
-	It's complex and needs a clear documentation about how it all works
-		While it's fresh write a quick overview in docs so can flesh it out more later but get the main points even if in shorthand
-		Big overview then drill down
-
 todo: UI QUICK NOTIFY need a place to send a General (old "quick") notification directly to a user and test it works via email delivery as well when user subscribes to general via email
 	Maybe from the IN APP notification form itself as a link in the menu?
+	Can choose any user except customer type unless you're of a certain higher level role allowed to deal with customers like service manager, sales manager, biz admin etc
 
 todo: As biz objects are fleshed out need to also code their notification event stuff as well
 
@@ -43,6 +23,11 @@ todo: Localize this message or get rid of it, it's annoying and possibly useless
 todo: backup notification:	AY:Backup status:~SERVER~ 
 	fixup token with translated text and include link to backup status ops page
 
+todo: notification system docs
+	It's complex and needs a clear documentation about how it all works
+		While it's fresh write a quick overview in docs so can flesh it out more later but get the main points even if in shorthand
+		Big overview then drill down
+
 ##########################
 todo: User edit form role control is not working
 todo: server state form is not getting dirtied when setting radio button, only on text (try going to closed then open and not change text on open)