Updated The BOINC test drive (markdown)

The-BOINC-test-drive.md

@@ -26,7 +26,7 @@ The test drive can't include:
 First, we create a "BOINC app library".
 It includes a number of widely-used apps (like Autodock, Charm, Rosetta, etc),
 compiled to run on BOINC (w/ the BOINC library).
-For app, the library includes app versions for various platforms,
+For each app, the library includes app versions for various platforms,
 CPU features, and GPUs.
 Each app version has an associated plan class specification.
 One of the apps is the VBox wrapper.
@@ -70,12 +70,12 @@ attaching hosts to project.
 It knows which hosts are part of the Demo grid.
 For each project, it knows whether it is
 - unvetted
-- vetted (shallow or deep; see below)
+- vetted (partial or full; see below)
 This info is used in deciding what projects to attach each host to.
 
 ## Test-drive scenarios
 
-### unvetted/central
+### Unvetted/central
 ```
     goal: quickly run batches of jobs on computers you don't own
     User experience:
@@ -140,10 +140,10 @@ Notes:
 - you don't have to specify job sizes (CPU, RAM, disk).
 We could have a system that estimates these for you, based on past jobs
 
-## unvetted/distributed
+## Unvetted/distributed
 ```
     Similar, but user has their own BOINC server;
-        avoids storage and BW bottleneck of central server
+        avoids storage and bandwidth bottleneck of central server
         Also lets you attach your own computers directly.
     - get a Linux machine visible on Internet
         could be Cloud node