Fix MD040 warnings
The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md
Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I503908cfe6b198c172d158acbb3e50033f862686
diff --git a/README.md b/README.md
index 63a2481..edbdd5c 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@
Say we have 'identify' LED in our system, which may be declared in devicetree.
-```
+```text
leds {
compatible = "gpio-leds";
@@ -19,13 +19,13 @@
We can add an LED via the helper program. The main service is then started via
dbus-activation.
-```
+```sh
./add-led-action --path /sys/class/leds/identify
```
which will expose following dbus objects:
-```
+```text
busctl tree xyz.openbmc_project.LED.Controller
`- /xyz
`- /xyz/openbmc_project
@@ -50,7 +50,7 @@
Query the LED State
-```
+```text
busctl get-property xyz.openbmc_project.LED.Controller \
/xyz/openbmc_project/led/physical/identify \
xyz.openbmc_project.Led.Physical State \
@@ -59,7 +59,7 @@
Set the LED State
-```
+```text
busctl set-property xyz.openbmc_project.LED.Controller \
/xyz/openbmc_project/led/physical/identify \
xyz.openbmc_project.Led.Physical State s \
@@ -68,7 +68,7 @@
## How to Build
-```
+```sh
meson setup build
cd build
ninja