Fix MD030 warnings

The following warnings are generated by using markdownlint analysis:
```
tuning.md:68:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:69:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:72:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:74:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:75:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:76:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
```
Refer to markdown-lint [1] to fix MD030
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/030-list-marker-space.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I6a44ef257f7786dbe6b6875ef3b83559360dc1ee
diff --git a/tuning.md b/tuning.md
index 718b784..54a19cd 100644
--- a/tuning.md
+++ b/tuning.md
@@ -65,12 +65,12 @@
 
 ## Thermal Tuning Example
 
-1.  Create initial `/usr/share/swampd/config.json` used for PID control
-2.  (Option 1) If using a fixed setpoint, write the value to
-    `/etc/thermal.d/setpoint`, run swampd manually with
-    `swampd -l ${LOG_PATH}&`, and kill the process after desired duration.
-3.  (Option 2) If sweeping fan setpoint, using the tuning helper script
-    `fan_rpm_loop_test.sh` to configure fan setpoint in steps and collect logs
-4.  Parse logs from `${LOG_PATH}/zone_*.log` and analyze response data
-5.  Modify `/usr/share/swampd/config.json` as needed
-6.  Repeat from step 2 or step 3
+1. Create initial `/usr/share/swampd/config.json` used for PID control
+2. (Option 1) If using a fixed setpoint, write the value to
+   `/etc/thermal.d/setpoint`, run swampd manually with `swampd -l ${LOG_PATH}&`,
+   and kill the process after desired duration.
+3. (Option 2) If sweeping fan setpoint, using the tuning helper script
+   `fan_rpm_loop_test.sh` to configure fan setpoint in steps and collect logs
+4. Parse logs from `${LOG_PATH}/zone_*.log` and analyze response data
+5. Modify `/usr/share/swampd/config.json` as needed
+6. Repeat from step 2 or step 3