PEL: README: Fix linting
Change-Id: Id9656444a88b3b8a5339ecb9562ba4314ed45f73
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
diff --git a/extensions/openpower-pels/README.md b/extensions/openpower-pels/README.md
index 02a26a4..6d60f2f 100644
--- a/extensions/openpower-pels/README.md
+++ b/extensions/openpower-pels/README.md
@@ -213,7 +213,6 @@
PEL:
- The AdditionalData property contents
-
- If the AdditionalData property in the OpenBMC event log has anything in it,
it will be saved in a UserData section as a JSON string.
@@ -588,13 +587,11 @@
```
- User Data parser module
-
- Module name: `xzzzz.py`, where `x` is the Creator Subsystem from the Private
Header section (in ASCII) and `zzzz` is the 2 byte Component ID from the
User Data section itself (in HEX). All should be converted to lowercase.
- For example: `b0100.py` for Hostboot created UserData with CompID 0x0100
- Function to provide: `parseUDToJson`
-
- Argument list:
1. (int) Sub-section type
2. (int) Section version
@@ -616,12 +613,10 @@
```
- SRC parser module
-
- Module name: `xsrc.py`, where `x` is the Creator Subsystem from the Private
Header section (in ASCII, converted to lowercase).
- For example: `bsrc.py` for Hostboot generated SRCs
- Function to provide: `parseSRCToJson`
-
- Argument list:
1. (str) Refcode ASCII string
2. (str) Hexword 2
diff --git a/extensions/openpower-pels/registry/README.md b/extensions/openpower-pels/registry/README.md
index ba80f39..5c862e0 100644
--- a/extensions/openpower-pels/registry/README.md
+++ b/extensions/openpower-pels/registry/README.md
@@ -631,7 +631,6 @@
4. One can test what PELs are generated from these new entries without writing
any code to create the corresponding event logs:
-
1. Copy the modified message_registry.json into `/etc/phosphor-logging/` on
the BMC. That directory may need to be created.
2. Use busctl to call the Create method to create an event log corresponding