few corrections in the README

tmss/README.md

@@ -100,6 +100,8 @@ If everything is specified in the config file, there are still few must-have opt
 - name of the config file (`--config`)
 - `-ub` options to upload and blueprint scheduling unit(s)
 
+# Usage examples with command-line options
+
 - simple LBA pulsar timing observation (submit the draft to TMSS with `-u` and blueprint it with `-b`). Here we modified the existing the HBA specs by giving `LBA_ALL` value for the `--antennafield`  option and also changing the filter to `LBA_10_90` for the `--filter` option.
 ```
 ./tmss_sched_observation.py --name "B0809+74-test-sched" 
@@ -149,10 +151,11 @@ If everything is specified in the config file, there are still few must-have opt
 ```
 
 # Configuration file
-Here are a couple examples of configuration file (YAML format), where `tstart` is used either as a "string" or a "list":
+Here is a couple examples of configuration file (YAML format) to be specified with `--config`:
 ```
 #
-# using "tstart" as a list, together with Pulsar Timing strategy with id=520 using "strategy_id", enabling FE observation with "fe" setting other parameters for BF data.
+# using "tstart" as a list, together with Pulsar Timing strategy with id=520 using "strategy_id", 
+# enabling FE observation with "fe" setting other parameters for BF data.
 #
 project: "COM_LOFAR2"
 strategy_id: 520
@@ -173,7 +176,11 @@ tstart:
   - "2025-02-09T13:01:00"
 ```
 ```
-# using "tstart" as a single string, with a prepared JSON "specfile" instead of strategy, specifying "coherent" observation with 8-bit recording (quantisation: True) of XXYY data (mode: "XXYY"), forming 2 rings of TABs with a given ring radius.
+#
+# using "tstart" as a single string, with a prepared JSON "specfile" instead of strategy, 
+# specifying "coherent" observation with 8-bit recording (quantisation: True) of XXYY data (mode: "XXYY"), 
+# forming 2 rings of TABs with a given ring radius.
+#
 project: "COM_LOFAR2"
 specfile: "examples/generic-bf.json"
 target: "PSR B1919+21"