1 files changed, 7 insertions, 6 deletions

diff --git a/settings_file.html b/settings_file.html
index bde19a5..d8dfb1a 100755
--- a/settings_file.html
+++ b/settings_file.html
@@ -64,7 +64,7 @@
             
             
               <div class="version">
-                0.3-rc10
+                0.3
               </div>
             
           
@@ -175,12 +175,13 @@ running. Grouping similar jobs in named queues will help you tune this number.</
 </div>
 <div class="section" id="queues">
 <h3>queues<a class="headerlink" href="#queues" title="Permalink to this headline">¶</a></h3>
-<p>Default: (10, default)</p>
-<p>Semi-colon seperated list of queues to process jobs for with thier
-weights. Example: <code class="docutils literal"><span class="pre">queues=(10,</span> <span class="pre">data_process);</span> <span class="pre">(15,</span> <span class="pre">email)</span></code>.  With these
+<p>Default: [[10, &#8220;default&#8221;]]</p>
+<p>Comma seperated list of queues to process jobs for with thier weights. This list
+must be valid JSON otherwise an error will be thrown.
+Example: <code class="docutils literal"><span class="pre">queues=[[10,</span> <span class="pre">&quot;data_process&quot;],</span> <span class="pre">[15,</span> <span class="pre">&quot;email&quot;]]</span></code>.  With these
 weights and the <code class="docutils literal"><span class="pre">CONCURRENT_JOBS</span></code> setting, you should be able to tune managers
-running jobs locally pretty efficiently. If you have a larger box with a weight
-of 50 on q1 and 8 concurrent jobs and a smaller box with a weight 30 and 4
+running jobs locally efficiently. If you have a larger server with a weight of
+50 on q1 and 8 concurrent jobs and a smaller server with a weight 30 and 4
 concurrent jobs, the q1 jobs will be sent to the large box until it is no longer
 accepting jobs. At this point jobs will start to be sent to the next highest
 number until the large box is ready to accept another q1 job.</p>