commit a1347418307d31a94bd21f22897aa508df938dcf
author Patrick Williams <patrick@stwcx.xyz> Tue Dec 06 10:56:22 2022 -0600
committer Patrick Williams <patrick@stwcx.xyz> Tue Dec 06 11:11:59 2022 -0600
tree dfcb36f177db4f34b8b3f2be3ff718b3648ef755
parent 3c7b858a13aa5fde934d6d789c9a6027490f78dc

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

yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml

diff --git a/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml b/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
index 8cb0f13..0d99995 100644
--- a/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
+++ b/yaml/xyz/openbmc_project/MCTP/Endpoint.interface.yaml
@@ -20,12 +20,11 @@
           The logical address used to route MCTP messages to a specific MCTP
           endpoint. A numeric handle (logical address) that uniquely identifies
           a particular MCTP endpoint within a system for MCTP communication and
-          message routing purposes. Endpoint IDs are unique among MCTP
-          endpoints that comprise an MCTP communication network within a
-          system. MCTP EIDs are only unique within a particular MCTP network.
-          That is, they can be duplicated or overlap from one MCTP network to
-          the next. This is also referred to as "endpoint ID" and abbreviated
-          as "EID".
+          message routing purposes. Endpoint IDs are unique among MCTP endpoints
+          that comprise an MCTP communication network within a system. MCTP EIDs
+          are only unique within a particular MCTP network. That is, they can be
+          duplicated or overlap from one MCTP network to the next. This is also
+          referred to as "endpoint ID" and abbreviated as "EID".
 
     - name: SupportedMessageTypes
       type: array[byte]
@@ -37,6 +36,6 @@
           Ethernet over MCTP(0x03), NVM Express Management Messages over
           MCTP(0x04) and SPDM over MCTP(0x05). There are ranges for vendor
           defined message types. All the message types are specified in the
-          DSP0239 specification. A device that supports a given message type
-          may not support that message type equally across all buses that
-          connect to the device.
+          DSP0239 specification. A device that supports a given message type may
+          not support that message type equally across all buses that connect to
+          the device.