analyzer/ras-data/ras-data-definition.md: 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: I7bcddf15b7b059a0be181c09fec4924f2d15ecb8
diff --git a/analyzer/ras-data/ras-data-definition.md b/analyzer/ras-data/ras-data-definition.md
index f21e0de..50c4867 100644
--- a/analyzer/ras-data/ras-data-definition.md
+++ b/analyzer/ras-data/ras-data-definition.md
@@ -28,7 +28,7 @@
The value of this keyword is a JSON object representing all of the guardable
unit targets on this chip. Each element of this object will have the format:
-```
+```text
"<unit_name>" : "<relative_devtree_path>"
```
@@ -43,7 +43,7 @@
The value of this keyword is a JSON object representing all of the buses
connected to this chip. Each element of this object will have the format:
-```
+```text
"<bus_name>" : { <bus_details> }
```
@@ -68,7 +68,7 @@
actions available for the file. Each element of this object contains an array of
RAS actions, to be performed in order, with the format:
-```
+```text
"<action_name>" : [ { <action_element> }, ... ]
```
@@ -261,7 +261,7 @@
from this chip requiring RAS actions. Each element of this object will have the
format:
-```
+```text
"<sig_id>" : { "<sig_bit>" : { "<sig_inst>" : "<action_name>", ... }, ... }
```