Remove confusing TODO

README.md

@@ -16,7 +16,7 @@ that references to the task can be resolved to the right backend.
 Desired properties:
 
 * a proper fully functional *task* entity with max_retries, an
-  absolute deadline, logs, etc (logs are TODO)
+  absolute deadline, logs, etc (logs are somewhat TODO)
 * a JSON input/output data type for genericity
 * the ability to run worker code in any language
   * this requires all communication to be mediated by a well-defined API
@@ -25,7 +25,7 @@ Desired properties:
     lifetime
   * a task *implementation* (the executor) API is just an external
     program, to which we pass the JSON arguments via stdin, and read
-    JSON output via stdout (worker API is TODO)
+    JSON output via stdout
 * the ability to enqueue large number of tasks (for batch-like
   operations, forklifts, etc)
 * a concept of task dependencies (a DAG), to support multi-step use