Inputs.md

@@ -61,13 +61,21 @@ Available modules:
     - stations -- Generate stationlist.json from shake_result.hdf.
 ```
 \
-So a simple call to organize the input data for the 'ci3144585' event into the HDF input file would be: 
+A simple call to organize the input data for the 'ci3144585' event into the HDF input file would be: 
 ```
 > shake ci3144585 assemble
+```
+You will then be prompted to enter a comment for this run, useful for keeping track of version changes:
+```
 INFO ; 2018-02-09 11:43:24 ; shake.main ; Running command assemble
+Please enter a comment for this version.
+comment:
+```
+Once a comment is entered, assemble will finish running.
+```
 INFO ; 2018-02-09 11:43:24 ; shake.main ; Finished running command assemble: Elapsed 0.14 secs
 ```
-This is not all that useful unless you want to read in and inspect the HDF file, called [shake_data.hdf](http://usgs.github.io/shakemap/manual4_0/tg_formats.html#shake-data-hdf). `shake_result.hdf` is a binary data structure for efficiently storing all of the inputs and results of the shakemap. Other modules extract information from this file and convert the results to more convenient formats, but this is the most fundamental data file for each shakemap from which all other outputs are created. 
+The `assemble` module alone is not all that useful _unless_ you want to read in and inspect the HDF file, called [shake_data.hdf](http://usgs.github.io/shakemap/manual4_0/tg_formats.html#shake-data-hdf). `shake_result.hdf` is a binary data structure for efficiently storing all of the inputs and results of the ShakeMap software and is the most fundamental data file from which all other outputs are created. Other modules called by `shake` extract information from this file and convert the results to more convenient formats.  
 \
 \
 \