Inputs.md

-To run ShakeMap, an event needs to be added to the data directory. The easiest way to create an event is to use the `sm_create` tool, which should be in your path if you are in the `shakemap` virtual environment. To create a data directory for the January 1994 Northridge earthquake, you could run the following command:
+To run ShakeMap, an event needs to be added to the data directory. The easiest way to create an event is to use the `sm_create` tool, which should be in your path if you are in the `shakemap` virtual environment. To create a data directory for the January 1994 Northridge earthquake, you could run the command:
 ```
 sm_create ci3144585
 ```
@@ -13,21 +13,22 @@ This command will:
 
 OR
 
-you could run the command 
+you could run the command: 
 
 ```
 sm_create ci3144585 -e ci 1994-01-17T12:30:55 -118.546 34.211 19 6.6 "Northridge, California" -n
 ```
 
-where the `-e` flag tells sm_create to gather origin information from the command line, and
-
-the `-n` flag prevents this event being flagged as a scenario.
+where the `-e` flag tells sm_create to gather origin information from the command line, and the `-n` flag prevents this event being flagged as a scenario.
 
 This version of the command will only create an event.xml file.
 
-The programs for running ShakeMap are all managed by the command [shake](http://usgs.github.io/shakemap/programs/shake.html). The basic idea is that you will call `shake`, which has a number of optional arguments, but it is followed by an event id (i.e., the name of the event directory in the data directory) and then the names of the modules that you want to run for that event. You can get help in a terminal like this
+The programs for running ShakeMap are all managed by the command [shake](http://usgs.github.io/shakemap/programs/shake.html). The basic idea is that you will call `shake`, which has a number of optional arguments, followed by an event id (the name of the event directory in the data directory) **and then the names of the modules that you want to run for that event**. You can get help in a terminal by typing:
 ```
 > shake -h
+```
+which will output the following:
+```
 usage: shake [-h] [-d] [-q] [-l] eventid cmds [cmds ...]
 
     Run specified ShakeMap modules.
@@ -59,10 +60,15 @@ Available modules:
     - select - Parse STREC output, make a GMPE set, create model_zc.conf.
     - 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 
+\
+So a simple call to organize the input data for the 'ci3144585' event into the HDF input file would be: 
 ```
 > shake ci3144585 assemble
 INFO ; 2018-02-09 11:43:24 ; shake.main ; Running command assemble
 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). 
+\
+\
+\
+Next step: [Model](https://github.com/usgs/shakemap/wiki/model)
\ No newline at end of file