Fix MD001 warnings
The following warnings are generated by using markdownlint analysis:
```
bmc/README.md:6 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3]
```
Refer to markdown-lint [1] to fix MD001
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/001-header-increment.md
Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I511b66da543dd2bfb40ea4910d2d74416fd0ccb9
diff --git a/bmc/README.md b/bmc/README.md
index 8083e5f..28f4e6f 100644
--- a/bmc/README.md
+++ b/bmc/README.md
@@ -3,7 +3,7 @@
This document gives details about the format of the config file used by log,
version and firmware handler. The config file is a .json file.
-### Parameters
+## Parameters
There are 3 important parameters in this config file
@@ -36,24 +36,24 @@
}
```
-#### blob
+### blob
This parameter defines the unique name of the blob. This parameter must be
defined for each blob.
-#### handler
+### handler
A blob must have a handler with a type. Currently only "file" type is supported.
With file type, a path of the handler file must be provided.
-#### actions
+### actions
"actions" define various steps to be performed and are required for each blob.
These actions can be triggered from ipmi-blob commands. Currently there are 2
types of actions supported: `systemd` to invoke a systemd service, or `skip` to
not perform any action.
-### Workflow of log handler
+## Workflow of log handler
```json
{