diff --git a/docs/structured-logging.md b/docs/structured-logging.md
index 2e73bed..93db30c 100644
--- a/docs/structured-logging.md
+++ b/docs/structured-logging.md
@@ -109,10 +109,10 @@
 
 The APIs can handle (and format appropriately) any data of the following types:
 signed or unsigned integers, floating point numbers, booleans, strings
-(C-strings, std::strings, or `std::string_views`), sdbusplus enums and
-`object_paths`, generic enumerations (as numbers), exceptions, and pointers. The
-APIs will also allow arbitrary type formatting for any type which has a
-`to_string` function defined.
+(C-strings, std::strings, or `std::string_views`), `std::filesystem::paths`,
+sdbusplus enums and `object_paths`, generic enumerations (as numbers),
+exceptions, and pointers. The APIs will also allow arbitrary type formatting for
+any type which has a `to_string` function defined.
 
 The APIs also perform compile-time analysis of the arguments to give descriptive
 error messages for incorrect parameters or format flags. Some examples are:
diff --git a/extensions/openpower-pels/registry/README.md b/extensions/openpower-pels/registry/README.md
index edc9151..27c0044 100644
--- a/extensions/openpower-pels/registry/README.md
+++ b/extensions/openpower-pels/registry/README.md
@@ -211,8 +211,9 @@
 are separated by underscores. If not specified, the code will choose a default
 format, which may depend on the SRC type.
 
-For example: ["SRCWord3", "SRCWord9"] would be: `<ASCII_STRING>_<SRCWord3>_<SRCWord9>`,
-which could look like: `B181320_00000050_49000000`.
+For example: ["SRCWord3", "SRCWord9"] would be:
+`<ASCII_STRING>_<SRCWord3>_<SRCWord9>`, which could look like:
+`B181320_00000050_49000000`.
 
 ```json
 "SymptomIDFields": ["SRCWord3", "SRCWord9"]