reformat with latest settings

Reformat with the latest settings from openbmc-build-scripts (and
copy latest config files where appropriate).  Fix a few minor
markdownlint issues.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I55205817c29dc3f182a165ddf9cd5d4e07b90063
diff --git a/yaml/xyz/openbmc_project/Logging/Create.interface.yaml b/yaml/xyz/openbmc_project/Logging/Create.interface.yaml
index 9798b76..0da55b5 100644
--- a/yaml/xyz/openbmc_project/Logging/Create.interface.yaml
+++ b/yaml/xyz/openbmc_project/Logging/Create.interface.yaml
@@ -1,8 +1,7 @@
 description: >
-    This interface contains a Create method, which can be implemented
-    to allow creation of xyz.openbmc_project.Logging.Entry objects
-    directly over D-Bus, without needing the errors defined in
-    the *.Error/metadata.yaml files.
+    This interface contains a Create method, which can be implemented to allow
+    creation of xyz.openbmc_project.Logging.Entry objects directly over D-Bus,
+    without needing the errors defined in the *.Error/metadata.yaml files.
 
 methods:
     - name: Create
@@ -20,8 +19,7 @@
           - name: AdditionalData
             type: dict[string, string]
             description: >
-                The AdditionalData property of the event entry.
-                e.g.:
+                The AdditionalData property of the event entry. e.g.:
                   {
                     "key1": "value1",
                     "key2": "value2"
@@ -34,9 +32,9 @@
           Create an xyz.openbmc_project.Logging.Entry object and pass in an
           array of file descriptors for files that contain FFDC (first failure
           data capture) data which may be used by event log extensions that
-          support storing it with their event logs.  The other arguments are
-          the same as with Create().  The FFDC argument is ignored by the
-          base phosphor-logging event logs.
+          support storing it with their event logs.  The other arguments are the
+          same as with Create().  The FFDC argument is ignored by the base
+          phosphor-logging event logs.
 
           When the method call is complete the descriptors must be closed and
           the files can be deleted if desired.
@@ -52,8 +50,7 @@
           - name: AdditionalData
             type: dict[string, string]
             description: >
-                The AdditionalData property of the event entry.
-                e.g.:
+                The AdditionalData property of the event entry. e.g.:
                   {
                     "key1": "value1",
                     "key2": "value2"
@@ -63,20 +60,21 @@
           - name: FFDC
             type: array[struct[enum[self.FFDCFormat], byte, byte, unixfd]]
             description: >
-                File descriptors for any files containing FFDC, along with metadata
-                about the contents:
+                File descriptors for any files containing FFDC, along with
+                metadata about the contents:
 
                   FFDCFormat- The format type of the contained data.
                   subType - The format subtype, used for the 'Custom' type.
-                  version - The version of the data format, used for the 'Custom'
+                  version - The version of the data format, used for the
+                'Custom'
                             type.
                   unixfd - The file descriptor to the data file.
 
-                e.g.:
-                [
-                  {"xyz.openbmc_project.Logging.Create.FFDCFormat.JSON", 0, 0, 5},
-                  {"xyz.openbmc_project.Logging.Create.FFDCFormat.Custom", 1, 2, 6}
-                ]
+                e.g.: [
+                  {"xyz.openbmc_project.Logging.Create.FFDCFormat.JSON", 0, 0,
+                5},
+                  {"xyz.openbmc_project.Logging.Create.FFDCFormat.Custom", 1, 2,
+                6} ]
 
 enumerations:
     - name: FFDCFormat