yaml: format with prettier

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I193f690f3612fe72ec69030f81f4d5096a761601
diff --git a/yaml/xyz/openbmc_project/Software/RedundancyPriority.interface.yaml b/yaml/xyz/openbmc_project/Software/RedundancyPriority.interface.yaml
index 5290218..4b3e088 100644
--- a/yaml/xyz/openbmc_project/Software/RedundancyPriority.interface.yaml
+++ b/yaml/xyz/openbmc_project/Software/RedundancyPriority.interface.yaml
@@ -5,19 +5,20 @@
     - name: Priority
       type: byte
       description: >
-        The priority order specified for the associated Software.Version,
-        represented as a value between 0 (High) and 127 (Low).  Any value
-        above 127 has implementation-specific purpose.
+          The priority order specified for the associated Software.Version,
+          represented as a value between 0 (High) and 127 (Low).  Any value
+          above 127 has implementation-specific purpose.
 
-        Only one Software.Version, per associated device, may be at any
-        particular priority.  A requested priority change may cause other
-        Software.Versions to change priority.
+          Only one Software.Version, per associated device, may be at any
+          particular priority.  A requested priority change may cause other
+          Software.Versions to change priority.
 
-        A dual-sided redundancy model could be represented by two
-        Software.Version associations, one of which is at priority 0 and the
-        other at priority 1.  When a new image is Activated, the old
-        priority-1 association is deleted, the old priority-0 association
-        becomes priority-1, and the new image is assigned priority-0.
+          A dual-sided redundancy model could be represented by two
+          Software.Version associations, one of which is at priority 0 and the
+          other at priority 1.  When a new image is Activated, the old
+          priority-1 association is deleted, the old priority-0 association
+          becomes priority-1, and the new image is assigned priority-0.
+
 # TODO: Specify "EAGAIN" type error when priority is unable to be modified
 #       due to current system state.  Currently, sdbusplus does not support
 #       errors on properties.