pushing change to configuration format

hpvm/docs/developerdocs/configuration-format.rst

@@ -10,11 +10,13 @@ The format of the configuration is includes one line per fused HPVM node. Note t
 File Format
 --------------
 
-`+++++`
-`${config_id} ${predicted_speedup} $predicted_energy} ${real_accuracy} ${accuracy_degration}`
-`${hpvm_node_id} ${device=cpu|gpu} ${tensor_op_type} ${approximation_knob} ....`
-`${hpvm_node_id} .....`
-`-----`
+.. code-block:: lang
+		
+   +++++
+   ${config_id} ${predicted_speedup} $predicted_energy} ${real_accuracy} ${accuracy_degration}
+   ${hpvm_node_id} ${device=cpu|gpu} ${tensor_op_type} ${approximation_knob} ....
+   ${hpvm_node_id} .....
+   -----
 
 The delimeters `+++++` and `-----` marked beginning and end of a configuration
 
@@ -26,5 +28,5 @@ The `$config_id` is the configuration ID in the configuration file. A configurat
 
 `$real_accuracy` is the accuracy of the program on the tune set (inputs used for tuning) when no approximations are applied and `$accuracy_degradation` is the drop in accuracy when applying the configuration that follows - the specific knob settings that follow.
 
-`$hpvm_node_id` specifies the node ID to apply the approximation knobs for, `$device` specifies the device to offload to, `${tensor_op_type}` specifies the type of tensor operation (conv, mul, add, relu etc.), and `approximation_knob` is the knob setting corresponding to this tensor operation. The autotuner selects these knobs.  
+`$hpvm_node_id` specifies the node ID to apply the approximation knobs for, `$device` specifies the device to offload to, `$tensor_op_type` specifies the type of tensor operation (conv, mul, add, relu etc.), and `$approximation_knob` is the knob setting corresponding to this tensor operation. The autotuner selects these knobs.