Update docs

Author: ethanhann

docs-src/configuration.md

@@ -1,14 +1,14 @@
 # Configuration 
 
-Configuration is accomplished by modifying the appsettings.json file that comes with the InEngine.NET binary distribution.
+Configuration is accomplished by modifying the appsettings.json file that comes with the InEngine.NET binary distribution. The -c, --configuration argument can also be used to specify an alternate configuration file.
 
 
 ```json
 {
   "InEngine": {
     "Queue": {
       "PrimaryQueueConsumers":  16,
-      "SecondaryQueueConsumers": -1,
+      "SecondaryQueueConsumers": 4,
       "QueueName": "InEngine:Queue",
       "RedisHost": "localhost",
       "RedisPort": 6379,
@@ -20,8 +20,15 @@ Configuration is accomplished by modifying the appsettings.json file that comes
 
 ```
 
-The -c, --configuration argument can also be used to specify an alternate configuration file.
-
+| Setting                   | Description               |
+| ------------------------- | ------------------------- |
+| PrimaryQueueConsumers     | The number of consumers to schedule for the primary queue.        |
+| SecondaryQueueConsumers   | The number of consumers to schedule for the secondary queue.      |
+| QueueName                 | The base name of the queue, used to form the Redis Queue keys.    |
+| RedisHost                 | The Redis hostname to connect to.                                 |
+| RedisPort                 | Redis's port.                                                     |
+| RedisDb                   | The Redis database - 0-15                                         |
+| RedisPassword             | The Redis auth password                                           |
 
 
 

docs-src/queuing.md

@@ -89,9 +89,7 @@ However, it is often desirable to have more than 1 queue.
 For example, long running jobs might be sent to the secondary queue, 
 while jobs that are expected to finish after only a few moments are sent to the primary queue.
 
-What about 3, 4, 900 queues? This gets to be a pain to manage and, practically speaking, is probably unnecessary.
+What about 3, 4, or 900 queues? Numerous queues gets to be a pain to manage and, practically speaking, is probably unnecessary.
 If it is desirable, different [configuration files](configuration) can be used to run multiple instances of InEngine.NET.
-
- 
-  
+Simply create a new config file with a new QueueName setting and point inengine.exe at it.