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.
diff --git a/yaml/xyz/openbmc_project/MCTP/README.md b/yaml/xyz/openbmc_project/MCTP/README.md
index 57a5044..0d3f5cf 100644
--- a/yaml/xyz/openbmc_project/MCTP/README.md
+++ b/yaml/xyz/openbmc_project/MCTP/README.md
@@ -1,9 +1,9 @@
 # Overview
 
-MCTP D-Bus interfaces are implemented by the MCTP control process daemon
-alias mcptd and aids in the discovery of MCTP enabled devices by application
-layer protocols (like PLDM, SPDM) which are implemented in the userspace.
-Application layer protocols will rely on the discovery of
+MCTP D-Bus interfaces are implemented by the MCTP control process daemon alias
+mcptd and aids in the discovery of MCTP enabled devices by application layer
+protocols (like PLDM, SPDM) which are implemented in the userspace. Application
+layer protocols will rely on the discovery of
 `xyz.openbmc_project.MCTP.Endpoint` D-Bus interface to discover MCTP endpoints.
 The supported MCTP message types in an endpoint are exposed by the
 `SupportedMessageTypes` property in the `xyz.openbmc_project.MCTP.Endpoint`
@@ -15,8 +15,8 @@
 ## D-Bus object modelling
 
 The root D-Bus object path for the mctpd is `/xyz/openbmc_project/mctp`. There
-will be a D-Bus object for every endpoint that is discovered by the mctpd.
-The lifetime of the D-Bus object is the lifetime of the connected MCTP device.
+will be a D-Bus object for every endpoint that is discovered by the mctpd. The
+lifetime of the D-Bus object is the lifetime of the connected MCTP device.
 
 The D-Bus object path for MCTP endpoints are named
 `xyz/openbmc_project/mctp/<NetworkId>/<EID>` where NetworkId is the locally
@@ -34,9 +34,9 @@
 to tell whether the access points provide access to the same MCTP Network or to
 different MCTP Networks. If the implementation supports the optional MCTP
 network ID then it is exposed on the D-Bus. The D-Bus object path is
-`xyz/openbmc_project/mctp/<NetworkId>` where NetworkId is the locally
-defined [network identfier][1] and implements the
-`xyz.openbmc_project.Common.UUID` interface and the UUID property is the MCTP
-network ID.
+`xyz/openbmc_project/mctp/<NetworkId>` where NetworkId is the locally defined
+[network identfier][1] and implements the `xyz.openbmc_project.Common.UUID`
+interface and the UUID property is the MCTP network ID.
 
-[1]: https://github.com/openbmc/docs/blob/master/designs/mctp/mctp-kernel.md#addressing
+[1]:
+  https://github.com/openbmc/docs/blob/master/designs/mctp/mctp-kernel.md#addressing