diff --git a/Docker-universal-app-web-interface.md b/Docker-universal-app-web-interface.md
index 45f2997..1e2f535 100644
--- a/Docker-universal-app-web-interface.md
+++ b/Docker-universal-app-web-interface.md
@@ -2,9 +2,9 @@ There are various possible interfaces for job submission to BUDA.
 We could make a Python-based remote API.
 We (or others) could use this API to integrate it into batch systems.
 
-But for starters, I propose implementing a generic (all-application)
-web-based job submission system.
-This uses the per-user file sandbox system.
+But for starters, I propose implementing a generic (multi-application)
+web-based job submission system,
+using the per-user file sandbox system.
 
 ## Managing science apps
 
@@ -13,7 +13,7 @@ This shows you the set of existing apps,
 and lets you edit them or create a new one.
 The form for this includes
 
-* select (from file sandbox) a set of 'app files'.  Must include
+* select (from your file sandbox) a set of 'app files'.  Must include
     * a Dockerfile
     * a main prog to run in container
     * other files if needed
@@ -25,11 +25,12 @@ The form for this includes
 
 ## Submitting jobs
 
-The form for submitting jobs:
+The form for submitting a batch of jobs:
 
+* batch name (optional)
 * select a BUDA science app and plan class
 * select (from the file sandbox) a zip file of job descriptions.
-This has one dir per job:
+This file has one dir per job:
 ```
 jobname/
     [cmdline]
@@ -37,9 +38,8 @@ jobname/
     ...
 ...
 ```
-* batch name (optional)
 
-Issue:
+Question:
 should this system manage file immutability?
 If so,
 the above filenames are logical and don't need to be unique;