Rewrite shell snippets for clarity

README.md

@@ -96,7 +96,7 @@ We need to start the queue engine and tell it which database to use:
 Then we can start the worker and have it talk to the engine:
 
 ```shell
-# enq worker --server localhost:3733
+enq worker --server localhost:3733
 ```
 
 Run each of these commands in its own terminal as they are daemons
@@ -133,7 +133,7 @@ Save the above to *task.json*. Now it's possible to submit this task
 to the queue:
 
 ```shell
-# enq submit --server localhost:3733 < task.json
+enq submit --server localhost:3733 < task.json
 ```
 
 The worker logs should show the *process-user-data* script being
@@ -202,7 +202,7 @@ will ensure the correct order of execution. Save the above to
 *tree.json* and submit it with:
 
 ```shell
-# enq submit --server localhost:3733 < tree.json
+enq submit --server localhost:3733 < tree.json
 ```
 
 Again, worker logs should show the two tasks being executed in
@@ -225,12 +225,12 @@ We can start the various components with the following commands
 (again, run each one in a separate terminal):
 
 ```shell
-# enq server --db test1.db --shard host1 --addr :3733 \
+enq server --db test1.db --shard host1 --addr :3733 \
     --topology static:1=localhost:3733,2=localhost:3734
-# enq server --db test2.db --shard host2 --addr :3734 \
+enq server --db test2.db --shard host2 --addr :3734 \
     --topology static:1=localhost:3733,2=localhost:3734
-# enq worker --id worker1 --server localhost:3733
-# enq worker --id worker2 --server localhost:3734
+enq worker --id worker1 --server localhost:3733
+enq worker --id worker2 --server localhost:3734
 ```
 
 Suppose that we now want to save user data from all shards:
@@ -292,7 +292,7 @@ You can send the submission request to any instance of the
 engine. Save the above to *tree2.json* and submit it with:
 
 ```shell
-# enq submit --server localhost:3734 < tree2.json
+enq submit --server localhost:3734 < tree2.json
 ```
 
 All tasks should execute in order on the expected workers.