Minor polishing for docs

Author: netj

README.md

@@ -8,7 +8,7 @@ It organizes code, inputs, and outputs for experiments, records results, and let
 ### Motivation
 Organizing the data that goes into and comes out of experiments, as well as maintaining the infrastructure for running them, is generally regarded as a tedious and mundane task.
 Often times we end up in a suboptimal environment improvised and hard-coded for each experiment.
-The problem is exacerbated when the experiments must be performed iteratively for exploring a large parameter space.
+The problem is exacerbated when the experiment runs must be performed iteratively for exploring a large parameter space.
 Easing this burden will enable us to more quickly make interesting discoveries from the data our experiments produce.
 "Data scientists" are emerging everywhere these days to ask questions in the form of computational experiments, and to discover new facts from the "big data" their institutions have accumulated.
 In fact, these computational and data-driven approaches have long been a standard method for doing science in many domains, and we see ever growing number of fields depending on computational experiments.

docs/features/README.md

@@ -25,7 +25,7 @@ For example, you can use <span class="sans-serif">3X</span> to play with small P
 
 ### Input Variables
 *Input variables* are what you want to vary between executions of your program.
-You can specify a finite set of discrete, symbolic values for each input variable, e.g., `insertionSort`, `quickSort`, and `mergeSort`, etc. for input variable `algo` that determines which sorting algorithm is used.
+You can specify a finite set of discrete, symbolic values for each input variable.
 <span class="sans-serif">3X</span> supplies values for the input variables to your experiment program in the form of environment variables.
 A filesystem directory is provided for each input variable and each value of it to let you organize relevant input files in a manifest way.