diff --git a/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml b/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
index 0262660..ca14aeb 100644
--- a/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
+++ b/yaml/xyz/openbmc_project/HardwareIsolation/Create.interface.yaml
@@ -1,15 +1,15 @@
 description: >
-    This interface contains create method, which can be implemented to
-    create an xyz.openbmc_project.HardwareIsolation.Entry object
-    which will use to provide the information of isolated hardware.
+    This interface contains create method, which can be implemented to create an
+    xyz.openbmc_project.HardwareIsolation.Entry object which will use to provide
+    the information of isolated hardware.
 
 methods:
     - name: Create
       description: >
-          Create an xyz.openbmc_project.HardwareIsolation.Entry object
-          if any of the hardware, needs to be isolated. This interface
-          can be used if want to isolate hardware without an error log,
-          for example, the user voluntarily tried to isolate hardware.
+          Create an xyz.openbmc_project.HardwareIsolation.Entry object if any of
+          the hardware, needs to be isolated. This interface can be used if want
+          to isolate hardware without an error log, for example, the user
+          voluntarily tried to isolate hardware.
       parameters:
           - name: IsolateHardware
             type: object_path
@@ -34,13 +34,12 @@
 
     - name: CreateWithErrorLog
       description: >
-          Create an xyz.openbmc_project.HardwareIsolation.Entry object
-          if any of the hardware, needs to be isolated. This interface
-          can be used if the system wants to isolate hardware with
-          an error log that is caused to isolate hardware.
-          This method is not going to create an error log and the consumer
-          of this method need to pass the bmc error log which caused
-          the isolation.
+          Create an xyz.openbmc_project.HardwareIsolation.Entry object if any of
+          the hardware, needs to be isolated. This interface can be used if the
+          system wants to isolate hardware with an error log that is caused to
+          isolate hardware. This method is not going to create an error log and
+          the consumer of this method need to pass the bmc error log which
+          caused the isolation.
       parameters:
           - name: IsolateHardware
             type: object_path
diff --git a/yaml/xyz/openbmc_project/HardwareIsolation/Entry.interface.yaml b/yaml/xyz/openbmc_project/HardwareIsolation/Entry.interface.yaml
index bc49434..a435307 100644
--- a/yaml/xyz/openbmc_project/HardwareIsolation/Entry.interface.yaml
+++ b/yaml/xyz/openbmc_project/HardwareIsolation/Entry.interface.yaml
@@ -2,21 +2,19 @@
     Implement to provide the isolated hardware entry attributes.
 
     The object which implements this interface must implement
-    xyz.openbmc_project.Association.Definitions to point associated
-    object, for example, isolated hardware inventory path and error
-    log if it caused to isolate hardware. The isolated hardware
-    association of forward and reverse name must be following
-    respectively "isolated_hw" and "isolated_hw_entry". The error
-    log association of forward and reverse types must be following
+    xyz.openbmc_project.Association.Definitions to point associated object, for
+    example, isolated hardware inventory path and error log if it caused to
+    isolate hardware. The isolated hardware association of forward and reverse
+    name must be following respectively "isolated_hw" and "isolated_hw_entry".
+    The error log association of forward and reverse types must be following
     respectively "isolated_hw_errorlog" and "isolated_hw_entry".
 
     The object which implements this interface should implement
-    xyz.openbmc_project.Object.Delete to allow the deletion of
-    individual isolated hardware object.
+    xyz.openbmc_project.Object.Delete to allow the deletion of individual
+    isolated hardware object.
 
     The object which implements this interface must implement
-    xyz.openbmc_project.Time.EpochTime for the isolated hardware
-    creation time.
+    xyz.openbmc_project.Time.EpochTime for the isolated hardware creation time.
 
 properties:
     - name: Severity
@@ -27,11 +25,11 @@
       type: boolean
       default: false
       description: >
-          The isolated hardware resolution status is used to indicate
-          whether the isolated hardware is repaired or replaced.
-          Setting this to "true" may not delete this entry object because
-          in a few system platforms isolated hardware entries may not be
-          deleted and used for further analysis.
+          The isolated hardware resolution status is used to indicate whether
+          the isolated hardware is repaired or replaced. Setting this to "true"
+          may not delete this entry object because in a few system platforms
+          isolated hardware entries may not be deleted and used for further
+          analysis.
 
 enumerations:
     - name: Type
@@ -43,10 +41,9 @@
                 Critical hardware to repair or replace.
           - name: Warning
             description: >
-                The system can boot without the isolated hardware but,
-                will lose the system configuration benefits of isolated
-                hardware.
+                The system can boot without the isolated hardware but, will lose
+                the system configuration benefits of isolated hardware.
           - name: Manual
             description: >
-                A user attempted to isolate hardware to proceed with
-                the host to boot.
+                A user attempted to isolate hardware to proceed with the host to
+                boot.