diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index f206d8a5..45c111f6 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -1,31 +1,12 @@
 # now
 
 
+- case 4207 work out a maintenance schedule that works for me for each data center relative to their timezones and general workday
 
-todo: case 4193 In job log add cancel button for running jobs or someway of doing it from there
-	should be able to see active jobs at a glance, how long running, who started if applicable and cancel
-
-
-todo: document how subswcription servers will work, follow the plan of discourse
-	have a small number maybe one of shared servers in set regions, e.g. USWEST, USEAST, CANEAST(TORONTO), EU(germany) and whatever is close to singapore
-	Or, perhaps start a new user in any region on a regular droplet but with storage instad of local drive space on server
-	then, as new users are added just add more horsepower to that server and add more users to it until it's at a good limit
-	THIS---===^
-todo: make a sample customer droplet with all storage on an external volume 
-	Not sure about db but maybe just accept the db will be local?
 
 
 REORGANIZE BELOW AND THEN WHATEVER IS MOST URGENT
 
-PRICING / COSTS
-
-Done!
-
-
-
-- Launch a trialing server, can start small and work up but keep all users on it so to save money and not any of our own corporate infrastructure servers
-	"All free trial subscriptions are located in New York data center.  Paid subscriptions can be in any of the following data centers of your choice ...blah blah blah."
-- Test moving a trial db to a dedicated droplet as will utltimately need to do that for users
 
 
 
@@ -40,24 +21,7 @@ The initial sign up form is a dialog that requests the following info:
 
 
 
-=-=-=-=-
 
-# later
-
-THINGS HOLDING UP RELEASE
-
-- figure out how to use a storage volume and put multiple single users and trialers on the same server
-	So each user has a dedicated server, dedicated 20gb storage space (or whatever size), entire db and all data is on that storage
-	Start with a trialer / tester server and work up from there to actual hosting on the same server
-	Maybe for single users have no more than 3 per server or some fixed number in case the server crashes or a single user ties it up somehow or whatever?
-
-- Move this to a case I think: How to tell which of multiple customers on the same server is using the most resources 
-	Keep in mind need to know if there are 5 users on a server which of the 5 is using up the bandwidth/cpu/whatever if we need to boot them off
-	Like the TOP utility showing each process so know which server by name or...??
-	this is a tricky issue maybe ignore it for now but circle around back to it later
-	AyaNova maybe report some gross statistics on usage etc that we can tap into without logging in.
-	Seems like we need an ops interface without actually logging into their data but still see it? hmm...
-	Maybe just pull the metrics part of the db out for analysis??
 
 
 - Subscribers need to know taht their server will be rebooted daily if and when security updates come in